SCIM API
Unified.to's SCIM API provides SCIM 2.0 Users and Groups endpoints, based on RFC 7644, over its HR & Directory integrations. A SCIM client can list, create, update and delete users in a customer's HR system or directory, including systems that don't support SCIM themselves. It's available on every plan.
How does SCIM map onto HR & Directory integrations?
Each SCIM call is translated into the connected integration's own API at request time, using the HR & Directory Employee object for users. SCIM works on any HR & Directory integration that supports the Employee object; there's no separate SCIM integration to activate. Activate the HR integrations you need and create connections as usual.
What works depends on the integration:
- Reads (list, get) work wherever the integration lists employees.
- Creates, updates and deletes work only where the integration writes employees. Okta, Microsoft Entra ID, Google Workspace Directory and JumpCloud, for example, create, update and remove them; Workday and Remote.com are read-only for employees (as of 19 October 2026).
- Groups map to the HR & Directory Group object, so they depend on the integration's group support: Okta and Google Workspace Directory, for example, create, update and remove groups; Workday only reads them (as of 19 October 2026).
- An operation the integration doesn't support returns 501.
Each integration's Feature Support tab lists its employee and group methods.
Endpoints
| Object | Method | Path | Operation |
|---|---|---|---|
| Users | POST | /scim/{connection_id}/users | Create user |
| Users | GET | /scim/{connection_id}/users | List users |
| Users | GET | /scim/{connection_id}/users/{id} | Get user |
| Users | PUT | /scim/{connection_id}/users/{id} | Update user |
| Users | PATCH | /scim/{connection_id}/users/{id} | Update user (partial) |
| Users | DELETE | /scim/{connection_id}/users/{id} | Delete user |
| Groups | POST | /scim/{connection_id}/groups | Create group |
| Groups | GET | /scim/{connection_id}/groups | List groups |
| Groups | GET | /scim/{connection_id}/groups/{id} | Get group |
| Groups | PUT | /scim/{connection_id}/groups/{id} | Update group |
| Groups | PATCH | /scim/{connection_id}/groups/{id} | Update group (partial) |
| Groups | DELETE | /scim/{connection_id}/groups/{id} | Delete group |
List requests accept filter, startIndex and count for paging, and sortBy and sortOrder. Responses use the SCIM schemas. Send Accept: application/scim+json to receive the SCIM media type. The OpenAPI file is openapi-scim.json.
Which schema extensions are supported?
User records accept three extensions:
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User: employee number, cost centre, organization, division, department, managerurn:ietf:params:scim:schemas:extension:lattice:attributes:1.0:Userurn:ietf:params:scim:schemas:extension:peakon:2.0:User
Does the SCIM API send webhooks?
No. The SCIM API doesn't send webhooks. To find out when users change, subscribe to HR & Directory employee and group webhooks on supported integrations. They're native on integrations such as HiBob, Personio, Google Workspace Directory and Microsoft Entra ID, and come from virtual webhooks on integrations such as BambooHR, Workday and Okta, which check at an interval you set, as often as every minute on paid plans.
Limits
- Enterprise-managed (
ema_) tokens can't call the SCIM API. - Unified.to keeps no customer records at rest; connection credentials and operational metadata are encrypted at rest.