v1/mgmt/thirdparty/app/createAuthorization
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 is the structured scope→claim model. Consumed by CreateThirdPartyApplicationV2 (v2 write-replace: attributesScopes is ignored/cleared). v1 ignores this field.
clientAuthMethod: "clientSecret" (default when empty) or "privateKeyJwt" (only clientAssertions are accepted).
clientAssertions are the private_key_jwt trust entries (JWKS URL or PEM public key per entry).
Create a new third party application, using a valid management key.
curl -X POST "https://api.descope.com/v1/mgmt/thirdparty/app/create" \ -H "Content-Type: application/json" \ -d '{}'{ "id": "string", "cleartext": "string", "clientId": "string"}export interface Response {id?: stringcleartext?: stringclientId?: string}