For AI agents: the documentation index is at /llms.txt, and this page is available as Markdown at /api/auth/oauth-consent.md.
Record a consent decision
The signed-in user's answer to the consent screen. Approving records
the grant and mints an authorization code; denying returns the client
to its redirect with error=access_denied.
The authorize parameters are repeated here and validated again, because nothing but the user's browser carries them between the two requests.
Returns where the browser should go rather than redirecting, since the consent screen issues this as a fetch.
Rate limit: counts against the Keys and credentials limit, 10 a minute and 50 a day (user token, per user); 100 a minute and 500 a day (organization api key, per organization). See Rate limits.
bearerAuthAuthorizationBearer <JWT>An access token from POST /api-key/token. An organization token lasts one hour and has no refresh token; a personal token can be refreshed.
application/json- body
approved?booleanFalse returns the client to its redirect with access_denied.
client_id*stringredirect_uri*stringuriresponse_type*"code""code"scope?stringstate?stringcode_challenge*stringcode_challenge_method*"S256""S256"resource*stringuriDecision recorded
application/json- response
redirect_to*stringWhere the browser should go next, approved or denied.
uricurl -X POST 'https://api.truemarkets.co/v1/auth/oauth/consent' \ -H 'Content-Type: application/json' \ -d '{ "client_id": "string", "redirect_uri": "http://example.com", "response_type": "code", "code_challenge": "string", "code_challenge_method": "S256", "resource": "http://example.com"}'{ "redirect_to": "http://example.com"}Start an authorization request GET
The authorization endpoint (RFC 6749 4.1.1). A valid request is redirected to the consent screen with its parameters intact; the signed-in user's decision comes back through /oauth/consent.
Exchange a grant for tokens POST
The token endpoint (RFC 6749 4.1.3 and 6), form encoded.