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
Data Manager → Delete Purpose
AI-generatedOverview
This node operation deletes a specific purpose in the Didomi Data Manager. It is useful for managing user data and privacy preferences by removing purposes that are no longer relevant or needed. For example, if a company wants to remove a data processing purpose from their configuration, this operation facilitates that deletion via the Didomi API.
Use Case Examples
- Deleting a purpose by specifying its Purpose ID to ensure it is no longer available in the data management system.
- Automating the cleanup of outdated or deprecated purposes in a privacy management workflow.
Properties
| Name | Meaning |
|---|---|
| Purpose ID | The unique identifier of the purpose to be deleted. This is required to specify which purpose to remove. |
| Query Parameters | Optional parameters to refine the API request, such as filtering or pagination options. These include flags and identifiers like organization user ID, cursor, limit, status, and others as defined in the node properties. |
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 with API Key and Secret for authentication
Troubleshooting
- Missing Purpose ID will cause an error indicating that the Purpose ID is required.
- Failure to retrieve an access token from the Didomi API will result in an error preventing the operation from proceeding.
- API errors during the delete request will be caught and reported with the message 'Error calling Didomi API' along with the error details.
Links
- Didomi API Delete Purpose - Official API documentation for deleting a purpose in Didomi Data Manager.