Credentials
Client secrets: issue, list, revoke, and remove the record of a revoked one.
4 routes
A secret is shown once, on creation. Issuing one is a passkey-confirmed action in the console session.
The guide for this family is Environments and credentials.
GET /v1/developer/applications/{applicationId}/credentials
GET /v1/developer/applications/{applicationId}/credentialsAuthentication- Developer console session
POST /v1/developer/applications/{applicationId}/credentials/oauth-client-secret
POST /v1/developer/applications/{applicationId}/credentials/oauth-client-secretAuthentication- Developer console session
Request body — CreateOAuthSecretDto
namerequiredstring— IsString, IsNotEmpty, MaxLength(100)overlapHoursoptionalnumber— IsInt, Min(1), Max(72)
DELETE /v1/developer/applications/{applicationId}/credentials/oauth-client-secret/{credentialId}
DELETE /v1/developer/applications/{applicationId}/credentials/oauth-client-secret/{credentialId}Authentication- Developer console session
DELETE /v1/developer/applications/{applicationId}/credentials/oauth-client-secret/{credentialId}/record
DELETE /v1/developer/applications/{applicationId}/credentials/oauth-client-secret/{credentialId}/recordAuthentication- Developer console session
What this does not do
- Responses are not listed. The API declares no response types, so this page describes what to send and who may send it. Recorded response shapes are on the guides.
- This page is generated. It was read from the API at commit
234dba22. Editing it by hand changes nothing; the next sync overwrites it.
Verified against API commit 234dba22 on 2026-10-18. The routes, scopes, checklist, events and limits on these pages are read from that export, not typed.