Authorize an App
Completes the OAuth authorization step for the authenticated user: records their consent to the scopes an app asked for and mints an authorization code. Returns the grant plus a redirect_url carrying the code, which is returned only this once; the app exchanges it at POST /oauth/token. Requires a user session, because consent has to come from the account holder: an API key or an OAuth token is refused, so an app can never authorize itself. Send an Idempotency-Key so a retry returns the original redirect_url and code instead of issuing a second one.
Authorizations
Only available to a signed-in whop.com session. API keys, access tokens, and OAuth tokens are not accepted.
Headers
A unique key that makes this request safe to retry. See Idempotent requests.
255"d9105228-4a08-46b1-8b91-42fed586d383"
Pins the request to a dated API version.
"2026-10-15-1"
Body
The app being authorized, prefixed app_.
"app_xxxxxxxxxxxxxx"
Where to send the user once they have consented. Must match one of the app's registered redirect URIs exactly — it is compared as a string, not normalized.
"https://Booking.Shinetime.example:8443/oauth/Callback/"
The permissions the app is asking for, for example member:basic:read. GET /api_keys/permissions names and describes each one. Granting adds to whatever the user already granted this app rather than replacing it.
Authorize the app for one of the user's accounts rather than for the user alone, prefixed biz_. The user must have access to it.
"biz_xxxxxxxxxxxxxx"
The PKCE code challenge: the base64url-encoded SHA-256 of your code verifier, without padding. Required unless the app is confidential; a confidential app that leaves it out redeems the code with its secret instead of a verifier.
"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
How code_challenge was derived. Only S256 is accepted. Required with code_challenge.
S256 "S256"
Whether the consent UI listed these scopes for the user. Sending false succeeds only when the user has already granted every scope requested, or when the app is one of Whop's own with the consent skip switched on and asks for openid alone.
true
The downstream MCP client displayed on the consent screen. Requires explicit consent even when the upstream app already has a grant. Bound to the authorization code and returned on token exchange so the MCP server can verify the approved client.
OIDC nonce, echoed into the resulting ID token. Required when requested_scopes includes openid.
"n-0S6_WzA2Mj"
The OAuth response type. Only code is accepted; defaults to code.
code "code"
Opaque value appended to redirect_url unchanged, for the client to correlate the response with its request.
"opaque-client-state"
Response
the app is authorized
The account the grant is scoped to, prefixed biz_. null when the user authorized the app for themselves rather than for one of their accounts.
"biz_xxxxxxxxxxxxxx"
The app this grant authorizes, prefixed app_.
"app_xxxxxxxxxxxxxx"
When the user last authorized the app, as an ISO 8601 timestamp.
"2026-01-01T12:00:00.000Z"
When the user first authorized the app, as an ISO 8601 timestamp.
"2026-01-01T12:00:00.000Z"
Grant ID, prefixed oag_.
"oag_xxxxxxxxxxxxxx"
When the grant was revoked, as an ISO 8601 timestamp, or null while it is still in force. A revoked grant authorizes nothing — treat its scopes as no longer granted.
"2026-01-01T12:00:00.000Z"
Every permission the user has granted this app, accumulated across authorizations, for example member:basic:read. GET /api_keys/permissions names and describes each one.
Where to send the user to finish the flow: the redirect_uri you supplied with the authorization code appended, and state when you supplied one. Its scheme, host, port, and path come back exactly as sent — never re-cased or re-encoded — because the client matches them against its registered URI. Returned only once, on create: the code is single-use and expires 10 minutes after it is issued, so redirect immediately.
"https://Booking.Shinetime.example:8443/oauth/Callback/"

