For AI agents: the documentation index is at /llms.txt, and this page is available as Markdown at /api/auth/oauth-authorize.md.

Start an authorization request

GET
/oauth/authorize

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.

Where a failure is reported depends on what failed. An unknown client or an unregistered redirect_uri is answered here, because the only target we could redirect to is the one we just refused to trust. Everything else redirects back to the client with error and state (RFC 6749 4.1.2.1).

PKCE is required and code_challenge_method must be S256.

Query Parameters

client_id*string
redirect_uri*string

Must match one the client registered, byte-for-byte outside loopback.

Formaturi
response_type*"code"
Value in"code"
code_challenge*string

base64url SHA-256 of the client's code verifier.

code_challenge_method*"S256"
Value in"S256"
resource*string

RFC 8707 resource indicator; becomes the access token's audience.

Formaturi
scope?string

Space-delimited. Defaults to every scope the client registered for.

state?string

Echoed back unchanged so the client can detect an unsolicited response.

Response Body

Redirect to the consent screen, or back to the client's redirect_uri carrying error and state.

Example Request
curl -X GET 'https://api.truemarkets.co/v1/auth/oauth/authorize?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'
Example Response
Empty