Read public-safe metadata about a pending grant
Used by the dashboard authorize page to render Authorize {clientName}?
before the user clicks Approve. Requires the dashboard user to be
authenticated. Does NOT return the grant_code — only the metadata
that’s safe to display in a logged-in browser.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
The user_code from the URL ?code= query param.
Response
Grant metadata.
Response from GET /auth/grant/peek?user_code=.... Used by the dashboard
authorize page to render Authorize {clientName}? before the user clicks
Approve. Does NOT return the grant_code — only the public-safe metadata.
Type of first-party client being authorized. cli for the dyn CLI,
mcp for an MCP server, demo for demo applications oauth-ing into
redcoast, ide-plugin for editor extensions, and other as a catch-all.
cli, mcp, demo, ide-plugin, other Optional metadata sent at grant request time so the authorizing user can recognize the client in the management UI. Every field is optional — a CLI may know its hostname, an embedded MCP server may not.
CF-geolocated city, region, country of the /auth/grant/code
requester. Omitted off-edge (preview / local).
256CF-geolocated city, region, country of the dashboard user
viewing the consent screen. Omitted off-edge.
256true when both cf-ipcountry values are known and differ.
Omitted (not false) when either country is unknown — callers
must treat omitted as "do not warn".