Approve or deny an OAuth2 authorization (mints the code)
Called by the web consent screen AFTER a signed-in user approves (or denies). It re-validates the client_id, exact redirect_uri, requested scope (subset of the client’s max ∩ ValidScopes), state and optional PKCE server-side — the query params carried through the browser are untrusted — and confirms the user is acting as the org being authorized (orgId == the token’s active org). On approve it mints a single-use, 10-minute authorization code and returns the redirectTo URL (redirect_uri?code=…&state=…); on deny it returns redirect_uri?error=access_denied. HUMAN-ONLY: a service principal (API key or OAuth token) is rejected with 403 even if scoped.
Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
Body
The registered OAuth client id.
Must EXACTLY match a registered redirect URI.
Opaque CSRF value echoed back to the client.
The org to authorize; must equal the caller's active org.
true to grant
Space-separated requested scopes (subset of the client max).
Optional PKCE challenge (S256).
PKCE method; S256 only.
S256