Skip to content
Live productRunning in production

Indonesian public data, behind one API key.

A REST API platform that turns scattered Indonesian public data into unified, documented endpoints. We designed it, built it, and operate it. Inspect the live product, then see the product decisions behind it.

Open apiindonesia.idBook a Fit Check
API groups
23API groups
MCP tools
77MCP tools
Districts covered
514Districts covered

Every figure on this page is published on the live product. Follow the link and check it.

What was built

One shape, one key, one place to ask.

The platform sits between scattered public sources and the application that needs them. Each layer below removes a decision the developer would otherwise have to make themselves.

  1. 01
    IngestScattered public sources brought together in one place, on one schedule, under one owner.
  2. 02
    NormalizeField names, casing, and identifiers made consistent across groups, so the same client code keeps working as you add another.
  3. 03
    ServeREST endpoints grouped by subject, documented per endpoint, and deployed on the Cloudflare edge network.
  4. 04
    MeterA single x-api-key header identifies the caller, and credits are counted per successful request.
  5. 05
    Expose23 API groups on the REST surface, plus 77 MCP tools for agent and assistant use.

Dataset catalog

PRODUCTION
WilayahProvinces down to villages, plus postal codes80,500+ villages
SchoolsSchool directory addressable by NPSN code93,500+ schools
UniversitiesHigher education institutions across the country4,300+ universities
HospitalsHospital directory across Indonesia2,900+ hospitals
Prayer timesDaily prayer schedules resolved by district514 districts
HolidaysNational holidays and shared leave datesBy year
SURFACE
23 API groups77 MCP toolsSingle x-api-key headerPer-endpoint documentationCloudflare edge network

The live product has the complete catalog and current figures.

How it is called

One header. One path. A response you can use.

There is no token exchange step and no client library to install first. Send the key in a header, read the JSON, move on. The panel on the right is drawn for illustration. The exact response for each endpoint is documented on the product itself.

Read the endpoint documentation
REQUEST AND RESPONSEEXAMPLE VIEW
REQUEST
GET/api/v1/wilayah/provinces
Host:apiindonesia.id
x-api-key:your_api_key
No token exchangeOnly successful calls cost credit
RESPONSE200 OK
{
  "success": true,
  "data": [
    { "code": "11", "name": "Aceh" },
    { "code": "31", "name": "DKI Jakarta" },
    { "code": "35", "name": "Jawa Timur" }
  ]
}

Illustrative shape and values. Endpoint paths, fields, and pagination are documented per endpoint on API Indonesia.

The platform layer

Endpoints are the easy half.

Anyone can return JSON. Turning that into something a stranger will pay for and depend on means keys, credits, plans, a dashboard, documentation, and a deployment somebody keeps an eye on. That is the part we have already shipped.

  1. 01

    Authentication

    One x-api-key header. No token exchange, no session, nothing a developer has to read twice before the first call works.

    We can build thisKey issuance, rotation, and revocation
  2. 02

    Quota accounting

    Credits are counted per request, and only successful requests consume them. A failure on our side is not something the caller pays for.

    We can build thisCredit ledgers and fair failure handling
  3. 03

    Plans and billing

    A free tier for evaluation, two paid tiers, and custom plans for anyone whose volume does not fit the published ones.

    We can build thisTier design, limits, and upgrade paths
  4. 04

    Dashboard

    Self-serve. Daily usage, remaining quota, and API key management, so nobody has to email support to find out where they stand.

    We can build thisUsage views developers trust
Published plans

What the product charges.

These are API Indonesia's own published prices, listed here so the commercial design is visible alongside the technical one. They are not khaisa.studio service rates.

Free

no cost
Rp 0
Allowance
1,000 requests per month
Rate limit
10 requests per second

For evaluation and small projects

Pro

per month
Rp 49.000
Allowance
50,000 credits
Rate limit
20 requests per second

For a product in production

Business

per month
Rp 149.000
Allowance
250,000 credits
Rate limit
60 requests per second

For higher volume and burst traffic

Custom plans

Volumes that do not fit the published tiers are handled as custom plans. Across every tier the same accounting rule applies: only successful requests consume credits.

Prices, quotas, and rate limits shown here are the figures published on API Indonesia at the time of writing. The live pricing page is the authority.

Check the live pricing
Next step

Have data that should be an API product?

Start with a short fit check. We look at the data, the callers, and the commercial shape, then say plainly whether it is worth building.

Book a Fit CheckOpen the live product