How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Didomi notices API

The notices API from Didomi — 18 operation(s) for notices.

Didomi notices API is one of 37 APIs that Didomi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include Notices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, rate-limit docs, and 4 JSON Schemas.

This API exposes 38 operations across 18 paths, and defines 22 schemas. It is described by OpenAPI 3.0.2, at version 1.0.

Requests are made against a single base URL, https://api.didomi.io/v1.

38 operations 18 paths 22 schemas 4 DELETE16 GET6 PATCH7 POST5 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
1.0
Base URL
https://api.didomi.io/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Didomi notices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer). By default, every request must be authenticated.

Paths & Operations 38

Across 18 paths, the API surfaces 38 operations — 4 DELETE, 16 GET, 6 PATCH, 7 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.

notices 38
GET
/widgets/notices/texts
Retrieve a list of notice texts
→ 200
POST
/widgets/notices/texts
Create a notice text
1 param body → 200
GET
/widgets/notices/texts/{id}
Retrieve a notice text
1 param → 200
PUT
/widgets/notices/texts/{id}
Update a notice text
2 params body → 200
PATCH
/widgets/notices/texts/{id}
Patch a notice text
2 params body → 200
GET
/widgets/notices/texts-contents
Retrieve a list of notice text contents
→ 200
POST
/widgets/notices/texts-contents
Create a notice text content
1 param body → 200
GET
/widgets/notices/texts-contents/{id}
Retrieve a notice text content
1 param → 200
PUT
/widgets/notices/texts-contents/{id}
Update a notice text content
2 params body → 200
PATCH
/widgets/notices/texts-contents/{id}
Patch a notice text content
2 params body → 200
DELETE
/widgets/notices/texts-contents/{id}
Delete a notice text content
1 param → 200
POST
/widgets/notices/generators/sdk
Generate a SDK configuration
1 param body → 200
POST
/widgets/notices/generators/configs
Generate a Notice configuration
1 param body → 200
GET
/widgets/notices/templates/configs
Retrieve a list of notice template configurations
2 params → 200
GET
/widgets/notices/templates/configs/{id}
Retrieve a notice template configuration
3 params → 200
PUT
/widgets/notices/templates/configs/{id}
Update a notice template configuration
2 params body → 200
PATCH
/widgets/notices/templates/configs/{id}
Patch a notice template configuration
2 params body → 200
DELETE
/widgets/notices/templates/configs/{id}
Removes the resource with id.
1 param → 200401404500
GET
/widgets/notices/templates
Retrieve a list of notices templates
2 params → 200
POST
/widgets/notices/templates
Create a notice template
1 param body → 200
GET
/widgets/notices/templates/{id}
Retrieve a notice template
3 params → 200
PUT
/widgets/notices/templates/{id}
Updates the resource identified by id using data.
1 param body → 200401404500
PATCH
/widgets/notices/templates/{id}
Patch a notice template, and associate notice template with notices
2 params body → 200
DELETE
/widgets/notices/templates/{id}
Removes the notice template, and associated notice template config
1 param → 200
GET
/widgets/notices/deployments
Retrieve a list of deployments
→ 200
POST
/widgets/notices/deployments
Create a deployment
1 param body → 200
GET
/widgets/notices/deployments/{id}
Retrieve a deployment
1 param → 200
GET
/widgets/notices/configs
Retrieve a list of configurations
2 params → 200
GET
/widgets/notices/configs/{id}
Retrieve a notice configuration
3 params → 200
PATCH
/widgets/notices/configs/{id}
Patch a notice configuration
3 params body → 200
GET
/widgets/notices/sdk-configs
Retrieve a list of SDK configurations
→ 200
GET
/widgets/notices/sdk-configs/{id}
Retrieve a SDK configuration
1 param → 200
GET
/widgets/notices
Retrieve a list of notices
→ 200
POST
/widgets/notices
Create a notice
2 params body → 200
GET
/widgets/notices/{id}
Retrieve a notice
1 param → 200
PUT
/widgets/notices/{id}
Update a notice
2 params body → 200
PATCH
/widgets/notices/{id}
Patch a notice
2 params body → 200
DELETE
/widgets/notices/{id}
Delete a notice
1 param → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are notices-config (79 properties), notices-config-input (63 properties), notices-regulation-config-input (58 properties), notices-regulations-config (58 properties). Each schema is shown below with its type and property counts.

notices-templates-input
object
A template defines common configuration shared across multiple consent notices
2 properties
notices-input
object
7 properties 2 required
notices-templates-configs
object
A template config defines a notice configuration associated with a template
8 properties 3 required
notices-templates-configs-input
object
A template config defines a notice configuration associated with a template
2 properties 2 required
notices-text-content
object
The actual content of a notice text (the text itself, approval status, etc.).
10 properties 10 required
notices-templates
object
A template defines common configuration shared across multiple consent notices
7 properties 3 required
notices-text-input
object
Texts that can be used in notices for consent collection on various platforms (web, mobile, etc.). The actual content of a text (the text itself, approval stat…
4 properties 2 required
notices-config-input
object
63 properties 2 required
notice-configs-input
object
2 properties 2 required
notices-text-content-input
object
The actual content of a notice text (the text itself, approval status, etc.).
4 properties 3 required
notices-config
object
Configuration (purposes and vendors, theme, format, etc.) of a consent notice
79 properties 3 required
notices-sdk-config
object
Published SDK configuration
10 properties 10 required
notice-configs
object
Consent notice configuration structured for Didomi API
1 property 1 required
notices
object
Consent notices (for mobile and desktop)
11 properties 3 required
notices-deployments-input
object
4 properties 3 required
notices-regulation-config-input
object
58 properties 3 required
notices-text
object
Texts that can be used in notices for consent collection on various platforms (web, mobile, etc.). The actual content of a text (the text itself, approval stat…
8 properties 8 required
notices-regulations-config
object
Regulation configuration (purposes and vendors, theme, format, etc.) of a consent notice
58 properties 4 required
sdk-configs
object
Consent notice configuration structured for a Didomi SDK
1 property 1 required
notices-templates-translatable-string
object
An object that represens translatable string, to support translations to different languages
2 properties 1 required
sdk-configs-input
object
37 properties 3 required
notices-deployments
object
A deployment updates the live configuration used by a notice
9 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

didomi-notices-api-openapi.yml Raw ↑

Other APIs Didomi publishes across the network.

Didomi Web SDK
Didomi Android SDK
Didomi iOS SDK
Didomi Cross-Platform SDKs (React Native, Flutter, Unity, Vega OS, AMP)
Didomi Consent String Toolkit
Didomi consents/events API
Didomi consents/proofs API
Didomi consents/tokens API
Didomi consents/users API
Didomi cookies API
Didomi dashboards-urls API
Didomi domains API
Where this information came from

This is an independent, third-party profile of Didomi notices API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.