API ReferenceManagementScim Management
POST
/v1/mgmt/scim/key/activate

Authorization

Descope Project ID and Management Key
AuthorizationBearer <token>

Project ID:Management Key as bearer token.

In: header

Request Body

application/json

tenantId?string
ssoId?string

The SSO configuration the keys belong to. Omit it to target the tenant's default configuration - it does NOT mean "every configuration".

keyIds?array<string>
string

The keys to activate, from LoadSCIMAccessKeys. Required and explicit on purpose: activating a whole configuration would silently restore a key an operator had deactivated because its secret leaked. Ids that are not SCIM keys of this tenant and configuration are rejected.

Re-enable specific deactivated SCIM access keys of a tenant, using a valid management key. This reverses a revoke that used revokeMode DEACTIVATE; keys that were deleted cannot be restored. The keys to activate must be named explicitly - call Load SCIM Access Keys to get their ids - so that a key deactivated because its secret leaked is never restored as a side effect.

curl -X POST "https://api.descope.com/v1/mgmt/scim/key/activate" \  -H "Content-Type: application/json" \  -d '{}'
{  "activatedKeyIds": [    "string"  ]}
export interface Response {activatedKeyIds?: string[]}
Was this helpful?

Delete resources batch POST

Delete multiple resources, using a valid management key.

Create SCIM Access Key POST

Create a SCIM access key for a tenant, using a valid management key. The key is scoped to the given tenant and carries the roles and custom claims SCIM requires, so the returned bearer token can be pasted straight into an identity provider's SCIM configuration. Existing SCIM keys for the same SSO configuration stay valid. The cleartext is returned exactly once.