GETGet Operator Parameters
Fetch the custom input fields required by a specific biller before payment.
Returns the operator-specific parameter schema — field names, labels, data types, and validation regex — needed to build a dynamic payment form. Also returns fetchBill (1 = mandatory Fetch Bill step) and BBPS (1 = show Bharat BillPay branding). Call this once per operator and cache the result.
Path parameters
| Field | Type | Required | Description |
|---|---|---|---|
operator_id | number | required | The operator/biller ID from the Get Operators response.e.g. 83 |
operator_idnumberRequiredThe operator/biller ID from the Get Operators response.
example: 83
Query parameters
| Field | Type | Required | Description |
|---|---|---|---|
initiator_id | string | required | Registered mobile number of the API user (see Platform Credentials).e.g. 9962981729 |
initiator_idstringRequiredRegistered mobile number of the API user (see Platform Credentials).
example: 9962981729
Headers
| Field | Type | Required | Description |
|---|---|---|---|
developer_key | string | required | Static API key issued to your account after KYC. |
secret-key | string | required | Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))). |
secret-key-timestamp | string | required | Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time. |
content-type | string | required | application/jsone.g. application/json |
developer_keystringRequiredStatic API key issued to your account after KYC.
secret-keystringRequiredDynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
secret-key-timestampstringRequiredCurrent time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
content-typestringRequiredapplication/json
example: application/json
Responses
statusnumberPrimary success indicator (0 = success).
messagestringHuman-readable response / error message.
response_status_idnumberGranular status id; see the shared error-codes table.
response_type_idnumberA unique id for every possible response shape (success or error) — useful for client logic branching and analytics.
dataobjectAPI-specific response payload.
fetchBillnumber1 = Fetch Bill API must be called before Pay Bill; 0 = direct payment allowed.
BBPSnumber1 = biller is on the BBPS network; display the Bharat BillPay logo per NPCI guidelines.
dataarrayList of input parameters required by this biller.
param_namestringAPI field name to send in the Fetch Bill / Pay Bill request.
param_labelstringUI label to display to the end user.
param_typestringInput type: Numeric, Decimal, AlphaNumeric, or List.
regexstringRegular expression to validate the user's input before submission.
error_messagestringValidation error message to show when the regex does not match.