Skip to main content
DELETE
Revoke Consent

Overview

Revokes a specific consent for a user. This operation creates a new consent record with revoked status while preserving the original consent record for audit purposes.
Revoking required consents (e.g., termsAndPrivacy) will change the user’s overall consent status to incomplete, potentially restricting their access to features.

Endpoint

Headers

Path Parameters

Response

200 OK

New Consent Record: Notice the consentId in the response is different from the request. Revocation creates a new record, preserving the original for audit compliance.

404 Not Found

Possible Causes:
  • Consent ID doesn’t exist
  • Consent already revoked
  • Wrong consent set ID

498 Invalid Client Key

499 Missing Client Key

Code Examples

TypeScript

TypeScript - Revoke by Type

Python

cURL

Use Cases

Allow users to opt-out of marketing:
Revoke all consents for account deletion:
Revoke consent based on policy updates:
Revoking consents affects the user’s overall consent status:
Always check the user’s consent status after revocation to determine if access restrictions should be applied.

Best Practices

Check if consent is already revoked:
Send confirmation after revocation:
Warn users about feature impacts:
Track revocation requests:

Get User Consent Status

Check consent status after revocation

Get Consent Audit Trail

View revocation in audit history

Get Consent Set

Retrieve consent set details

Compliance Guide

GDPR/CCPA compliance best practices