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
Privacy Request → Update Request
AI-generatedOverview
This node operation updates an existing privacy request in the Didomi API. It is useful for managing user privacy requests such as data access, deletion, or opt-out requests by modifying their details or status. For example, it can be used to update the status of a privacy request or change its associated data based on new information or user actions.
Use Case Examples
- Updating the status of a privacy request to 'completed' after processing.
- Modifying the details of a privacy request to correct user information or add notes.
Properties
| Name | Meaning |
|---|---|
| Request ID | The unique identifier of the privacy request to update. |
| Query Parameters | Optional parameters to filter or modify the request, such as status, limit, or organization ID. |
Output
JSON
json- The updated privacy request data returned from the Didomi API.
Dependencies
- Didomi API key and secret credentials for authentication.
Troubleshooting
- Missing or invalid API key or secret will cause authentication failure.
- Omitting the required Request ID will result in an error indicating the missing parameter.
- API errors from Didomi will be wrapped and reported as NodeApiError with details.
- Ensure the request body JSON is correctly formatted to avoid request errors.
Links
- Didomi API Documentation - Update Privacy Request - Official API reference for updating a privacy request in Didomi.