Read your own registration with your app key
The self-read: the app’s own registration, answered to the credential the app already holds. Registration metadata only — the values the developer registered, plus the console origin and endpoint paths an SDK needs to run the whole handshake without being separately configured with any of them.
Authorizations
A Connect app key (pgc_app_…), identifying the registered third-party app. Always presented together with connectGrant — the pair is one credential, and either half alone is refused. Accepted on the /connect/* surface only.
Response
The registration, as the key's holder may see it
The self-read (GET /connect/apps/me): registration metadata plus the discovery an SDK boots from, and nothing else.
What your customers' consent page shows as "… wants access".
Which world a Connect app lives in. sandbox — the Durango demo bank, where nothing is money; a sandbox app may declare only DURANGO agents and its credentials are minted as pgc_app_test_… / pgc_grant_test_…. live — everything else; a live app cannot declare DURANGO agents.
sandbox, live The registered list, exactly as authorize and the exchange will byte-compare it. This is the value an SDK should derive its callback handling from, in place of a separately configured copy.
When this registration ages out. An SDK's doctor check warns from this; renewing is a console (session) action.
The consumer console's origin — where consent and approvals are collected. The same configuration approval URLs are minted from, and null under the same missing configuration.
The consent page on that origin. Null when consoleOrigin is.
Path of the token exchange, relative to this server's origin.
Path of the served tool definition, relative to this server's origin.

