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 Token
AI-generatedOverview
This node operation creates a token in the Didomi Consent and Preference API. It is useful for scenarios where you need to generate a token for managing user consents and preferences programmatically, such as integrating consent management into your application or automating consent workflows.
Use Case Examples
- Generating an access token to authenticate further API requests related to user consents.
- Automating the creation of tokens for consent management in a privacy compliance system.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional parameters to customize the token creation request, such as filtering or pagination options. |
| Request Body | JSON object representing the body of the token creation request, containing the necessary data to create the token. |
Output
JSON
json- The JSON response from the Didomi API containing the created token details or relevant data.
Dependencies
- Didomi API with API Key and API Secret credentials
Troubleshooting
- Ensure that both API Key and API Secret credentials are provided; missing credentials will cause an error.
- Verify that the Consent Event ID is not required for this operation, but if any required parameter is missing, the node will throw an error indicating which parameter is missing.
- Check the API response for errors; the node throws detailed errors if the API call fails, including the error message and stack trace.