ReferenceOAuth consent and connected apps
The consent page's view of an authorization request: the client, the gateway and where the browser goes back to
GET
/v1/oauth/consentTakes the authorization request's parameters as they are and checks them again (signed-in session required). 400 with the reason for a request that isn't valid (the page shows it and never redirects). 404 when the resource names no gateway the caller can use.
Query Parameters
client_id*string
redirect_uri*string
response_type*string
code_challenge*string
code_challenge_method*string
resource*string
state?string
scope?string
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/oauth/consent?client_id=string&redirect_uri=string&response_type=string&code_challenge=string&code_challenge_method=string&resource=string"{ "data": { "client": { "id": "string", "kind": "metadata", "name": "string", "host": "string", "uri": "string", "logoUrl": "string", "trusted": true }, "gateway": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "slug": "string", "name": "string", "description": "string", "ownerKind": "team", "teamSlug": "string", "teamName": "string", "url": "string", "access": [ "team_member" ], "groups": [ "string" ], "capabilityCount": 0, "capturesPayloads": true, "needsPersonCount": 0 }, "redirectUri": "string", "redirectHost": "string", "remembered": true }}