Replace a SCIM user
PUT
/v1/scim/v2/{connectionId}/Users/{id}How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| connectionId | path | string | Yes | Identity connection encoded into the tenant-specific SCIM base URL |
| id | path | string | Yes | Stable SCIM resource ID |
Query parameters
None.
Body schema
Content type: application/scim+json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| schemas | string[] | Yes | — |
| id | string | No | Unique identifier. |
| externalId | string | No | — |
| userName | string | Yes | — |
| displayName | string | No | — |
| active | boolean | No | — |
| emails | object[] | No | — |
| emails[].value | string | Yes | — |
| emails[].primary | boolean | No | — |
| emails[].type | string | No | — |
| meta | object | No | — |
| meta.resourceType | User | Group | Yes | — |
| meta.created | string | Yes | — |
| meta.lastModified | string | Yes | — |
| meta.location | string | No | — |
| meta.version | string | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200SCIM user replaced
None.