API Coverage Across Japan and Korea: 157 Providers, 436 APIs

API Coverage Across Japan and Korea: 157 Providers, 436 APIs

Japan & Korea maps to 157 providers publishing 436 indexed APIs on the network — two of the world’s most mature industrial economies, with API concentration in manufacturing, automotive, robotics, gaming, and deep B2B consumer-tech integration.

The cohort

Provider APIs Band Score
PAY.JP 14 exemplar 73.2
PortOne 20 exemplar 66.3
Soracom 45 strong 63.9
KUFU 2 developing 54.5
Papago 5 developing 52.4
JPX (Japan Exchange Group) 8 developing 52.0

Also in the region: 151 more providers.

Two payments companies at the top, and then a 9-point drop to a connectivity platform, and another 9 to everything else.

Payments leads, and that is not obvious

PAY.JP at 73.2 and PortOne at 66.3 are the region’s two strongest entries, and both are payments infrastructure — Japanese and Korean respectively.

That is a more interesting result than it looks, because both markets have unusually entrenched domestic payment behaviour. Japan ran on konbini payments, bank transfers and domestic card rails long after the rest of the world standardised; Korea’s card infrastructure and identity requirements have historically made cross-border integration genuinely hard.

Companies that succeeded in those markets did so by making the local complexity callable. The score reflects a decade of that work.

Soracom is the structural entry

Soracom publishes 45 APIs — the largest surface in the regional cohort — as an IoT connectivity control plane. It scores 63.9, strong.

Japan’s industrial base is the reason this company’s shape makes sense. Manufacturing, automotive and robotics are the region’s API-relevant strengths, and all three run on device fleets that need SIM provisioning, connectivity management and telemetry as programmable operations rather than as procurement contracts.

Soracom is what happens when the connectivity layer beneath an industrial economy gets an API.

The long tail sits in the developing band

KUFU (2 APIs, 54.5), Papago (5, 52.4) and JPX (8, 52.0) are all developing, and the pattern is consistent: small published surfaces from organisations with far more capability than they expose.

JPX is the clearest case. The Japan Exchange Group operates one of the world’s largest securities markets and publishes 8 indexed APIs at 52.0. That is not a technology limitation. Market data has historically been a licensed, contracted, high-margin product, and the incentive to publish it as an open, well-described API is weak when the current distribution model works.

The caveat on the count

Region mapping here derives from provider tags and name-pattern matching. It surfaces what is explicitly signalled in the structured data and deliberately does not infer beyond it — so a Japanese or Korean company that never tags itself geographically will not appear in this cut. Read 157 as a floor.

Takeaway

436 APIs across 157 providers, led by two domestic payments platforms that made local complexity callable, anchored structurally by an IoT connectivity control plane, with a long tail of institutions publishing far less than they could. Japan and Korea’s API surface is narrower than their industrial weight — and the gap is a licensing decision, not a technical one.

Browse the region at apis.io/regions/japan-korea/, and every sales region at apis.io/regions/.

← The HubSpot Associations API: 652 JSON Schemas and api.example.com
Eight More APIs Land on APIs.io →