ready-to-use endpoints in this product, with JSON responses and consistent error handling.
Indonesian administrative region data from province down to village level, complete with region codes, postal codes, and coordinates. All list endpoints support pagination.
Indonesian administrative region data from province down to village level, complete with region codes, postal codes, and coordinates. All list endpoints support pagination.
ready-to-use endpoints in this product, with JSON responses and consistent error handling.
Can be tried with the 3,000 credit signup bonus, then used in production through one API Indonesia key.
https://use.apiindonesia.id/api/v1/wilayah/provinsiReturns a list of all provinces in Indonesia.
The Regions API fits apps that need a clean Indonesian address structure: provinces, regencies/cities, districts, down to villages. It works well for checkout, onboarding, branch search, service areas, and region analysis without shipping static address lists in the frontend.
You need cascading address dropdowns that stay consistent across web, mobile, and admin panels.
You need region codes to connect user records with internal reporting.
You need basic coordinates for location search or service-area estimates.
For legal address validation, pair this API with your own business rules. Region data gives structure, not proof of someone’s domicile.
This section separates the product page from the docs. The docs explain how to call endpoints; this page explains why the endpoints make sense for your feature.
curl "https://use.apiindonesia.id/api/v1/wilayah/provinsi?page=1&per_page=20" \
-H "x-api-key: YOUR_API_KEY"{
"data": [
{
"id": "32",
"code": "32",
"name": "JAWA BARAT",
"alt_name": "Jawa Barat",
"lat": -6.914744,
"lng": 107.609811,
"is_active": 1
}
],
"meta": {
"total": 38,
"page": 1,
"per_page": 20,
"total_pages": 2
}
}Start with a one-time 3,000 credit bonus at signup (Rp3,000, granted after email verification), with no monthly allowance. Upgrade to Pro or Business, or buy pay as you go credits when you need a one-time top-up. One credit equals Rp1, and the price is per product per hit: a successful public data request costs 2 credits. A failed hit is free. Payments are processed through Sumopod.
Yearly saves 2 months
Do you want to skip subscriptions? Top up credits once from the dashboard and use them until they run out. One credit equals Rp1: a successful public data request costs 2 credits (Rp2), and a failed request is never charged.
Open dashboardFor trying the API and early integration.
For projects that are starting to get real usage.
For production apps with higher traffic.
For high volume, SLA, or company contracts.
Quick answers to common questions about getting started, the signup bonus, API key security, data sources, and Sumopod billing.