Approve or deny an OAuth interaction

Used by the login and consent application. Requires the signed-in user's Wingspan session token as a bearer token, an Origin header from the consent application, and the decisionNonce returned by POST /v3/platform/oauth/authorize-context. Records whether the user approved or denied the interaction. When approved, the request names the accountId and roleScope being granted, and a consent grant is created. Always returns 200. The result is either a Redirect (to the client's registered redirect URI, with an authorization code on approval or an error such as access_denied on denial) or a DirectError. The application then sends the user agent to that redirect. The response is not cacheable.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required
string
required
boolean
required
string
^(?:[A-Za-z0-9_.]{22}|[a-f0-9]{24})$

Account identifier. Newly created V3 Accounts use a 22-character Wingspan ID; migrated Accounts may retain a 24-character lowercase hexadecimal ID.

string
enum
Headers
string
length between 1 and 255
^[\x21-\x7e]{1,255}$

Optional idempotency token for authenticated POST and PATCH requests. Reusing the same key and body returns the cached response for 24 hours, except credential operations that explicitly document a 409 because one-time secret material is never cached; reusing it with a different body returns 409 IdempotencyKeyConflict. Use 1-255 printable ASCII characters.

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json