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 → Create Consent User
AI-generatedOverview
This node operation creates a consent user in the Didomi system. It is useful for managing user consent data by enabling the creation of new consent user records, which can be essential for compliance with privacy regulations and managing user preferences across platforms. For example, it can be used to register a new user who has given consent for data processing.
Use Case Examples
- Creating a new consent user record when a user signs up on a website and agrees to the privacy policy.
- Automating the creation of consent users in bulk from an existing user database.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional parameters to customize the API request, such as filtering or pagination options. |
Output
JSON
json- The JSON response from the Didomi API representing the created consent user or relevant data.
Dependencies
- Didomi API key and secret credentials required for authentication.
Troubleshooting
- Ensure that the API key and secret credentials are correctly set and valid; missing or invalid credentials will cause authentication failures.
- Verify that the required fields, such as the request body, are correctly formatted JSON; malformed JSON will cause request errors.
- Check that any required IDs or parameters are provided; missing required parameters will result in errors.
- Common error messages include authentication failures, missing required parameters, and invalid request formats. Resolving these involves verifying credentials, input parameters, and JSON formatting.