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
Consent And Preference → Get Pending Event
AI-generatedOverview
This node operation retrieves a specific pending consent event from the Didomi API. It is useful in scenarios where you need to fetch details about a user's pending consent event for compliance or auditing purposes. For example, you might use this to check the status or details of a consent event before approving or processing it further.
Use Case Examples
- Fetch a pending consent event by its ID to review user consent status before approval.
- Retrieve detailed information about a pending consent event for reporting or compliance checks.
Properties
| Name | Meaning |
|---|---|
| Consent Event ID | The unique identifier of the consent event to retrieve. This is required to specify which pending event to get. |
| Query Parameters | Optional parameters to filter or modify the request, such as organization user ID, cursor for pagination, limit on number of results, status filter, and other consent event related filters. |
Output
JSON
id- The unique identifier of the pending consent event.status- The current status of the pending consent event.organization_user_id- The organization user ID associated with the consent event.created_at- Timestamp when the pending event was created.updated_at- Timestamp when the pending event was last updated.details- Additional details about the pending consent event.
Dependencies
- Didomi API with API Key and Secret credentials
Troubleshooting
- Ensure the Consent Event ID is provided; otherwise, the node will throw an error indicating it is required.
- Verify that the API Key and API Secret credentials are correctly set and valid to obtain an access token.
- Check the network connectivity and Didomi API availability if requests fail.
- If the response is empty or unexpected, verify the query parameters and consent event ID for correctness.