Polled by the client to check whether the grant has been approved or
denied. Public — the grant_code itself is the proof of identity.
Status follows RFC 8628 conventions: authorization_pending,
slow_down, approved, access_denied, expired_token. On
approved, the response includes the minted client JWT.
curl --request POST \
--url https://app.dynamicauth.com/api/v0/auth/grant/token \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"grant_code": "<string>"
}
'{
"status": "authorization_pending",
"jwt": "<string>",
"token_type": "<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.
Request body for POST /auth/grant/token.
Current grant state. See status for details.
Response from POST /auth/grant/token. The status field follows
RFC 8628's "error-via-200" convention so the client can branch its polling
loop on status without interpreting HTTP error codes.
Was this page helpful?
curl --request POST \
--url https://app.dynamicauth.com/api/v0/auth/grant/token \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"grant_code": "<string>"
}
'{
"status": "authorization_pending",
"jwt": "<string>",
"token_type": "<string>"
}