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 Secret
AI-generatedOverview
This node operation creates a secret in the Didomi Consent and Preference API. It is useful for managing user consent data securely by generating secrets that can be used for authentication or encryption purposes within consent management workflows.
Use Case Examples
- Creating a secret to securely store user consent tokens.
- Generating a secret for use in consent event processing.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional parameters to customize the API request, such as filtering or pagination options. |
Output
JSON
id- The unique identifier of the created secret.secret- The secret value created by the API.created_at- Timestamp when the secret was created.
Dependencies
- Didomi API with API Key and Secret credentials
Troubleshooting
- Ensure that both API Key and API Secret credentials are provided; missing credentials will cause authentication failure.
- Verify that the request body JSON is correctly formatted; invalid JSON will cause request errors.
- Check that the API endpoint URL is correct and that required parameters are provided; missing required IDs will cause errors.
- Handle API errors gracefully by inspecting error messages returned from the Didomi API for troubleshooting.