ReferenceOAuth consent and connected apps
The consent page's view of an app's authorization request (the person signed in)
GET
The query is the authorization request the app sent to /oauth/authorize, unchanged (the platform redirects the browser to the web app's /connect/consent with it). A request that isn't valid is a 400 whose code starts with oauth_ (the page shows the reason and never sends the browser anywhere).
client_id?stringredirect_uri?stringresponse_type?stringcode_challenge?stringcode_challenge_method?stringstate?stringscope?stringresource?stringThe app, where it will send the person back, and what it asks for
application/json- response
data*curl -X GET 'https://agents.example.com/v1/oauth/consent'{ "data": { "client": { "id": "string", "kind": "metadata", "name": "string", "host": "string", "uri": "string", "logoUrl": "string", "trusted": true }, "redirectUri": "string", "redirectHost": "string", "scopes": [ "string" ], "remembered": true, "personalWorkspace": { "slug": "string", "name": "string" } }}