Didi

DiDi Global is a mobility technology platform best known for ride-hailing, taxi-hailing, and enterprise employee travel across China and international markets. DiDi exposes a public developer surface through DiDi Enterprise Services (DDES) — an Open API for corporate travel management covering approval workflows, bills, budget/cost centers, orders, single sign-on, users, roles, and company entities. The DDES API (base URL https://api.es.xiaojukeji.com) is documented at opendocs.xiaojukeji.com/version2024, secured with OAuth 2.0 client_credentials plus per-request signing, and shipped with official Java and Go SDKs under the github.com/didi organization. DiDi is backed by Hillhouse and the SoftBank Vision Fund.

Didi is listed with 1 API on the APIs.io network. Tagged areas include Company, Mobility, Ride Hailing, Transportation, and Enterprise Travel.

Didi’s developer surface includes documentation, getting-started guide, authentication, and 9 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

19.9/100 emerging ▬ flat Agent 3/100 human only Heartbeat 83/100 alive library Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessSelf serve

1 API

Company Mobility Ride Hailing TransportationEnterprise TravelExpense Management OAuth Authentication

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 19.9/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 9.7 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.3 / 11

Contract Governance 0.5 / 10

Discoverability 6.2 / 9

Regulatory Posture 2.5 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/didi/"><img src="https://apis.io/badge/didi/card.svg" alt="Didi on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 0.0 — up to +20.0 composite points
Operational Transparency scores 2.6 — up to +12.7 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/didi/apis.yml: open an issue on github.com/api-evangelist/didi to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Transit and Mobility (public transit, rail, micromobility)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OAuth

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

DiDi Enterprise (DDES) Open API

DiDi Enterprise Services (DDES) Open API for corporate employee travel management — approval, bills, budget/cost centers, city info, company entities, single sign-on, users, ord...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Didi Authentication

oauth2 · 1 scheme

SECURITY

Didi Domain Security

TLSv1.2 · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Conformance

Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: didi
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/didi.png
name: Didi
description: DiDi Global is a mobility technology platform best known for ride-hailing, taxi-hailing, and enterprise employee
  travel across China and international markets. DiDi exposes a public developer surface through DiDi Enterprise Services
  (DDES) — an Open API for corporate travel management covering approval workflows, bills, budget/cost centers, orders, single
  sign-on, users, roles, and company entities. The DDES API (base URL https://api.es.xiaojukeji.com) is documented at opendocs.xiaojukeji.com/version2024,
  secured with OAuth 2.0 client_credentials plus per-request signing, and shipped with official Java and Go SDKs under the
  github.com/didi organization. DiDi is backed by Hillhouse and the SoftBank Vision Fund.
url: https://raw.githubusercontent.com/api-evangelist/didi/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- hillhouse
- softbank-vision-fund
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
tags:
- Company
- Mobility
- Ride Hailing
- Transportation
- Enterprise Travel
- Expense Management
- OAuth
- Authentication
tags_raw:
- Company
- Mobility
- Ride Hailing
- Transportation
- Enterprise Travel
- Expense Management
- OAuth
- Authentication
apis:
- name: DiDi Enterprise (DDES) Open API
  description: DiDi Enterprise Services (DDES) Open API for corporate employee travel management — approval, bills, budget/cost
    centers, city info, company entities, single sign-on, users, orders, ranks, regulations, roles, external travelers, and
    work locations.
  humanURL: https://opendocs.xiaojukeji.com/version2024
  baseURL: https://api.es.xiaojukeji.com
  tags:
  - Enterprise Travel
  - Mobility
  - Expense Management
  properties:
  - type: Documentation
    url: https://opendocs.xiaojukeji.com/version2024
  - type: APIReference
    url: https://opendocs.xiaojukeji.com/version2024
  - type: GettingStarted
    url: https://opendocs.xiaojukeji.com/version2024/10957
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.didiglobal.com
- type: DeveloperPortal
  url: https://opendocs.xiaojukeji.com/version2024
- type: Documentation
  url: https://opendocs.xiaojukeji.com/version2024
- type: GettingStarted
  url: https://opendocs.xiaojukeji.com/version2024/10957
- type: GitHubOrganization
  url: https://github.com/didi
- type: Authentication
  url: authentication/didi-authentication.yml
- type: Conventions
  url: conventions/didi-conventions.yml
- type: Conformance
  url: conformance/didi-conformance.yml
- type: Packages
  url: packages/didi-packages.yml
- type: SDKs
  url: packages/didi-packages.yml
- type: DomainSecurity
  url: security/didi-domain-security.yml
- type: LLMsTxt
  url: llms/didi-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Didi API — frequently asked questions

Does Didi have an API?

Yes. APIs.io lists 1 API from Didi, including DiDi Enterprise (DDES) Open API.

How do I authenticate with the Didi API?

Didi uses bearer-token authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Didi Authentication.

Is the Didi API ready for AI agents?

Didi has a Kin Score of 19.9 out of 100 (emerging) and an Agent Readiness score of 2.5 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/didi"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/didi/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/didi/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.