Get Consent Context

GET /oauth/consent

What the consent screen renders: who is asking, for what, and which anchors this person may hand over. Reading it grants nothing — approving is a separate call.

The parameters are optional-then-required for the reason authorize gives.

Role floor

Requires viewer or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
client_id	query	string | null	optional	—
redirect_uri	query	string | null	optional	—
code_challenge	query	string | null	optional	—
response_type	query	string	optional	Default "code".
code_challenge_method	query	string	optional	Default "S256".
scope	query	string | null	optional	—
state	query	string | null	optional	—
resource	query	string | null	optional	—

Responses

Status	Description	Body
200	Successful Response	—
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X GET https://your-deployment.example.com/oauth/consent \
  -H "Authorization: Bearer $COBRE_TOKEN"