Skip to main content
GET
Get a consent by ID

Authorizations

Authorization
string
header
required

Bearer and DPoP tokens are supported depending on the API configuration

Scopes

read:me:consents

Headers

x-correlation-id
string

A client-provided unique identifier for a single operation, used to correlate the request across Auth0 systems. The value is surfaced under references.correlation_id in tenant logs and echoed back on the response's x-correlation-id header. Invalid or oversized values are silently dropped and replaced by a generated UUID v4. Avoid including personally identifiable information (PII).

traceparent
string

A W3C Trace Context header used to correlate the request across distributed traces. When supplied, the inbound trace is continued and a fresh child span is echoed back on the response's traceparent header; the trace ID is also surfaced under references.trace_id in tenant logs. Malformed values are ignored.

Path Parameters

The ID of the consent to retrieve

Response

Successfully retrieved consent

A consent record representing user authorization for a specific client and scope.

id
string
required

The unique identifier of the consent.

Example:

"cns_abc123def456"

client_id
string
required

The client ID that the consent was granted to.

requested_details
object
required

Details of the consent request

created_at
string<date-time>
required

The date and time when the consent was created.

expires_at
string<date-time>
required

The date and time when the consent expires.

challenge
string

The MFA challenge associated with this consent when initiated via push notification. Only present when a push notification was associated.