Retrieve application OAuth credentials
Returns the Cognito clientId, tokenUrl, and currently-authorized
scopes for the App, wrapped under a productionCredentials envelope
(and a sandboxCredentials envelope when provisioned), plus
sandboxStatus. No secret is ever returned by this endpoint, by Cognito
design.
sandboxStatus is pending when the sandbox side has not been
provisioned, awaiting_secret_claim when the sandbox exists but the
developer has not yet collected its secret (call
POST /applications/1.0/{sourcedApplicationId}/credentials/rotate to
receive a claim URL without rotating production), and provisioned
when the sandbox credentials have been issued.
If you lost a client secret, call
POST /applications/1.0/{sourcedApplicationId}/credentials/rotate, which
mints a new client + secret and returns a fresh SSO-gated claim URL.
The clientId is stable across draft→active promotion: developers do
NOT need to rotate credentials when their App is approved. Scopes
expand on promotion; client identity does not. (Rotation is a separate,
developer-initiated event where the clientId does change.)
The caller must hold the app:read_credentials grant on urn:app:<appId>.
The grant is issued to the App’s creator at registration time.
Authorizations
OAuth 2.0 client credentials flow. Contact timeback@trilogy.com to request credentials for your application.
Path Parameters
UUID of the App whose credentials are being retrieved
Response
App credentials
Response from GET /applications/1.0/{appId}/credentials. The credential
fields are wrapped under productionCredentials so a future sandboxCredentials
sibling envelope can be added without breaking this response.
clientSecret is intentionally absent: Cognito does not allow reading the
secret back after creation. It is surfaced exactly once on the
POST /applications/1.0/drafts response; if you did not save it then,
contact TimeBack support.
The clientId is stable across draft→active promotion: developers do NOT
need to rotate credentials when their App is approved. Scopes expand on
promotion; client identity does not.
Canonical URN identifying your registered application.
Format: urn:uuid:{applicationId} (RFC 4122). Use this value as Caliper
edApp.id when emitting events from your app.
^urn:uuid:[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"urn:uuid:53f0d94d-786d-409a-b5eb-7a6c1db8957b"
Unique identifier of the App whose credentials are returned.
OAuth credentials for the App on the production Cognito user pool.
The same client is used in both draft and active App states — scopes
expand on promotion but clientId, tokenUrl, and shape do not change.
A future sandboxCredentials sibling envelope will carry sandbox-pool
credentials when the sandbox Cognito pool exists.
Sandbox-pool credentials (no secret). Null when the App is sandbox-pending.
pending when the sandbox side has not been provisioned; awaiting_secret_claim
when the sandbox exists but the secret has not been issued (call rotate_credentials
to collect it without rotating production); provisioned when the sandbox
credentials have been issued.
pending, awaiting_secret_claim, provisioned