capabilities.work

Deploy a Consent Notice

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

Recipe · 3 steps

Deploy a Consent Notice

with Didomi · Privacy & Data Protection Management

Create a notice then deploy a notice configuration to production for an organization.

  1. Create a new consent notice owned by the organization. Only the organization_id and name are required by the NoticeInput schema.
  2. Deploy the supplied production notice configuration for the new notice. notice_id, organization_id and production_config_id are all required by the NoticeDeploymentInput schema.
  3. Read the deployment back by its ID to confirm it was registered.
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 owns the notice and deployment.
  • noticeName: Internal name of the notice used to distinguish it in your account.
  • productionConfigId: The ID of the notice configuration to deploy to production.
  • deploymentMessage: Optional human-readable description of the deployment content.
For your developer

Arazzo workflow didomi:deploy-notice, 3 operations: {$sourceDescriptions.noticesApi.url}#/paths/~1widgets~1notices/post → {$sourceDescriptions.noticesApi.url}#/paths/~1widgets~1notices~1deployments/post → {$sourceDescriptions.noticesApi.url}#/paths/~1widgets~1notices~1deployments~1{id}/get. 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 RequestGroup Notices Under a TemplateIssue a Consent Token for an End UserProvision an Organization and Invite a MemberRecord a Consent Event and Confirm StatusRegister and Verify a CookieSubmit Notice Text Content for Approval