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
Widget → Update Widget
AI-generatedOverview
This node operation updates an existing widget configuration in the Didomi platform. It is useful for scenarios where you need to modify the settings or properties of a widget that manages user consent and preference interfaces. For example, updating the widget's layout, behavior, or associated data to reflect new compliance requirements or user preferences.
Use Case Examples
- Updating a widget's configuration to change its appearance or functionality.
- Modifying widget settings to comply with updated privacy regulations.
Properties
| Name | Meaning |
|---|---|
| Widget ID | The unique identifier of the widget to update. |
| Query Parameters | Optional parameters to filter or modify the request behavior when updating the widget. |
| Request Body | The JSON body containing the updated widget configuration data. |
Output
JSON
Status Code- HTTP status code when no content is returned (e.g., 204 No Content).*- The JSON response from the Didomi API representing the updated widget details.
Dependencies
- Didomi API key and secret credentials are required for authentication.
Troubleshooting
- Ensure the Widget ID is provided; otherwise, the node throws an error indicating the missing Widget ID.
- Verify that the API key and secret credentials are correctly set and valid to avoid authentication errors.
- Check the request body JSON format for correctness to prevent request failures.
- Common error messages include missing required parameters and authentication failures; resolving these involves providing the required inputs and valid credentials.