Decide on a consent
Approve or deny a pending consent for the authenticated user. When signature and kid are supplied, the consents service verifies the JWS signature against the user’s registered consent signing key before recording the decision.
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
Body
The user's decision on a pending consent request.
The user's decision on the consent request.
approve, deny Compact JWS serialization of the signed consent payload, produced by the device. Must be provided together with kid.
Key ID of the registered consent signing key used to produce signature. Must be provided together with signature.
Challenge response JWT that the device builds with the Guardian SDK from the consent's challenge. Send it when the consent was initiated through a push notification, to resolve the associated MFA transaction.