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 → Approve Pending Events
AI-generatedOverview
This node operation approves pending consent and preference events using the Didomi API. It is useful in scenarios where user consent events need to be programmatically approved, such as automating consent management workflows or integrating consent approval into larger data processing pipelines. For example, a company can use this node to approve pending consent events after verifying user actions or compliance requirements.
Use Case Examples
- Approving pending consent events for a specific user or organization.
- Automating the approval of consent events as part of a compliance audit process.
Properties
| Name | Meaning |
|---|---|
| Consent Event ID | The unique identifier of the consent event to approve. This is required to specify which pending event to approve. |
| Query Parameters | Optional parameters to filter or modify the approval request, such as organization user ID, cursor, limit, status, and other filters. |
| Request Body | The JSON body of the approval request, containing details necessary to approve the pending events. |
Output
JSON
Status Code- HTTP status code or message indicating the result of the approval request.json- The JSON response from the Didomi API after approving the pending events, containing details of the approved events or status.
Dependencies
- Didomi API key and secret credentials for authentication.
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 secret credentials are correctly set and valid to avoid authentication errors.
- Check the request body JSON format for correctness to prevent request failures.
- If the API returns an error, review the error message and stack trace provided by the node for debugging.