Overview

This node operation lists all pending consent and preference events from the Didomi API. It is useful for scenarios where you need to retrieve and review pending user consent events, such as for compliance monitoring or processing user consent updates. For example, a privacy officer might use this to fetch all pending consent events to approve or audit them.

Use Case Examples

1. Retrieve a list of all pending consent events for a specific organization user ID.
2. Fetch pending consent events filtered by status or other query parameters to monitor consent processing.

Properties

Output

JSON

• id - Unique identifier of the pending event.
• status - Current status of the pending event.
• organization_user_id - Identifier of the organization user associated with the event.
• created_at - Timestamp when the event was created.
• updated_at - Timestamp when the event was last updated.
• details - Additional details about the pending event.

Dependencies

• Didomi API with API Key and Secret for authentication

Troubleshooting

• Ensure that the API Key and API Secret credentials are correctly configured and valid, as missing or invalid credentials will cause authentication failures.
• Verify that the required 'Consent Event ID' parameter is provided when needed; for listing pending events, ensure query parameters are correctly set if filtering is applied.
• Check network connectivity and API endpoint availability if requests fail.
• Handle API rate limits and errors gracefully; the node throws descriptive errors if the Didomi API call fails.

Links

• Didomi API Documentation - List Pending Events - Official API documentation for listing pending consent and preference events in Didomi.