Skip to main content
POST
Approve or decline a connection request

Authorizations

Authorization
string
header
required

A Cognito access token, issued through the dashboard's own sign-up and sign-in pages (a backend-for-frontend; there is no Cognito Hosted UI) and sent as Authorization: Bearer <jwt>. Dashboard operations require this scheme and cannot be called with an API key, with no exception. GET /v1/usage and GET /v1/limits offered both schemes from 0.8.0; 0.8.1 withdrew that, because the control-plane API serves them alone and its authorizer has no API-key branch. An account_id supplied by the client is ignored; all reads/writes are scoped server-side to the authenticated account.

Path Parameters

request_id
string
required

A pending OAuth authorization request, as the consent page's URL carries it.

Maximum string length: 40
Pattern: ^oar_[a-f0-9]{24}$

Body

application/json
approve
boolean
required

Response

Where to send the browser.

redirect_to
string<uri>
required

The app's redirect, carrying code, state and iss on an approval, or error=access_denied on a refusal.

Maximum string length: 4096
grant_id
string

A connected app — one OAuth grant.

Maximum string length: 40
Pattern: ^oag_[a-f0-9]{24}$