SCIM provisioning - 400 Bad Request on user update with extension attribute

Administration
1

I know SSO can feel overwhelming, but… we’re hitting a 400 Bad Request when attempting to update a user in Genesys Cloud via the SCIM API - specifically when including a custom extension attribute. The error message is pretty vague: “Invalid request body”. We’re on Genesys Cloud, API v2.

From what I’ve seen, the documentation isn’t super clear on handling extensions during updates. The flow is an OIDC initiated provisioning from Okta, using the /api/v2/scim/users endpoint. The payload looks valid against the schema - just trying to add a simple string attribute. Is there a specific format Genesys Cloud expects for extension attributes during PUT requests?

Here’s a sample payload snippet:

{
 "schemas": ["urn:ietf:params:scim:schema:2.0:Core", "urn:ietf:params:scim:schema:2.0:extension:genesyscloud:user"],
 "id": "user123",
 "externalId": "okta-user-123",
 "userName": "user123@example.com",
 "name": {
 "givenName": "John",
 "familyName": "Doe"
 },
 "extension": {
 "someCustomAttribute": "someValue"
 },
 "meta": {
 "resourceType": "User"
 }
}
1 Like