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 Request
AI-generatedOverview
This node operation retrieves a specific privacy request from the Didomi API using the provided Request ID and optional query parameters. It is useful for scenarios where you need to access detailed information about a user's privacy request, such as data access, deletion, or opt-out requests, to manage compliance and user data privacy.
Use Case Examples
- Retrieve a privacy request by its unique Request ID to check its status and details.
- Fetch privacy request information filtered by specific query parameters like status or organization ID to monitor ongoing requests.
Properties
| Name | Meaning |
|---|---|
| Request ID | The unique identifier of the privacy request to retrieve. |
| Query Parameters | Optional parameters to filter or modify the request, such as status, limit, cursor, organization ID, and others to refine the data returned. |
Output
JSON
*- The JSON response from the Didomi API containing the privacy request details or error information.
Dependencies
- Didomi API credentials (API Key and API Secret)
Troubleshooting
- Ensure that the Request ID is provided; otherwise, the node will throw an error indicating the missing Request ID.
- Verify that the Didomi API credentials (API Key and API Secret) are correctly set up, as missing credentials will cause authentication failures.
- Check the API response for error messages if the request fails, and ensure the query parameters are valid and correctly formatted.
Links
- Didomi API - Get Privacy Request - Official Didomi API documentation for retrieving a privacy request.