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 → List Preferences
AI-generatedOverview
This node operation lists preferences managed in the Didomi platform's Data Manager resource. It allows users to retrieve a collection of preference records with optional query parameters to filter and control the results, such as limiting the number of results, filtering by organization user ID, status, regulation, and other criteria. This operation is useful for managing and auditing user preferences related to data privacy and consent within an organization.
Use Case Examples
- A privacy officer wants to retrieve all user preferences related to a specific regulation to ensure compliance.
- A data manager needs to list preferences with a limit of 100 to review recent changes.
- An analyst filters preferences by organization user ID to generate a report on user consent trends.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Collection of optional filters and controls to refine the list of preferences returned by the API, including pagination, filtering by IDs, status, counts, and other attributes. |
Output
JSON
json- The JSON array of preference objects returned by the Didomi API, representing the list of preferences matching the query parameters.
Dependencies
- Didomi API credentials (API Key and API Secret) are required for authentication.
Troubleshooting
- Missing or invalid API Key or API Secret will cause authentication failure and prevent the node from executing.
- Required parameters such as Configuration Tree ID or Preference ID (if applicable) must be provided; otherwise, the node throws an error indicating the missing parameter.
- API request failures or network issues will result in error messages from the Didomi API, which are propagated by the node with details for troubleshooting.