API ReferenceManagementInbound Apps
POST
/v1/mgmt/thirdparty/app/secret/add

Authorization

Descope Project ID and Management Key
AuthorizationBearer <token>

Project ID:Management Key as bearer token.

In: header

Request Body

application/json

id*string
Length1 <= length <= 254
name*string
Length1 <= length <= 100
expireTime?integer
Formatint32

Add a new named client secret to a third party application, using a valid management key. Returns the new secret metadata and its cleartext value (shown only once).

curl -X POST "https://api.descope.com/v1/mgmt/thirdparty/app/secret/add" \  -H "Content-Type: application/json" \  -d '{    "id": "string",    "name": "string"  }'
{  "meta": {    "id": "string",    "name": "string",    "status": "string",    "expireTime": 0,    "createdTime": 0  },  "cleartext": "string"}
export interface Response {meta?: {id?: stringname?: stringstatus?: stringexpireTime?: numbercreatedTime?: number}cleartext?: string}
Was this helpful?

Batch delete third party applications POST

Delete multiple third party applications in batch, using a valid management key.

Create third party application consent POST

Create a user consent for a third party application, using a valid management key. Use it to migrate consents a user already granted elsewhere, so the user is not asked to consent again. The scopes are added to any existing consent of the user for the same application and tenant. The consent is validated like one granted on the consent screen: every scope must be defined by the application, the mandatory scopes of the application must be included (all of its scopes when it does not allow partial scopes), and the user must hold the roles and permissions the scopes map to. Consents of agentic applications cannot be created.