v1/mgmt/scim/key/revokeAuthorization
Descope Project ID and Management Key Project ID:Management Key as bearer token.
In: header
Request Body
application/json
1 <= lengthThe SSO configuration to revoke. Omit it to target the tenant's default configuration - it does NOT mean "every configuration", so a tenant with several SSO configurations keeps provisioning through the keys of the ones not named here. Call LoadSCIMAccessKeys first to see which configurations hold keys.
length <= 254How the keys are taken out of service. SCIM_KEY_REVOKE_MODE_DELETE (0, the default) deletes them permanently. SCIM_KEY_REVOKE_MODE_DEACTIVATE (1) disables them reversibly, so they can be restored later with Activate SCIM Access Keys.
enum"SCIM_KEY_REVOKE_MODE_DELETE" | "SCIM_KEY_REVOKE_MODE_DEACTIVATE"Revoke every SCIM access key of a tenant for the given SSO configuration, using a valid management key. This disables SCIM provisioning for that tenant until a new key is created and configured in the identity provider. Use revokeMode DEACTIVATE to suspend the keys reversibly instead of deleting them.
curl -X POST "https://api.descope.com/v1/mgmt/scim/key/revoke" \ -H "Content-Type: application/json" \ -d '{ "tenantId": "string" }'{ "revokedKeyIds": [ "string" ]}export interface Response {revokedKeyIds?: string[]}Load SCIM Access Keys GET
Load the SCIM access keys of a tenant, using a valid management key. Returns key metadata only - the cleartext of an access key is available exactly once, when the key is created or rotated, and is never returned again.
Rotate SCIM Access Key POST
Rotate the SCIM access keys of a tenant, using a valid management key. A new key is created and the tenant's existing SCIM keys for the same SSO configuration are revoked, either deleted or deactivated according to revokeMode. Update the identity provider with the new bearer token immediately - until you do, SCIM provisioning for that tenant will fail. The cleartext is returned exactly once.