capabilities.work

Issue a Consent Token for an End User

A 3-step recipe with Didomi. We can help you get access.

Recipe · 3 steps

Issue a Consent Token for an End User

with Didomi

Create a user, assign an internal ID, and issue a scoped consent token for that user.

  1. Create a new end user under the organization. organization_id is supplied as a required query parameter.
  2. Patch the user to assign your organization's internal user ID so the token can be scoped to that ID.
  3. Issue a consent token scoped to the user and organization. organization_id, organization_user_id and lifetime are all required by the ConsentToken input schema.
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 that the user and token belong to.
  • organizationUserId: Your organization's internal user ID to assign to the new user.
  • lifetime: Lifetime of the issued consent token, in seconds.
For your developer

Arazzo workflow didomi:issue-consent-token, 3 operations: {$sourceDescriptions.consentsUsersApi.url}#/paths/~1consents~1users/post → {$sourceDescriptions.consentsUsersApi.url}#/paths/~1consents~1users~1{id}/patch → {$sourceDescriptions.consentsTokensApi.url}#/paths/~1consents~1tokens/post. Specs on APIs.io.

More recipes with Didomi

Classify a Vendor and Register a CookieCreate a Consent User and Assign an Internal IDCreate and Verify a Privacy CenterData Subject Erasure RequestDeploy a Consent NoticeGroup Notices Under a TemplateProvision an Organization and Invite a MemberRecord a Consent Event and Confirm StatusRegister and Verify a CookieSubmit Notice Text Content for Approval