---
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.

Returns every currently active BBPS biller. Use `category` and `location` query parameters to narrow results. The `billFetchResponse` flag on each operator tells you whether the Fetch Bill step is mandatory before payment. Operators that are temporarily disabled are excluded from the response — poll this endpoint periodically to keep your list fresh.

> 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 |
| user_code | string | yes | User code of the retailer/agent the service is run for. e.g. 20810200 |
| category | number | no | Filter by category — use the `id` from Get Categories. e.g. 5 |
| location | number | no | Filter by state/circle — use the `id` from Get Locations. e.g. 7 |

## 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.operators | array | List of active BBPS billers matching the filters. |
| data.operators.operator_id ⭐ | number | Unique operator identifier. Pass this value in Fetch Bill and Pay Bill requests. |
| data.operators.operator_name ⭐ | string | Display name of the biller. |
| data.operators.category_id | number | Category this operator belongs to. |
| data.operators.billFetchResponse ⭐ | number | 1 = must call Fetch Bill API before Pay Bill; 0 = can pay directly. |
| data.operators.high_commission_channel | number | 0 = instant settlement (default); 1 = delayed channel with higher commissions. |

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Success",
  "response_type_id": 1388,
  "data": {
    "operators": [
      {
        "operator_id": 83,
        "operator_name": "BSES Rajdhani",
        "category_id": 5,
        "billFetchResponse": 1,
        "high_commission_channel": 0
      },
      {
        "operator_id": 84,
        "operator_name": "BSES Yamuna",
        "category_id": 5,
        "billFetchResponse": 1,
        "high_commission_channel": 0
      },
      {
        "operator_id": 87,
        "operator_name": "Tata Power Delhi Distribution",
        "category_id": 5,
        "billFetchResponse": 0,
        "high_commission_channel": 0
      }
    ]
  }
}
```