---
title: "Get BBPS Operators API Reference"
description: "List all active BBPS billers, optionally filtered by category and/or state."
canonical: "https://eps.eko.in/docs/bbps-get-operators"
---


> **Canonical URL:** https://eps.eko.in/docs/bbps-get-operators
> 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 BBPS Operators API Reference

`GET https://staging.eko.in/ekoapi/v3/customer/payment/bbps/operators`

List all active BBPS billers, optionally filtered by category and/or state.

**Behaviour**

- **Read-only**: Changes nothing; only returns data.

Returns the list of billers. Filter by `category`, `location`, or both, using the identifiers from Get Categories and Get Locations; omit both to list every biller.

The `operator_id` returned here is what you pass as **`phone_operator_code`** to Fetch Bill and Pay Bill — the names differ. `billFetchResponse` tells you whether the biller supports a live bill fetch. The list is returned under `param_attributes.list_elements`, not under `data`.

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

## Query parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| initiator_id | string | yes | Registered mobile number of the API user (see Platform Credentials). e.g. 9962981729 |
| client_ref_id | string | no | Unique reference ID per API call, generated by your system (10–20 characters; 10 recommended). The SDKs generate one for every non-GET call when you don't. e.g. 2026010100123456789 |
| category | number | no | Filter by category — the `operator_category_id` from Get Categories. e.g. 11 |
| location | number | no | Filter by state / UT — the `operator_location_id` from Get Locations. e.g. 35 |

## 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 | UI display hint only (-1/0 success, 1 failure, 2 initiated, 3 refund initiated, 4 refunded). Never branch on it — use `status` (and `tx_status` for financial APIs), or `response_type_id` where documented. |
| 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.param_attributes ⭐ | object | Wrapper for the biller list — returned at the top level of the response, not under `data`. |
| data.param_attributes.list_elements ⭐ | array | One entry per biller matching the filters. |
| data.param_attributes.list_elements.operator_id ⭐ | number | Biller identifier. Pass as `phone_operator_code` to Fetch Bill and Pay Bill. |
| data.param_attributes.list_elements.name ⭐ | string | Biller name. |
| data.param_attributes.list_elements.operator_category | number | Category this operator belongs to. |
| data.param_attributes.list_elements.location_id | number | Location this operator serves; `0` = pan-India. |
| data.param_attributes.list_elements.kyc_required | number | Whether customer KYC is required for this operator. |
| data.param_attributes.list_elements.billFetchResponse ⭐ | number | Whether the operator supports live bill fetch (`1` = yes). |
| data.param_attributes.list_elements.high_commission_channel | number | Whether the biller is available on the higher-commission channel. |

## Response types

Branch on `response_type_id` to decide the next call:

| response_type_id | Meaning | Next step |
| --- | --- | --- |
| 2461 | Biller list returned — read the chosen operator's input fields next. | [bbps-get-operator-parameters](https://eps.eko.in/docs/bbps-get-operator-parameters.md) |

## Example response

`response_type_id` `2461` — Biller list returned — read the chosen operator's input fields next.. Next step: [bbps-get-operator-parameters](https://eps.eko.in/docs/bbps-get-operator-parameters.md).

```json
{
  "response_status_id": 0,
  "param_attributes": {
    "list_elements": [
      {
        "operator_id": 159,
        "name": "ACT Fibernet",
        "billFetchResponse": 0,
        "high_commission_channel": 0,
        "kyc_required": 1,
        "operator_category": 1,
        "location_id": 0
      },
      {
        "operator_id": 541,
        "name": "Port Blair Municipal Council - Water",
        "billFetchResponse": 0,
        "high_commission_channel": 0,
        "kyc_required": 0,
        "operator_category": 11,
        "location_id": 35
      }
    ]
  },
  "response_type_id": 2461,
  "message": "BBPS operators fetch success",
  "status": 0
}
```

## Error scenarios

| Status | response_type_id | Scenario |
| --- | --- | --- |
| 200 | `-1` | Invalid or missing initiator_id |