Actions75
- Compliance Report Actions
- Consent And Preference Actions
- Data Manager Actions
- Add Preference Into Your Configuration Tree
- Add Purpose Into Your Configuration Tree
- Create Preference
- Create Purpose
- Delete Preference
- Delete Purpose
- Delete Selected Preference
- Delete Selected Purpose
- Get Available Regulations and Related Information
- Get Configuration Tree
- Get Preference
- Get Purpose
- Get Vendor
- List Preferences
- List Purposes
- List User Rights
- List Vendors
- Update Preference
- Update Purpose
- Privacy Request Actions
- Widget Actions
- Create Authentication Provider
- Create Consent Notice
- Create Widget
- Delete Widget
- Get Archived Widget
- Get Current Draft Configuration For Notice
- Get Custom Theme
- Get Deployment
- Get Entity
- Get Widget
- List Archived Widget
- List Custom Themes
- List Deployments
- List Entities
- List Widgets
- Publish Current Draft Configuration For Notice
- Publish Widget
- Set Default Authentication Provider
- Update Component
- Update Current Draft Configuration For Notice
- Update Custom Theme
- Update Entity
- Update Multiple Components
- Update Multiple Entities
- Update Widget
Consent And Preference → Upload Proof
AI-generatedOverview
This node operation uploads a proof related to user consent and preferences to the Didomi API. It is useful in scenarios where you need to programmatically submit proof documents or evidence associated with user consents, such as compliance audits or legal verifications.
Use Case Examples
- Uploading a proof document for a user's consent event to ensure compliance with data privacy regulations.
- Submitting evidence of user consent for audit purposes in a privacy management workflow.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional parameters to customize the upload request, such as filtering or additional metadata. |
| Request Body | JSON object containing the proof data to be uploaded. |
Output
JSON
response- Response data from the Didomi API after uploading the proof.
Dependencies
- Didomi API credentials including API Key and API Secret for authentication.
Troubleshooting
- Ensure that the API Key and API Secret credentials are correctly configured; missing credentials will cause authentication failures.
- Verify that the request body contains valid JSON data representing the proof to upload; malformed JSON will cause request errors.
- Check that the endpoint URL is correctly constructed; missing required parameters like proof ID will cause errors.
- Common error messages include missing required IDs (e.g., Proof ID) or authentication token retrieval failures; resolving these involves providing the necessary parameters and valid credentials.