Skip to main content
POST

Authorizations

Authorization
string
header
required

JWT Bearer token obtained from /api/v1.0/access-token/b2b

Headers

X-PARTNER-ID
string
required

Your unique partner API key

Accept
string
default:application/json
required
Content-Type
string
default:application/json
required

Body

application/json
command
enum<string>
required

Biller command, mapped 1:1 to a flat category (pdam→PDAM, plnpos→PLNPOS, plnnon→PLNNON, intv→INTV, bpjsks→BPJSKS, putk→PUTK, bputk→BPUTK, mobpos→MOBPOS, educ→EDUC, prop→PROP, pbb→PBB)

Available options:
pdam,
plnpos,
plnnon,
intv,
bpjsks,
bputk,
putk,
mobpos,
educ,
prop,
pbb
Example:

"plnpos"

data
object
required

Response

Inquiry successful

V3 postpaid inquiry success response. Same shape as V2: the core fields below are always present; extra vendor fields (customer_name, period, late_fee, ...) depend on the command template.

command
string
Example:

"plnpos"

response_code
string
Example:

"00"

response_text
string
Example:

"Inquiry success"

data
object