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 metadata API

A metadata service

Didomi metadata 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 Metadata. 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 31 operations across 11 paths, and defines 12 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.

31 operations 11 paths 12 schemas 5 DELETE10 GET5 PATCH6 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 metadata API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer). By default, every request must be authenticated.

Paths & Operations 31

Across 11 paths, the API surfaces 31 operations — 5 DELETE, 10 GET, 5 PATCH, 6 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.

metadata 31

A metadata service

POST
/metadata/partners/deprecate
Creates a new resource with data.
body → 201401500
GET
/metadata/vendors
Retrieve a list of vendors
1 param → 200
POST
/metadata/vendors
Create a vendor
1 param body → 200
GET
/metadata/vendors/{id}
Retrieve a vendor
1 param → 200
PUT
/metadata/vendors/{id}
Update a vendor
2 params body → 200
PATCH
/metadata/vendors/{id}
Patch a vendor
2 params body → 200
DELETE
/metadata/vendors/{id}
Delete a vendor
1 param → 200
GET
/metadata/partners-categories
Retrieve a list of partners categories
4 params → 200
POST
/metadata/partners-categories
Create a partners category
1 param body → 200
GET
/metadata/partners-categories/{id}
Retrieve a partners category
1 param → 200
PUT
/metadata/partners-categories/{id}
Update a partners category
2 params body → 200
PATCH
/metadata/partners-categories/{id}
Patch a partners category
2 params body → 200
DELETE
/metadata/partners-categories/{id}
Delete a partners category
1 param → 200
GET
/metadata/partners-purposes
List partner-purpose associations
4 params → 200
POST
/metadata/partners-purposes
Create a partner-purpose association
body → 201
GET
/metadata/partners-purposes/{id}
Get a partner-purpose association
1 param → 200
PUT
/metadata/partners-purposes/{id}
Updates the resource identified by id using data.
1 param body → 200401404500
PATCH
/metadata/partners-purposes/{id}
Update processing rules
1 param body → 200
DELETE
/metadata/partners-purposes/{id}
Delete a partner-purpose association
1 param → 200
GET
/metadata/partners-purposes-templates-overrides
List template overrides
4 params → 200
POST
/metadata/partners-purposes-templates-overrides
Create a template override
body → 201
GET
/metadata/partners-purposes-templates-overrides/{id}
Get a template override
1 param → 200
PUT
/metadata/partners-purposes-templates-overrides/{id}
Updates the resource identified by id using data.
1 param body → 200401404500
PATCH
/metadata/partners-purposes-templates-overrides/{id}
Update a template override
1 param body → 200
DELETE
/metadata/partners-purposes-templates-overrides/{id}
Delete a template override
1 param → 200
GET
/metadata/partners-purposes-notices-regulations-overrides
List notice-regulation overrides
4 params → 200
POST
/metadata/partners-purposes-notices-regulations-overrides
Create a notice-regulation override
body → 201
GET
/metadata/partners-purposes-notices-regulations-overrides/{id}
Get a notice-regulation override
1 param → 200
PUT
/metadata/partners-purposes-notices-regulations-overrides/{id}
Updates the resource identified by id using data.
1 param body → 200401404500
PATCH
/metadata/partners-purposes-notices-regulations-overrides/{id}
Update a notice-regulation override
1 param body → 200
DELETE
/metadata/partners-purposes-notices-regulations-overrides/{id}
Delete a notice-regulation override
1 param → 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are partners (25 properties), metadata-vendors (12 properties), partners-purposes (11 properties), partners-purposes-notices-regulations-overrides (10 properties). Each schema is shown below with its type and property counts.

metadata-vendors-input
object
7 properties 1 required
partners-purposes-notices-regulations-overrides
object
10 properties 7 required
partners-purposes-templates-overrides
object
9 properties 6 required
partners-categories
object
4 properties 1 required
partners-categories-input
object
2 properties
partners-purposes-input
object
4 properties 3 required
partners-purposes-notices-regulations-overrides-input
object
6 properties 6 required
metadata-vendors
object
A vendor is a third-party company that provides services to properties by collecting data, transforming it, ... This object describes a vendor.
12 properties 2 required
partners-purposes
object
11 properties 4 required
vendors
object
A vendor that provides services to a property
7 properties 3 required
partners-purposes-templates-overrides-input
object
5 properties 5 required
partners
object
A third-party company that provides services to companies by collecting data, transforming it, etc.
25 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

didomi-metadata-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 metadata 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.