GET /v1/oauth/authorize

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/oauth/authorize?response_type=<response_type>&client_id=<client_id>&redirect_uri=<redirect_uri>&code_challenge=<code_challenge>&code_challenge_method=<code_challenge_method>

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Validates the client (a registered zoc_… id, or a Client ID Metadata Document URL), the exact redirect URI and the PKCE S256 challenge, then redirects the browser to the dashboard consent page. A bad client or redirect URI is answered here with 400 and is never redirected (no open redirector); every other error goes back to the client's redirect URI with error, state and iss. Unauthenticated (the consent page signs the person in).

Parameters

Errors this endpoint can return

400 · 503