Skip to main content
POST
NPWP Verification

Authorizations

Authorization
string
header
required

Use your API token as a Bearer token in the Authorization header.

Body

application/json
npwp
string
required

15- or 16-digit NPWP. Separators are accepted and removed before lookup.

Pattern: ^[0-9 .-]{15,20}$
Example:

"00.000.000.0-000.000"

metadata
object

Optional client-defined values echoed in completed and source-error responses.

Response

The source returned a completed verified or rejected result. Both outcomes use HTTP 200.

success
boolean
required
Example:

true

message
string
required
data
object
required

CamelCase result fields from the corresponding Indonesia v3 verification.

verificationStatus
enum<string>
required
Available options:
VERIFIED,
REJECTED
verificationStatusCode
enum<integer>
required

3 = Verified, 1 = Rejected.

Available options:
3,
1
transactionId
string<uuid>
required
verificationType
string
required
createdAt
string
required
Example:

"2026-09-02 08:00:00+0000"

metadata
object | null

Optional client-defined values echoed in completed and source-error responses.