Skip to main content
GET
Read an MCP consent request
A signed-in human session is required. API keys and MCP bearer credentials cannot replace that session. Reads the client and requested authorization for the signed-in human’s approval screen. Request conventions · API keys · MCP connections

Authorizations

posted_session
string
cookie
required

Signed-in human browser session; mutation requests also need the exact UI Origin

Path Parameters

id
string<uuid>
required

The id from the corresponding list, record or authorization response.

Response

Successful response. Examples are illustrative; field values vary by record.

clientName
string
clientId
string
clientTrust
string
redirectUri
string
scope
string
expiresIn
integer
user
object
availableAccessLevels
string[]
canApprove
boolean