Skip to main content
POST

Authorizations

Authorization
string
header
required

Bearer and DPoP tokens are supported depending on the API configuration

Scopes

create: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

Body

application/json

The user's decision on a pending consent request.

decision
enum<string>
required

The user's decision on the consent request.

Available options:
approve,
deny
signature
string
required if kid is set

Compact JWS serialization of the signed consent payload, produced by the device. Must be provided together with kid.

kid
string
required if signature is set

Key ID of the registered consent signing key used to produce signature. Must be provided together with signature.

challenge_response
string

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.

Response

The consent decision was recorded successfully.

The result of a consent decision.

The unique identifier of the consent record.

status
enum<string>
required

The updated status of the consent.

Available options:
approved,
denied