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
Compliance Report → Create Report
AI-generatedOverview
This node operation creates a compliance report by interacting with the Didomi API. It is useful for analyzing website compliance by scanning pages to detect trackers and vendors, generating reports with insights and recommendations. For example, a user can create a compliance report to assess their website's adherence to privacy regulations and identify any compliance issues.
Use Case Examples
- Creating a compliance report to evaluate website tracker usage and vendor compliance.
- Generating a report to monitor the status of compliance efforts across different organizational units.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Parameters to filter or customize the compliance report creation request, such as organization user ID, cursor, limit, status, and other report-specific filters. |
Output
JSON
reportId- The ID of the created compliance report.status- The status of the compliance report creation request.details- Additional details or metadata about the created report.
Dependencies
- Didomi API with API Key and API Secret credentials
Troubleshooting
- Missing API Key or API Secret will cause authentication failure; ensure credentials are provided.
- Required parameters such as Report ID must be provided for certain operations; missing these will throw errors.
- API request failures will throw errors with messages indicating the cause; check network connectivity and API limits.
Links
- Didomi API Documentation - Create Compliance Report - Official API documentation for creating compliance reports using Didomi API.