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 → Update Preference
AI-generatedOverview
This node operation updates a user preference in the Didomi Data Manager via the Didomi API. It is useful for scenarios where you need to modify existing user preferences related to data management, such as updating consent or privacy settings. For example, it can be used to change a preference's attributes or status based on new user input or compliance requirements.
Use Case Examples
- Updating a user's data preference to reflect new consent choices.
- Modifying preference details to comply with updated privacy regulations.
Properties
| Name | Meaning |
|---|---|
| Preference ID | The unique identifier of the preference to update. |
| Query Parameters | Optional parameters to filter or modify the request behavior, such as pagination or filtering by organization user ID. |
| Request Body | The JSON body containing the updated preference data to send in the PATCH request. |
Output
JSON
Status Code- HTTP status code or message when no content is returned*- The JSON response from the Didomi API representing the updated preference details
Dependencies
- Didomi API with API Key and API Secret credentials
Troubleshooting
- Missing or invalid API Key or API Secret will cause authentication failure. Ensure credentials are correctly set.
- Preference ID is required for updating a preference; missing this will throw an error.
- Malformed JSON in the request body can cause request failure; validate JSON format before sending.
- API errors from Didomi will be returned with error messages; check the error description for troubleshooting.