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 → Get Configuration Tree
AI-generatedOverview
This node operation retrieves the configuration tree data from the Didomi API's Data Manager resource. It is useful for scenarios where you need to access the hierarchical structure of user data preferences, purposes, and related configurations managed within Didomi. For example, it can be used to fetch the current configuration tree to analyze or update user privacy settings and preferences centrally.
Use Case Examples
- Fetch the configuration tree to display or audit user data preferences and purposes.
- Retrieve configuration tree data to integrate with other privacy management tools or workflows.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Parameters to filter or paginate the configuration tree data retrieved from the API. |
Output
JSON
*- The JSON response containing the configuration tree data retrieved 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.
- Required parameters like Configuration Tree ID must be provided for certain operations, otherwise an error is thrown.
- API request failures will throw errors with messages indicating the cause, such as missing IDs or network issues.
Links
- Didomi API Documentation - Get Configuration Tree - Official API documentation for retrieving configuration tree data from Didomi.