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.
curl --request GET \
--url https://app.dynamicauth.com/api/v0/auth/grant/peek \
--header 'Authorization: Bearer <token>'{
"client_type": "cli",
"client_metadata": {
"name": "<string>",
"version": "<string>",
"hostname": "<string>",
"os": "<string>"
}
}Documentation Index
Fetch the complete documentation index at: https://www.dynamic.xyz/docs/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The user_code from the URL ?code= query param.
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.
Show child attributes
Was this page helpful?
curl --request GET \
--url https://app.dynamicauth.com/api/v0/auth/grant/peek \
--header 'Authorization: Bearer <token>'{
"client_type": "cli",
"client_metadata": {
"name": "<string>",
"version": "<string>",
"hostname": "<string>",
"os": "<string>"
}
}