Submit Notice Text Content for Approval
A 4-step recipe with Didomi. We can help you get access.
Recipe · 4 steps
Submit Notice Text Content for Approval
with Didomi · Privacy & Data Protection Management
Create a notice text, submit a content version, and read its approval status.
- Create a notice text. organization_id and name are both required by the NoticeTextInput schema.
- Submit a content version against the new text. content, organization_id and text_id are required by the NoticeTextContentInput schema. The content enters the Didomi approval process and is assigned a content version.
- Read the content back by its ID and branch on its approval status: approved content ends the flow while submitted content is polled once more.
- Re-read the content to poll its approval status when it was still submitted and awaiting review by the Didomi team.
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 text and content.
- textName: Name used to distinguish this notice text in your account.
- content: The actual text content to submit for approval.
- includesPurposes: Whether the content includes a complete list of purposes.
For your developer
Arazzo workflow didomi:submit-notice-text-content, 4 operations: {$sourceDescriptions.noticesApi.url}#/paths/~1widgets~1notices~1texts/post → {$sourceDescriptions.noticesApi.url}#/paths/~1widgets~1notices~1texts-contents/post → {$sourceDescriptions.noticesApi.url}#/paths/~1widgets~1notices~1texts-contents~1{id}/get → {$sourceDescriptions.noticesApi.url}#/paths/~1widgets~1notices~1texts-contents~1{id}/get. Specs on APIs.io.