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 → Get Provider Configuration Schemas
AI-generatedOverview
This node interacts with the Didomi API to retrieve provider configuration schemas related to privacy requests. It is useful for scenarios where users need to access detailed schema information about provider configurations in the context of privacy management, such as compliance with data privacy regulations or managing privacy requests.
Use Case Examples
- Fetching provider configuration schemas to understand the structure and requirements for privacy request handling.
- Integrating with Didomi to automate retrieval of configuration schemas for privacy request workflows.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of optional parameters to filter or modify the request for provider configuration schemas. These include parameters like organization user ID, cursor for pagination, limit on number of results, status filters, and others to customize the API call. |
Output
JSON
json- The JSON response from the Didomi API containing the provider configuration schemas data.
Dependencies
- Didomi API key and secret credentials are required for authentication.
Troubleshooting
- Missing API Key or API Secret: Ensure that the Didomi API credentials are correctly configured in the node settings.
- Request ID or other required parameters missing: Some operations require specific IDs; ensure these are provided to avoid errors.
- API access token retrieval failure: The node fetches an access token before making API calls; network issues or invalid credentials can cause failure.
- Invalid query parameters: Ensure that query parameters are correctly formatted and valid according to the Didomi API documentation.
Links
- Didomi API Documentation - Official documentation for the Didomi API, including details on provider configuration schemas and privacy request operations.