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 → Delete Consent Event
AI-generatedOverview
This node operation deletes a specific consent event in the Didomi system. It is useful for scenarios where you need to remove user consent records, such as when a user withdraws consent or when cleaning up outdated consent data. The operation requires the Consent Event ID to identify which consent event to delete.
Use Case Examples
- Deleting a consent event by providing its unique Consent Event ID to ensure the user's consent record is removed from the system.
- Automating the cleanup of consent events that are no longer valid or required.
Properties
| Name | Meaning |
|---|---|
| Consent Event ID | The unique identifier of the consent event to be deleted. This is a required input for the delete operation. |
| Query Parameters | Optional parameters to refine or modify the API request, such as filtering or pagination options. |
Output
JSON
Status Code- HTTP status code indicating the result of the delete operation, e.g., '204 No Content' for successful deletion.
Dependencies
- Didomi API key and secret for authentication
Troubleshooting
- Ensure the Consent Event ID is provided; otherwise, the node throws an error indicating the missing ID.
- Check that the API key and secret credentials are correctly set and valid to avoid authentication errors.
- If the API returns an error, the node throws a NodeApiError with the message from the Didomi API, which should be reviewed for specific issues.
Links
- Didomi API - Delete Consent Event - Official API documentation for deleting a consent event in Didomi.