Get a consent by ID
Retrieve a specific consent for the authenticated user by ID.
Authorizations
Bearer and DPoP tokens are supported depending on the API configuration
Scopes
Headers
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).
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.
The unique identifier of the consent.
"cns_abc123def456"
The client ID that the consent was granted to.
Details of the consent request
The date and time when the consent was created.
The date and time when the consent expires.
The MFA challenge associated with this consent when initiated via push notification. Only present when a push notification was associated.