/widgets/notices/configs
endpoint of the API exposes the notice configurations managed by Didomi for your organizations. For a full reference of the endpoint and the resources that it returns, visit https://api.didomi.io/docs/.null
as the value for its deployed_at
field.deployed_at = null
.2fcjz7Cw
) is the current draft and can be modified to prepare for publishing.PATCH
request to the current draft configuration.PATCH
request with an updated configuration. Example for switching the notice to a mobile notice with a consent duration of 6 months:config
field and the other fields on the configuration object:config
field follows the format documented for the configuration of the SDKs in our SDKs configuration section.config
field into separate fields on configurations and will do so in a backward-compatible manner. The config
field will eventually be deprecated as it proved complex to work with.deployed_at
field. A configuration that is already published cannot be modified so that it can be used as proof of how consent was collected at a given time.POST /widgets/notices/deployments
request for that specific configuration.deployed_at
field and that configuration cannot be modified or published anymore. A new draft configuration is automatically created for the notice as a copy of the latest published configuration. To make further changes to the notice configuration, get the new draft configuration and modify it.production_config_id
should be the ID of the draft config you are publishing. message
is a text field that can be used to indicate information on what changes are included in your deployment.