---
title: "Get Operator Parameters API Reference"
description: "Fetch the custom input fields required by a specific biller before payment."
canonical: "https://eps.eko.in/docs/bbps-get-operator-parameters"
---


> **Canonical URL:** https://eps.eko.in/docs/bbps-get-operator-parameters
> This is a machine-readable Markdown version of the page for AI agents and LLMs. The primary (HTML) version lives at the canonical URL above.

# Get Operator Parameters API Reference

`GET https://staging.eko.in/ekoapi/v3/customer/payment/bbps/operator/{operator_id}/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.

> View product & pricing details: [Bharat Bill Payment System (BBPS)](https://eps.eko.in/products/bbps-api.md)

## Path parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| operator_id | number | yes | The operator/biller ID from the Get Operators response. e.g. 83 |

## Query parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| initiator_id | string | yes | Registered mobile number of the API user (see Platform Credentials). e.g. 9962981729 |

## Headers

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| developer_key | string | yes | Static API key issued to your account after KYC. |
| secret-key | string | yes | Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))). |
| secret-key-timestamp | string | yes | Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time. |
| content-type | string | yes | application/json e.g. application/json |

## Response

⭐ marks fields highlighted as verifiable.

| Field | Type | Description |
| --- | --- | --- |
| status | number | Primary success indicator (0 = success). |
| message | string | Human-readable response / error message. |
| response_status_id | number | Granular status id; see the shared error-codes table. |
| response_type_id | number | A unique id for every possible response shape (success or error) — useful for client logic branching and analytics. |
| data | object | API-specific response payload. |
| data.fetchBill ⭐ | number | 1 = Fetch Bill API must be called before Pay Bill; 0 = direct payment allowed. |
| data.BBPS | number | 1 = biller is on the BBPS network; display the Bharat BillPay logo per NPCI guidelines. |
| data.data | array | List of input parameters required by this biller. |
| data.data.param_name ⭐ | string | API field name to send in the Fetch Bill / Pay Bill request. |
| data.data.param_label | string | UI label to display to the end user. |
| data.data.param_type | string | Input type: Numeric, Decimal, AlphaNumeric, or List. |
| data.data.regex | string | Regular expression to validate the user's input before submission. |
| data.data.error_message | string | Validation error message to show when the regex does not match. |

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Success",
  "response_type_id": 1388,
  "data": {
    "fetchBill": 1,
    "BBPS": 1,
    "data": [
      {
        "param_name": "utility_acc_no",
        "param_label": "Consumer Number",
        "param_type": "Numeric",
        "regex": "^[0-9]{10,12}$",
        "error_message": "Please enter a valid 10-12 digit consumer number."
      }
    ]
  }
}
```