Skip to main content

Update User (SCIM)

Replace a user using SCIM 2.0 PUT operation (full replacement).

Quick Navigation

Endpoint

PUT /scim/v2/Users/{user_id}

Headers

HeaderRequiredDescription
AuthorizationYesBearer <scim_bearer_token>
Content-TypeYesapplication/scim+json
AcceptYesapplication/scim+json or application/json

Path Parameters

ParameterTypeRequiredDescription
user_idstringYesUser ID

Request Body

{
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"id": "123",
"userName": "user@example.com",
"name": {
"formatted": "Jane Doe",
"familyName": "Doe",
"givenName": "Jane"
},
"active": true,
"emails": [
{
"value": "user@example.com",
"primary": true
}
]
}

Response

Success (200)

{
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"id": "123",
"userName": "user@example.com",
"name": {
"formatted": "Jane Doe",
"familyName": "Doe",
"givenName": "Jane"
},
"active": true,
"emails": [
{
"value": "user@example.com",
"primary": true
}
],
"meta": {
"resourceType": "User",
"created": "2024-01-01T12:00:00Z",
"lastModified": "2024-01-01T13:00:00Z",
"location": "/scim/v2/Users/123"
}
}

Features

  • SCIM 2.0 compliant
  • Full replacement of user data
  • All fields must be provided (PUT semantics)
  • Use PATCH for partial updates

Example

curl -X PUT "https://api.rivergen.com/scim/v2/Users/123" \
-H "Authorization: Bearer <scim_bearer_token>" \
-H "Content-Type: application/scim+json" \
-H "Accept: application/scim+json" \
-d '{
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"id": "123",
"userName": "user@example.com",
"name": {
"formatted": "Jane Doe",
"familyName": "Doe",
"givenName": "Jane"
},
"active": true,
"emails": [{
"value": "user@example.com",
"primary": true
}]
}'