API Reference/Management/Tenants/SCIM
GET
/scim/v2/Users/{userId}

Authorization

AuthorizationRequiredBearer <token>

< Project ID >:< Access Key > as bearer

In: header

Path Parameters

userIdRequiredstring
curl -X GET "https://api.descope.com/scim/v2/Users/string" \
  -H "Authorization: Bearer <token>"

OK

{
  "user": {
    "schemas": [
      "string"
    ],
    "id": "string",
    "userName": "string",
    "meta": {
      "created": {},
      "location": "string",
      "lastModified": {},
      "resourceType": "string"
    },
    "emails": [
      {
        "value": "string",
        "primary": true,
        "type": "string"
      }
    ],
    "name": {
      "givenName": "string",
      "familyName": "string",
      "middleName": "string"
    },
    "active": true,
    "displayName": "string",
    "detail": "string",
    "attributes": {}
  }
}

Was this helpful?

Patch SCIM Group PATCH

Patch SCIM Group, using a valid access key. ### Endpoint Authentication Use authorization bearer header with the following format: `Authorization: Bearer <ProjectId:AccessKey>`

Update SCIM User PUT

### Update an existing SCIM user, using a valid access key. This endpoint allows administrators to update an existing SCIM user. Through this API endpoint, administrators can update the displayName, phoneNumbers, emails, and if the user is active. The response includes the user's object, which includes details about the users including their email, phone, username, name, etc. It is important to note the bearer token for SCIM API endpoints. The format is `ProjectId:AccessKey` the access key must be associated with the applicable tenant and associated with the tenant admin role. ### See also - See [SCIM Management](/scim) for further details on managing SCIM provisioning. ### Endpoint Authentication Use authorization bearer header with the following format: `Authorization: Bearer <ProjectId:AccessKey>`