ready-to-use endpoints in this product, with JSON responses and consistent error handling.
Structural validation for NIK, NPWP, phone numbers, and bank accounts — no lookup to official databases. Includes Indonesian bank code list.
Structural validation for NIK, NPWP, phone numbers, and bank accounts — no lookup to official databases. Includes Indonesian bank code list.
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/validasi/bankReturns bank codes with valid account number lengths.
The Validation API fits cleaning inputs before data enters your system: NIK, NPWP, phone numbers, and bank accounts. It focuses on structural validation, not identity checks against official databases.
Onboarding forms often fail because NIK, NPWP, phone, or bank-account formats are inconsistent.
The app wants to give immediate feedback before submission.
Teams need to reduce dirty data before KYC, billing, or disbursement workflows.
Structural validation does not prove that a number belongs to someone or is active at the related institution.
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/validasi/bank" \
-H "x-api-key: YOUR_API_KEY"{
"data": [
{ "code": "014", "name": "Bank BCA", "short_name": "BCA", "min_account_length": 10, "max_account_length": 10 }
]
}Sebelum bikin eFaktur, validasi format NPWP dan konversi jumlah nilai like 250.000 ke bentuk terbilang otomatis via API. Contoh kode curl dan JavaScript disertakan.
Cara pakai API cek NIK untuk validasi format 16 digit pada onboarding HR dan fintech, lengkap dengan batasan etika: validasi struktural bukan verifikasi Dukcapil.
Normalisasi nomor HP Indonesia dan cek format NPWP sebelum generate faktur — mengurangi pesanan B2B yang gagal divalidasi manual.
No. It only checks structure: 16-digit NIK and 15-digit NPWP, and extracts the region and birth-date codes from a NIK. There is no lookup against Dukcapil or DJP databases.
GET /api/v1/validasi/bank returns bank codes with min_account_length and max_account_length for each bank.
To reject obviously wrong input before processing, such as a mistyped NIK in a signup form, without paying for official verification.