capabilities.work

Upload and Verify a Consent Proof

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

Recipe · 2 steps

Upload and Verify a Consent Proof

with Didomi · Privacy & Data Protection Management

Upload a consent proof file for an organization and read it back by ID.

  1. Upload the base64-encoded file to serve as proof of consent for the organization. The file field is required by the ConsentProof input schema.
  2. Retrieve the uploaded proof by its ID, scoped to the same organization, to verify that it was persisted.
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 proof belongs to.
  • file: Base64-encoded data URI of the proof file (PDF, PNG, JPG, GIF, DOCX or DOC).
For your developer

Arazzo workflow didomi:upload-consent-proof, 2 operations: {$sourceDescriptions.consentsProofsApi.url}#/paths/~1consents~1proofs/post → {$sourceDescriptions.consentsProofsApi.url}#/paths/~1consents~1proofs~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 RequestDeploy a Consent NoticeGroup 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 Cookie