For AI agents: the documentation index is at /llms.txt, and this page is available as Markdown at /api/auth/oauth-authorize-details.md.
Describe an authorization request
What the consent screen renders: who is asking, for what, and whether we vouch for the name.
It validates the same request /oauth/authorize did, so the screen
cannot be made to describe a grant that would not actually be issued.
unverified is true for a client that registered itself and chose its
own name. redirect_host is shown beside the name because the host is
the part a client cannot assert freely.
client_id*stringredirect_uri*stringuriresponse_type*"code""code"code_challenge*stringcode_challenge_method*"S256""S256"resource*stringuriscope?stringstate?stringThe request as the consent screen should present it
application/json- response
client_id*stringclient_name*stringAlways the client's own claim; the callback host is not.
redirect_host*stringHost of the callback this grant would be returned to.
scopes*array<string>vendor*stringThe allowlist family whose rule admitted this client.
verification*stringWhat the authorization server can vouch for, based on where the
grant is delivered rather than on the name. vendor — the callback
belongs to a recognised host, so only that vendor can receive the
code. local — a loopback callback, so a program on the user's own
machine, which cannot be identified further.
"vendor""local"dynamically_registered*booleanTrue for a self-registered client, whose name is its own unvetted claim; the consent screen labels the name accordingly.
curl -X GET 'https://api.truemarkets.co/v1/auth/oauth/authorize/details?client_id=string&redirect_uri=http%3A%2F%2Fexample.com&response_type=code&code_challenge=string&code_challenge_method=S256&resource=http%3A%2F%2Fexample.com'{ "client_id": "string", "client_name": "string", "redirect_host": "string", "scopes": [ "string" ], "vendor": "string", "verification": "vendor", "dynamically_registered": true}