API Reference/Management/Tenants/SCIM
GET
/scim/v2/Groups/{groupId}

Authorization

AuthorizationRequiredBearer <token>

< Project ID >:< Access Key > as bearer

In: header

Path Parameters

groupIdRequiredstring

Query Parameters

displayNamestring
externalIdstring
excludedAttributesstring
curl -X GET "https://api.descope.com/scim/v2/Groups/string?displayName=string&externalId=string&excludedAttributes=string" \
  -H "Authorization: Bearer <token>"

OK

{
  "displayName": "string",
  "schemas": [
    "string"
  ],
  "id": "string",
  "members": [
    {
      "value": "string",
      "display": "string"
    }
  ],
  "meta": {
    "created": {},
    "location": "string",
    "lastModified": {},
    "resourceType": "string"
  },
  "externalId": "string",
  "detail": "string"
}

Was this helpful?

Create SCIM Group POST

### Create a SCIM group, using a valid access key. This endpoint allows administrators to create new SCIM groups within their environement. When creating the group, you can configure the groupId, displayName, and it's members. The response includes the new group's group object which includes details about the groups including the members. 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. ### Next Steps Once you have created the group, you can later add or remove users from the SCIM groups via [Update SCIM Group](/api/management/tenants/scim/update-scim-group). ### 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>`

Update SCIM Group PUT

### Update an existing SCIM group, using a valid access key. This endpoint allows administrators to update an existing SCIM group using the SCIM group ID, which is a required field. You can update the display name and members through this API endpoint. The response includes the group's object which includes details about the groups including the members. 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>`