What a consent page shows of an assistant’s request
GET
/v1/oauth/requests/{id}
const url = 'https://beta-api.plune.ai/v1/oauth/requests/example';const options = {method: 'GET', headers: {cookie: 'plune_session=<plune_session>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://beta-api.plune.ai/v1/oauth/requests/example \ --cookie plune_session=<plune_session>The request GET /oauth/authorize kept, for 10 minutes: who asks, how the client came to be known, the host the answer returns to (and whether that is this machine), and the right asked for. The signed-in session alone (an API token gets 401): a token, an assistant’s own included, can neither grant a connection nor widen one. Mounted only where the remote MCP server is switched on (MCP_PUBLIC_URL).
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ” id
required
string
The request id the consent page got in ?request=.
Responses
Section titled “ Responses ”The request
Media type application/json
object
id
required
string
client
required
object
name
required
string
kind
required
string
redirectHost
required
string
loopback
required
boolean
scope
required
string
Example
{ "id": "5d6c1f0a-3b1e-4a52-8a53-3c2b7c1f9e11", "client": { "name": "Assistant", "kind": "registered" }, "redirectHost": "assistant.example", "loopback": false, "scope": "write"}No / invalid session
Unknown, already answered or older than 10 minutes
Media type application/json
object
error
required
string
Example
{ "error": "the request is unknown, already answered or older than 10 minutes", "code": "request_gone"}