auth-oauth
Authorize Complete
User finished the /connect page — mint a short-lived code and return the redirect URL.
Auth: the user must be signed in (Clerk session cookie validated by the existing get_principal dependency). PKCE parameters and the redirect_uri come straight from the original client request via the keel-app page; we re-validate redirect_uri server-side.
Redirect validation, two mutually exclusive paths:
- CIMD client (client_id is an HTTPS URL): fetch the metadata document; its redirect_uris are AUTHORITATIVE for this client.
- otherwise: the hardcoded static allow-list.
The response redirect carries RFC 9207 iss (always) and honours an RFC 8707 resource indicator when the client sent one.
post/v1/auth/oauth/authorize-complete
Request
- Base URL: https://api.usekeel.io (the document declares no server; this is the origin it was published from)
- URL: https://api.usekeel.io/v1/auth/oauth/authorize-complete
- Auth: none declared
Headers
Authorizationstring nullable
X-Org-Idstring nullable
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.