/v1/mgmt/thirdparty/app/patchAuthorization
Descope Project ID and Management Key Project ID:Management Key as bearer token.
In: header
Request Body
application/json
string backChannelLogoutUrl = 10 [(validate).string = {url: true, optional: true}];
Custom attributes as key-value pairs. Keys must be strings; values can be strings, numbers, booleans, or arrays.
{
"attribute-key": "attribute-value"
}JAR (JWT-Secured Authorization Request, RFC 9101) settings for Third Party Applications
scopeClaimMapping replaces the stored mapping when provided; when absent the existing mapping is preserved. Consumed by PatchThirdPartyApplicationV2; v1 preserves the legacy attributesScopes.
idJagTargetClients replaces the stored mapping when provided. An absent field preserves it, and so does an empty map: a protobuf map has no presence, so it reaches the service as nil after the gRPC hop. Clear the mapping through the full update, which always writes the field.
Patch a third party application, using a valid management key.
curl -X POST "https://api.descope.com/v1/mgmt/thirdparty/app/patch" \ -H "Content-Type: application/json" \ -d '{}'