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

Manage secrets

Didomi secrets 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 Secrets. 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 6 operations across 2 paths, and defines 2 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.

6 operations 2 paths 2 schemas 1 DELETE2 GET1 PATCH1 POST1 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 secrets API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer). By default, every request must be authenticated.

Paths & Operations 6

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

secrets 6

Manage secrets

GET
/secrets
Retrieve a list of secrets
4 params → 200
POST
/secrets
Create a secret
1 param body → 200
GET
/secrets/{id}
Retrieve a secret
1 param → 200
PUT
/secrets/{id}
Update a secret
2 params body → 200
PATCH
/secrets/{id}
Patch a secret
2 params body → 200
DELETE
/secrets/{id}
Delete a secret
1 param → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are secrets (8 properties), secrets-input (3 properties). Each schema is shown below with its type and property counts.

secrets-input
object
3 properties 2 required
secrets
object
A secret is used to authenticate API requests in unsecure environments (client-side, emails, etc.)
8 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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