NTT Docomo

NTT DOCOMO, Inc. is Japan's largest mobile network operator and a wholly owned subsidiary of Nippon Telegraph and Telephone (NTT), serving roughly 90 million mobile subscriptions in its home market of Japan across the docomo, ahamo and irumo brands, alongside the d ACCOUNT identity, d POINT loyalty, d Payment wallet and Lemino media franchises. In the telecom value chain DOCOMO is a facilities-based incumbent carrier — it owns the 5G radio, core and subscriber identity — but it does not sell that capability to developers directly. Its API posture is partner-gated and sales-led: the first-party "docomo Developer support" programme launched in 2013 was shut down on 31 March 2021 and its host no longer resolves, no developer, developers, docs, api or opengateway subdomain exists on docomo.ne.jp, and the only surviving public developer page documents handset and content technical information rather than any HTTP API. DOCOMO's network APIs reach developers only through aggregation: the company participates in the GSMA Open Gateway initiative and signed a distribution partnership with Aduna, the Ericsson-and-carrier joint venture, on 29 January 2026 to expose CAMARA Number Verification and SIM Swap for international markets — a commitment announced in press releases, with nothing callable published first-party as of this profile. Enterprise and wholesale API traffic is redirected to sibling company NTT DOCOMO BUSINESS on a separate domain.

NTT Docomo publishes 2 APIs on the APIs.io network. Tagged areas include Telecommunications, Japan, Mobile Network Operator, Network APIs, and CAMARA.

NTT Docomo’s developer surface includes authentication, documentation, support, pricing, signup flow, engineering blog, and 17 more developer resources.

26.2/100 emerging ▬ flat Agent 14/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5
2 APIs
TelecommunicationsJapanMobile Network OperatorNetwork APIsCAMARAOpen GatewayAdunaCarrier IdentitySIM SwapNumber VerificationCarrier Billing5GPartner Gated

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 26.2/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 5.2 / 20
Commercial Clarity 8.9 / 20
Operational Transparency 2.7 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 14/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/ntt-docomo: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 2

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

d ACCOUNT Connect

d ACCOUNT Connect (dアカウント・コネクト) is DOCOMO's carrier identity service for businesses, offering OpenID Connect based social login backed by network line authentication and device ...

docomo Mail IMAP Interface

The docomo Mail IMAP interface is the one machine-interface specification NTT DOCOMO publishes openly, without registration, to third-party developers. It documents how a mail c...

Security Posture 2

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

Ntt Docomo Authentication

openIdConnect · 1 scheme

SECURITY

Ntt Docomo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: ntt-docomo
url: https://raw.githubusercontent.com/api-evangelist/ntt-docomo/refs/heads/main/apis.yml
name: NTT Docomo
kind: company
description: 'NTT DOCOMO, Inc. is Japan''s largest mobile network operator and a wholly owned subsidiary of Nippon Telegraph
  and Telephone (NTT), serving roughly 90 million mobile subscriptions in its home market of Japan across the docomo, ahamo
  and irumo brands, alongside the d ACCOUNT identity, d POINT loyalty, d Payment wallet and Lemino media franchises. In the
  telecom value chain DOCOMO is a facilities-based incumbent carrier — it owns the 5G radio, core and subscriber identity
  — but it does not sell that capability to developers directly. Its API posture is partner-gated and sales-led: the first-party
  "docomo Developer support" programme launched in 2013 was shut down on 31 March 2021 and its host no longer resolves, no
  developer, developers, docs, api or opengateway subdomain exists on docomo.ne.jp, and the only surviving public developer
  page documents handset and content technical information rather than any HTTP API. DOCOMO''s network APIs reach developers
  only through aggregation: the company participates in the GSMA Open Gateway initiative and signed a distribution partnership
  with Aduna, the Ericsson-and-carrier joint venture, on 29 January 2026 to expose CAMARA Number Verification and SIM Swap
  for international markets — a commitment announced in press releases, with nothing callable published first-party as of
  this profile. Enterprise and wholesale API traffic is redirected to sibling company NTT DOCOMO BUSINESS on a separate domain.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Telecommunications
