Record a Consent Event and Confirm Status
A 3-step recipe with Didomi. We can help you get access.
Recipe · 3 steps
Record a Consent Event and Confirm Status
with Didomi · Privacy & Data Protection Management
Create a consent event for a user and confirm whether it is confirmed or pending approval.
- Create a new consent event that updates the user's consent status for a single purpose. The user.id field is required by the ConsentEventInput schema.
- Read the created event back by its ID and branch on its status: confirmed events end the flow while pending_approval events are polled once more.
- Re-read the event to poll for a confirmed status when the event was still pending approval after creation.
What you'll need to have ready
- token: A valid Didomi JWT used as the bearer token for the Authorization header.
- organizationId: The ID of the organization for which to create the event.
- userId: The Didomi user ID the consent event belongs to (a UUID or mobile advertising ID).
- organizationUserId: Optional unique user ID internal to your organization (email, phone, client ID).
- purposeId: The purpose ID the user is making a consent choice for.
- purposeEnabled: Whether the user has given consent to the purpose.
For your developer
Arazzo workflow didomi:record-consent-event, 3 operations: {$sourceDescriptions.consentsEventsApi.url}#/paths/~1consents~1events/post → {$sourceDescriptions.consentsEventsApi.url}#/paths/~1consents~1events~1{id}/get → {$sourceDescriptions.consentsEventsApi.url}#/paths/~1consents~1events~1{id}/get. Specs on APIs.io.