Technical documentation for retrieving indicator values, standardized scores, and national ranks at prefecture, municipality, and neighborhood-block (chōchō) 220K grain from your programs, with sources attached. Assuming a commercial license, we publish the endpoints, authentication, rate limits, response schema, and pricing ranges. Only data from commercially distributable sources is delivered, and the source and processing level are always stated.
The following are the planned endpoint specifications (provided individually for now). Each row also shows whether the source is commercially distributable. Sources marked "Individual license" are delivered only once their usage terms have been confirmed individually.
| Endpoint | Description | Grain | License |
|---|---|---|---|
GET /api/v1/metrics | Metric catalog (commercially distributable metrics only) | — | Distributable |
GET /api/v1/prefectures/{id}/indicators | Per-prefecture indicator values + standardized scores + national ranks | Prefecture | Distributable |
GET /api/v1/municipalities/{id}/indicators | Per-municipality indicator values + standardized scores + national ranks | Municipality | Distributable |
GET /api/v1/chocho/{code}/scores | Neighborhood-block 7-domain scores (some require individual licensing by source terms) | Neighborhood block | Individual license Some content requires individual licensing by the source's usage terms |
Note: badges are based on the per-source commercial-distribution registry (audited 2026-06-10). Sources marked "Individual license" are delivered after confirming the usage terms for the specific content.
Pass your API key as a Bearer token in the Authorization header. API keys are issued after we receive your inquiry (issued individually for now).
# Example: retrieve per-prefecture indicator values
curl -H "Authorization: Bearer <api_key>" \
https://www.nippon-pulse.com/api/v1/prefectures/13/indicatorsNote: replace <api_key> with your issued key. Treat the key as a secret — do not write it directly into public repositories or client-side code.
Per-tier rate limits and quotas are set individually according to your usage scale (the figures below are indicative).
| Plan | Rate limit / quota (indicative) |
|---|---|
| Individual pro | Around 10,000 requests per month. |
| Enterprise | No fixed cap (by consultation). Designed individually to your usage scale. |
Responses are returned as JSON. Each value carries its source (source) and reference point in time (as_of) alongside, and the response headers also include X-Data-As-Of / X-Source. The following is an example showing the structure (actual values and grain vary by target).
{
"area": { "type": "prefecture", "id": "13", "name": "Tokyo" },
"as_of": "2024-01-01",
"indicators": [
{
"metric_id": "fiscal_capacity_index",
"label": "Fiscal Capacity Index",
"value": 1.18,
"unit": "index",
"deviation": 71.2,
"rank": 1,
"rank_total": 47,
"source": {
"name": "MIC Local Public Finance Survey",
"license": "Standard Terms of Use for Government (v2.0)",
"url": "https://www.e-stat.go.jp/"
},
"as_of": "2024-01-01"
}
]
}Note: the above is an example showing the structure. The standardized score (deviation) and national rank (rank) are computed values from our own fixed algorithms, and each value is tied to a source and a reference point in time.
Pricing is quoted individually according to the scale, use, update frequency, and redistribution scope you need. The ranges below are indicative for your consideration (not fixed prices).
Quoted individually by scale, update frequency, and redistribution scope. The target data, grain, and delivery format (CSV / Parquet / JSON, etc.) are settled by discussion.
Metered billing per 1,000 requests, designed individually for the validation phase. The fixed unit price is quoted once we hear your usage scale.
One-time extractions specified by area, grain, and period. Scope and license terms are agreed individually.
All are individual quotes. Tell us your usage picture (target area, grain, update frequency, expected request volume) and we'll follow up with the scope and license terms by discussion.
Only data from commercially distributable sources is delivered. We publish each source's commercial-distribution class, attribution requirement, and terms of use (audited 2026-06-10). Transparency lets you use this for your internal review before adoption.
| Source | Terms of use | Commercial | Attribution |
|---|---|---|---|
| 政府統計 (e-Stat・各府省) | 政府標準利用規約 (第2.0版) — CC BY 4.0 互換 | Distributable | Required |
| 国土数値情報 (KSJ・MLIT) | PDL1.0 (既定) / 一部 dataset は CC BY 4.0 や旧約款 | Individual license | Required |
| 不動産情報ライブラリ (REINFOLIB・MLIT) | REINFOLIB 利用規約 (+ 原典 使用許諾条件) | Individual license | Required |
| 気象庁 (JMA・予報/警報/観測) | 気象庁 公共データ利用規約 (第1.0版) + 気象業務法 | Display only | Required |
| 国土地理院 (GSI・統計表) | 国土地理院コンテンツ利用規約 (政府標準利用規約準拠) | Distributable | Required |
| 議員報酬 (議長会調査 + 各議会条例) | 議長会 調査結果 + 地方議会 報酬条例 | Individual license | Required |
| YouTube (ライブカメラ) | YouTube 利用規約 / API Services Terms | Display only | Not required |
Note: sources whose commercial distribution is "Individual license" or "Display only" are kept to on-site display, and only items that have passed individual usage-permission checks are placed in data provision. The Real Estate Information Library and Japan Meteorological Agency data carry caveats on distribution arising from the original source's usage terms and the Meteorological Service Act.
First, you can check the structure with a free sample CSV usable commercially with attribution. For API-key issuance and a quote, tell us your usage picture via the inquiry form.
Note: the data shown and delivered on Nippon Pulse is handled within the scope permitted by the public bodies. For dataset provision, API integration, or custom extraction, please use /feedback; for coverage or contributions, please use /press.