- Japan
- Mobile Network Operator
- Network APIs
- CAMARA
- Open Gateway
- Aduna
- Carrier Identity
- SIM Swap
- Number Verification
- Carrier Billing
- 5G
- Partner Gated
created: '2026-07-25'
modified: '2026-07-25'
specificationVersion: '0.19'
apis:
- aid: ntt-docomo:d-account-connect
  name: d ACCOUNT Connect
  description: d ACCOUNT Connect (dアカウント・コネクト) is DOCOMO's carrier identity service for businesses, offering OpenID Connect
    based social login backed by network line authentication and device biometrics against roughly 90 million d ACCOUNT registrations
    and approximately 2,000 implemented sites. A live, anonymous OpenID Connect discovery document is served at https://conf.uw.docomo.ne.jp/.well-known/openid-configuration
    (HTTP 200, fetched 2026-07-25) declaring issuer https://conf.uw.docomo.ne.jp/, the authorization endpoint https://id.smt.docomo.ne.jp/cgi8/oidc/authorize,
    token and userinfo endpoints, pairwise subject identifiers, response_types of code only, and HS256/RS256 ID token signing.
    No backchannel authentication endpoint is advertised, so CIBA — the grant CAMARA specifies for network-based authorization
    — is not exposed here. The integration manual and technical specification are downloadable only after submitting a use
    application and passing DOCOMO's review; no OpenAPI definition is published.
  humanURL: https://id.smt.docomo.ne.jp/src/index_business.html
  baseURL: https://conf.uw.docomo.ne.jp/
  tags:
  - Identity
  - OpenID Connect
  - Authentication
  - Carrier Identity
  - Partner Gated
  properties:
  - type: Documentation
    url: https://id.smt.docomo.ne.jp/src/index_business.html
  - type: APIReference
    url: https://id.smt.docomo.ne.jp/src/dlogin/ctop_method.html
  - type: GettingStarted
    url: https://id.smt.docomo.ne.jp/src/dlogin/ctop_method.html
  - type: OpenIDConnectDiscovery
    url: https://conf.uw.docomo.ne.jp/.well-known/openid-configuration
  - type: Authentication
    url: authentication/ntt-docomo-authentication.yml
  - type: WellKnown
    url: well-known/ntt-docomo-well-known.yml
  - type: JWKS
    url: well-known/ntt-docomo-jwks.json
  - type: SignUp
    url: https://g.daccount.docomo.ne.jp/VIEW_OC01/login4
  - type: StatusPage
    url: https://id.smt.docomo.ne.jp/src/dac/maintenance-g.html
  - type: Support
    url: https://id.smt.docomo.ne.jp/src/dlogin/ctop_method_form.html
  - type: TermsOfService
    url: https://id.smt.docomo.ne.jp/src/utility/rules.html
- aid: ntt-docomo:docomo-mail-imap-interface
  name: docomo Mail IMAP Interface
  description: 'The docomo Mail IMAP interface is the one machine-interface specification NTT DOCOMO publishes openly, without
    registration, to third-party developers. It documents how a mail client connects to the docomo Mail service over IMAP,
    and is distributed as a 96-page Japanese PDF specification (mail_imap_spec_260126.pdf, HTTP 200, application/pdf, 1,229,737
    bytes, edition 4.5 dated 2026-01-26, first edition 2013-12-19). This is an IMAP protocol interface, not an HTTP API: there
    is no REST surface, no OpenAPI definition, no API key issuance and no sandbox associated with it. The specification is
    complete and unredacted — it names the two production endpoints (imap.spmode.ne.jp and imap2.spmode.ne.jp, both on port
    993), pins TLS 1.2 with an explicit allow-list of ten cipher suites and a 2048-bit public key, authenticates with d ACCOUNT
    ID and password, and specifies 31 IMAP commands including IDLE, NAMESPACE, UID EXPUNGE and the QUOTA family. The imap2
    endpoint exists for the standard iPhone/iPad mailer and deliberately differs in behaviour, rewriting multipart structure
    for Deco-mail pictures and transcoding i-mode pictographs to Unicode emoji.'
  humanURL: https://www.docomo.ne.jp/service/developer/smart_phone/application/imap/
  baseURL: imaps://imap.spmode.ne.jp:993
  tags:
  - Email
  - IMAP
  - Protocol
  - Specification
  properties:
  - type: Documentation
    url: https://www.docomo.ne.jp/service/developer/smart_phone/application/imap/
  - type: APIReference
    url: https://www.docomo.ne.jp/binary/pdf/service/developer/smart_phone/application/imap/mail_imap_spec_260126.pdf
  - type: Conventions
    url: conventions/ntt-docomo-conventions.yml
common:
- type: DomainSecurity
  url: security/ntt-docomo-domain-security.yml
- type: Authentication
  url: authentication/ntt-docomo-authentication.yml
- type: WellKnown
  url: well-known/ntt-docomo-well-known.yml
- type: OpenIDConnectDiscovery
  url: well-known/ntt-docomo-openid-configuration.json
- type: Conformance
  url: conformance/ntt-docomo-conformance.yml
- type: Conventions
  url: conventions/ntt-docomo-conventions.yml
- type: Lifecycle
  url: lifecycle/ntt-docomo-lifecycle.yml
- type: StatusPage
  url: https://id.smt.docomo.ne.jp/src/dac/maintenance-g.html
- type: Packages
  url: packages/ntt-docomo-packages.yml
- type: LLMsTxt
  url: llms/ntt-docomo-llms.txt
- type: Website
  url: https://www.docomo.ne.jp/
- type: Website
  url: https://www.docomo.ne.jp/english/
- type: Documentation
  url: https://www.docomo.ne.jp/service/developer/
- type: TermsOfService
  url: https://www.docomo.ne.jp/service/developer/policy/index.html
- type: PrivacyPolicy
  url: https://www.docomo.ne.jp/utility/privacy/
- type: Support
  url: https://www.nttdocomo.co.jp/support/inquiry/
- type: HelpCenter
  url: https://www.docomo.ne.jp/support/
- type: Pricing
  url: https://www.docomo.ne.jp/charge/
- type: SignUp
  url: https://id.smt.docomo.ne.jp/cgi8/id/register
- type: GitHubOrganization
  url: https://github.com/docomo
- type: LinkedIn
  url: https://www.linkedin.com/company/ntt-docomo
- type: Blog
  url: https://www.docomo.ne.jp/english/info/media_center/pr/
- type: PressReleases
  url: https://www.docomo.ne.jp/info/news_release/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com