Your directory, driven by your systems
A REST API to create, update and deactivate employees from your own middleware, one at a time or 100 per request, matched on the identifier you already trust.
Book a free, no-obligation product demo call with our experts.
Does CultureMonkey have an API for employee data?
Yes. The CultureMonkey Employee API is a REST API your HR system, middleware or integration platform can call to keep the employee directory current: add joiners, update moves and promotions, and deactivate leavers, so every survey goes to the right people and every report cuts the right way.
Here is what it covers:
- OperationsList employees, fetch one, create, update, deactivate, and bulk upload up to 100 records per request.
- MatchingSingle-record calls use your external ID. Bulk uploads match on external ID by default, or on employee ID or email address.
- Org dataA team or location named in a record is created if it does not exist yet, and in bulk uploads business units and sub-teams too. Managers resolve from the same batch or the existing directory.
- LeaversDeactivation marks someone inactive. Their history and past responses stay intact.
- AccessOne API key per account, found under Settings, Integrations, sent over HTTPS with every request.
- LimitsUp to 1,000 requests a minute from one IP address, and 30 a second. A bulk request with some invalid records loads the valid ones and reports the rest.
What the API carries, and how it matches people
Type of integration
REST API, JSON
Direction
Your systems into CultureMonkey
Bulk upload
Up to 100 employees per request
Rate limit
1,000 requests a minute per IP
Built for the integration your IT team already runs
If your HR events already flow through middleware or an integration platform, the Employee API lets CultureMonkey be one more destination, current the moment your source system is.
Joiners, movers and leavers, as they happen
Call the API from the workflow that already handles a hire, transfer or exit, and CultureMonkey is current the moment your system is. No waiting for the next scheduled sync.
- Create a joiner with team, location, manager and start date, so onboarding surveys reach them on time.
- Send only the fields that changed when someone moves team, site or manager.
- Deactivate a leaver with one call. They stop receiving surveys and their past responses stay in reporting.
Bulk loads that survive a bad record
Load a whole directory in batches of 100. Records whose anchor already exists update in place, new ones are created, and one invalid row never sinks the batch.
- Valid records load; the response lists the ones that failed validation and why.
- Managers can be loaded in the same batch as their reports, or already exist in CultureMonkey.
- Teams, locations, business units and sub-teams named in a record are created when they do not exist yet.
Your identifiers, not ours
Give every person an external ID from your source system that never changes. Reads, updates and deactivations look people up by it, so records line up across every sync even when names and emails change.
- Bulk uploads can match on external ID, the default, or on employee ID or email address instead.
- Custom attributes, such as pay type, cost center or shift, travel with each record once they exist in CultureMonkey.
Data out goes through its own APIs
The Employee API manages the directory. To take engagement data into your warehouse or BI tool, CultureMonkey pushes it to an endpoint you host or lets your system pull it on its own schedule, with anonymity thresholds applied. See data warehouse and BI exports.
- Data Export pushes responses, participation, eNPS, comments, action plans and manager insights to your endpoint on a schedule.
- The Data Pull API lets your system read the same datasets a page at a time.
- Rows from anonymous surveys never carry identity, and small groups are withheld.
What the Employee API does
Single-record calls key on your external ID, and bulk uploads on the identifier you choose, so the same person lines up across every call, however often your systems sync.
| Operation | What it does | Worth knowing |
|---|---|---|
| List employees | Returns the directory a page at a time | Use it to reconcile against your source |
| Get employee | Returns one person by their external ID | Includes manager, team, location and custom attributes |
| Create employee | Adds one person | A new team or location named in the record is created |
| Update employee | Changes only the fields you send | Partial payloads are safe |
| Deactivate employee | Marks the person inactive | History and responses are kept |
| Bulk upload | Creates or updates up to 100 people per request | Existing anchors update; valid records load even if some fail |
Built for enterprise security, recognized for performance
Frequently asked questions
Where do we get an API key?
Can we load our whole directory through the API?
Do managers have to be created first?
Does deactivating an employee delete their responses?
What are the rate limits?
Can we send surveys or read results through this API?
Should we use the API, SFTP or an HRIS connector?
See the Employee API with your own directory
Book a free, no-obligation product demo call with our experts.