This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with 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 so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
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.
APIs.json: https://raw.githubusercontent.com/api-evangelist/ntt-docomo/refs/heads/main/apis.yml
- 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
There is no NTT DOCOMO developer portal. Every conventional developer host on docomo.ne.jp — developer., developers., docs., api., opengateway. — fails DNS resolution, and /developer/, /developers/, /api/ and /opengateway/ all return HTTP 404 on the main site.
The first-party programme that once existed is gone. docomo Developer support (dev.smt.docomo.ne.jp) opened in October 2013 as an API marketplace carrying DOCOMO and partner APIs — speech recognition, speech synthesis, chat dialogue, transit search, image recognition. It shut down on 31 March 2021, and the DNS record has since been removed entirely, so even the archived documentation is off the live web. Third-party SDKs written against it now point at a host that does not resolve.
One public developer page survives — www.docomo.ne.jp/service/developer/ (HTTP 200). It is open and requires no registration, but it documents handset and content technology (Machi-Chara, Deco-mail, emoji packages, NFC / Osaifu-Keitai, docomo Mail features, device spec lists, sp-mode server IP ranges), not an HTTP API. No keys, no sandbox, no REST reference, no machine-readable definition.
No OpenAPI, Swagger or AsyncAPI definition is published anywhere on an NTT DOCOMO host. This repository has no openapi/ directory because there was nothing real to harvest.
Press release, not implementation.
In its own 30 January 2026 release, DOCOMO states it "has participated in the GSMA Open Gateway initiative" and that it has collaborated with Aduna — the Ericsson-and-carrier joint venture — since June 2025, concluding a formal partnership agreement on 29 January 2026 to distribute its network APIs internationally. The release names two starting APIs:
- Number Verification
- SIM Swap
Nothing is callable. There is no CAMARA endpoint, no CAMARA OpenAPI hosted on a DOCOMO domain, no sandbox, no DOCOMO-branded Open Gateway portal and no credential path. And as of 2026-07-25, Aduna's own operator wall does not yet list NTT DOCOMO among its connected operators. A developer cannot call a DOCOMO network API today by any documented public route — not first-party, and not yet through the aggregator DOCOMO announced.
No TM Forum Open API conformance certification was confirmed for NTT DOCOMO, Inc. No public NEF/SCEF, network-slicing or edge/MEC API was found.
NTT DOCOMO reaches developers only through intermediaries:
- Network APIs → Aduna (announced; not yet live on the aggregator).
- Carrier billing (d払い) → payment gateways such as GMO Payment Gateway, PAYGENT and SB Payment Service, who carry the integration specs DOCOMO does not publish.
- Enterprise / wholesale →
docomo.ne.jp/bizredirects towww.ntt.com, the site of NTT DOCOMO BUSINESS, Inc. (the renamed NTT Communications), a separate legal entity on a separate domain, which runs the group's actual login-gated API gateway portal atdeveloper.ntt.com. That entity is profiled separately in this network asntt-comand is not counted here.
DOCOMO's carrier identity service for businesses — OpenID Connect social login backed by network line authentication and device biometrics, against roughly 90 million d ACCOUNT registrations and approximately 2,000 implemented sites.
- Human URL: https://id.smt.docomo.ne.jp/src/index_business.html
- Base URL:
https://conf.uw.docomo.ne.jp/
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):
- issuer
https://conf.uw.docomo.ne.jp/ - authorization endpoint
https://id.smt.docomo.ne.jp/cgi8/oidc/authorize - token endpoint
https://conf.uw.docomo.ne.jp/token - userinfo endpoint
https://conf.uw.docomo.ne.jp/userinfo response_types_supported: [code],subject_types_supported: [pairwise], ID token signing HS256/RS256
No backchannel_authentication_endpoint is advertised — CIBA, the grant CAMARA specifies for network-based authorization, does not appear. The integration manual and support libraries download only after a use application and DOCOMO's review. No OpenAPI definition is published.
The one machine-interface specification NTT DOCOMO publishes openly, without registration. It documents how a mail client connects to the docomo Mail service over IMAP, distributed as a 96-page Japanese PDF (mail_imap_spec_260126.pdf, HTTP 200, application/pdf, 1,229,737 bytes, revision dated 2026-01-26). This is an IMAP protocol interface, not an HTTP API — no REST surface, no OpenAPI, no key issuance, no sandbox.
- Website
- Website (English)
- Developer Information
- Developer Terms
- GitHub — organisation exists, zero public repositories
- Press Releases (English)
- Press Releases (Japanese)