---
type: "product"
title: "BBPS API / Bharat Connect API for Bill Payments in India"
description: "Integrate BBPS API to enable bill payments for electricity, gas, water, DTH, broadband, insurance, and 200+ biller categories. RBI-compliant infrastructure."
category: "payment"
canonical: "https://eps.eko.in/products/bbps-api"
---


> **Canonical URL:** https://eps.eko.in/products/bbps-api
> 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.

# BBPS API for Utility Bill Payments in India

Integrate Eko’s BBPS API to let customers fetch bills, pay utility bills, and track transaction status across electricity, gas, water, DTH, broadband, FASTag, insurance, credit card, EMI, LPG, and loan repayment categories.

_Complete bill payment ecosystem with 200+ biller categories_

To get started, fill the form at https://eps.eko.in/signup (with your name, mobile number and email) or call us at +919513181707

## Features

- 200+ Biller Categories: Access to extensive biller network covering electricity, gas, water, insurance, and more.
- Instant Bill Fetch: Fetch outstanding bill amounts in real-time before payment processing.
- Unified API: Single API integration for all biller categories - no separate integrations needed.
- Transaction Tracking: Complete visibility into transaction status with detailed reporting.
- Receipt Generation: Auto-generated receipts for every successful transaction.

## Benefits

- Simplified Integration: Easy-to-read API documentation and 24x7 integration support for quick go-live.
- Best Success Rate: Industry-leading success rates with smart retry mechanisms.
- Earn Commission: Attractive commissions on all types of bill payments processed through your platform.
- Extensive Biller Network: Access to 20,000+ billers across all major categories in India.
- Real-time Confirmation: Instant payment confirmation with transaction reference numbers.
- Customer Retention: Keep customers engaged with recurring bill payment reminders and services.

## Supported Types

- Electricity
- Gas
- Water
- DTH
- Broadband
- Mobile Recharge
- Fastag
- Insurance
- Credit Card
- EMI
- LPG Gas
- Loan Repayment

## Use Cases

- Banking Apps
- Fintech Platforms
- Payment Aggregators
- E-commerce Platforms
- Retail Networks
- Agent Banking
- Corporate Solutions

## API Preview — Fetch BBPS Bill

`GET /customer/payment/bbps/bill`

### Example inputs

| Field | Value |
| --- | --- |
| Phone Operator Code | 53 |
| Utility Acc No | 3287820071 |
| Confirmation Mobile No | 9903457748 |
| Sender Name | Asaad |
| Category | 8 |
| Client Ref Id | 2026010100123456789 |
| Source Ip | 192.168.1.1 |
| District Discome | Lucknow-MVVNL |
| State | 1 |
| Communication | 0 |

### Example outputs

| Field | Value |
| --- | --- |
| Amount | 2870.0 |
| Utilitycustomername | Amit Kumar |
| Bill Due Date | 20260728 |
| Customer Id | 3287820071 |

## API Preview — Pay BBPS Bill

`POST /customer/payment/bbps`

### Example inputs

| Field | Value |
| --- | --- |
| Phone Operator Code | 53 |
| Utility Acc No | 3287820071 |
| Confirmation Mobile No | 9903457748 |
| Sender Name | Asaad |
| Category | 8 |
| Amount | 2870 |
| Utilitycustomername | Amit Kumar |
| Client Ref Id | 2026010100123456789 |
| Source Ip | 192.168.1.1 |
| District Discome | Lucknow-MVVNL |
| Communication | 0 |

### Example outputs

| Field | Value |
| --- | --- |
| Tid | 3570553488 |
| Tx Status | 0 |
| Amount | 2870.0 |
| Balance | 46537.3 |

## API Preview — Get BBPS Categories

`GET /customer/payment/bbps/categories`

### Example outputs

| Field | Value |
| --- | --- |
| Operator Category Id | 8 |
| Operator Category Name | Electricity |

## API Preview — Get BBPS Locations

`GET /customer/payment/bbps/locations`

### Example outputs

| Field | Value |
| --- | --- |
| Operator Location Id | 06 |
| Operator Location Name | Haryana |

## API Preview — Get BBPS Operators

`GET /customer/payment/bbps/operators`

### Example inputs

| Field | Value |
| --- | --- |
| Category | 11 |
| Location | 35 |

### Example outputs

| Field | Value |
| --- | --- |
| Operator Id | 541 |
| Name | Port Blair Municipal Council - Water |
| Bill Fetch Response | 0 |

## API Preview — Get Operator Parameters

`GET /customer/payment/bbps/operator/{operator_id}/parameters`

### Example inputs

| Field | Value |
| --- | --- |
| Operator Id | 5 |

### Example outputs

| Field | Value |
| --- | --- |
| Operator Name | BSNL  Prepaid |
| Fetch Bill | 0 |
| Param Name | utility_acc_no |

## API Preview — Get Operator Code and Circle

`GET /customer/payment/bbps/recharge/{customer_mobile}/operator`

### Example inputs

| Field | Value |
| --- | --- |
| Customer Mobile | 9876543210 |

## API Preview — Get Recharge Plans

`GET /customer/payment/bbps/recharge/{customer_mobile}/operator/plans`

### Example inputs

| Field | Value |
| --- | --- |
| Customer Mobile | 9876543210 |
| Phone Operator Code | 400 |
| Circleid | 5 |

### Example outputs

| Field | Value |
| --- | --- |
| Amount | 349 |
| Validity | 28 Days |
| Plan Description | 1.5 GB/day + Unlimited Calls ... |

## API Preview — Get District Discome (UPPCL)

`GET /customer/payment/bbps/operators/190/district-discome`

### Example outputs

| Field | Value |
| --- | --- |
| Label | Lucknow |
| Value | Lucknow-MVVNL |

## Integration Steps

1. **[Sign Up](/console)** — Sign up in minutes with your mobile number (OTP verify).
2. **Verify Identity** — Complete your basic KYC with PAN and address details to verify your identity.
3. **Test APIs Live** — Load funds into your wallet and test the verification APIs live — evaluate before you integrate.
4. **[Integrate with AI](/ai)** — Ready to build? Visit our AI hub for free plugins & tools to integrate faster.
5. **UAT Testing** — Complete UAT testing with all biller categories.
6. **Go Live** — Launch with production credentials and start billing!

## FAQs

### Is BBPS API available 24/7?
Yes, BBPS services are available 24/7. However, some billers may have specific operating hours for payment processing.

### How is the bill payment amount protected?
Bill amounts are **fetched live from the biller**. Whenever a biller supports bill-fetch, the amount paid can **never exceed the fetched bill amount**.

### How do I get started?
Four steps: **sign up** at the [developer console page](/console), verify your identity with PAN and address details, load your wallet to test the APIs live, then integrate and go live. Sandbox credentials are issued immediately — you can call your first endpoint before any paperwork clears.

### What is EPS?
**EPS (Eko Platform Services)** is the technology arm of Eko — the developer tools, AI tooling and APIs that power modern fintech integration, from money transfer and AePS to identity verification.

### What are the different ways to integrate with Eko EPS?
Three paths, pick whichever suits your stack:

- Call the **REST APIs** directly.
- Use our official **Node.js, Python, PHP, Go or Java SDKs** to skip request-signing boilerplate.
- Let an **AI coding agent** build it via our [MCP server and agent skills](/ai#install).

For multi-step flows (onboard a sender, *then* transfer) start from a [transaction-flow recipe](/recipe) rather than wiring single endpoints together yourself.

### How does API authentication work?
Each request carries your static `developer_key` header plus a per-request `secret-key` header — an **HMAC-SHA256** signature of the current timestamp, keyed by your access key. The access key itself is **never sent over the wire**. You receive UAT keys on signup and production keys after KYC.

The [How Authentication Works](/docs/how-auth-works) guide has the full signing recipe in five languages plus an **in-browser playground** that generates and verifies a real `secret-key` against your own access key.

### Why does my API call return 401 Unauthorized?
Authentication failed. For the known causes, the response body's `status` names the check that failed:

- `2483` — The developer_key is wrong.
- `2484` — The secret-key (signature) is wrong.
- `2485` — The secret-key-timestamp is more than 2 minutes older or newer than the server clock, or was reused from an earlier request.
- `2486` — The secret-key-timestamp is not in milliseconds (13 digits) — often seconds (10 digits).
- `2487` — The secret-key or secret-key-timestamp header is missing.

If your signature checks out in the [secret-key playground](/docs/how-auth-works#try-it-secret-key-playground) and you still get a `401`, make sure the base URL matches your keys (UAT vs production) and, in production, that your server's IP is whitelisted.

### Is there a sandbox environment for testing?
Yes. A full **sandbox** is available immediately on signup — test your integration end-to-end before going live, no commitment required. For offline work you can also run our [mock server](/ai#artifacts) (`npx -y @ekoindia/eps-mock-server`) and get canned responses with no network calls at all.

### What are the sandbox and production base URLs?
Sandbox and production share the same paths and differ **only** by base URL:

- UAT / Sandbox — `https://staging.eko.in/ekoapi/v3`
- Production — `https://api.eko.in/ekoicici/v3`

A common cause of failures is calling the sandbox URL with live credentials, or vice-versa — **make sure the base URL matches the keys you are using**.

### Do I need to whitelist my server IP?
It's optional. **IP whitelisting** is available for **production** access as an extra layer of security — share your **static public (server) IP** with us and we'll whitelist it.

### Can an AI coding agent build the integration for me?
Yes — that is the fastest path. Point your agent (Claude Code, Codex, Cursor, Copilot, …) at our **MCP server** and it can look up any endpoint, generate correctly-signed requests, and scaffold the integration in your own stack. Install it in [one step from the AI hub](/ai#install), or start from a [ready-made prompt](/ai#quick-start).

We also publish an **OpenAPI 3.1 spec**, a **Postman collection** and per-agent **context packs** (`AGENTS.md`, `CLAUDE.md`, `.cursorrules`) so an agent has the ground truth instead of guessing.

### What response times can I expect?
Most verification APIs return in **real time with sub-second responses**, and 99th-percentile latency stays under two seconds across verification endpoints. Transaction APIs (DMT, AePS, BBPS) respond within seconds.

### Can the API handle high volumes?
Yes. The API is designed to handle **large-scale volumes** reliably without performance degradation.

### How is API usage billed?
Usage is billed **per successful API call** with no minimum commitment. Volume-based pricing tiers are available — see the [pricing calculator](/pricing) for indicative rates, or contact our team for a custom quote.

## API Endpoints

- **Bill Payment Lookups**
  - [Get BBPS Categories](https://eps.eko.in/docs/bbps-get-categories.md) (GET)
  - [Get BBPS Locations](https://eps.eko.in/docs/bbps-get-locations.md) (GET)
  - [Get BBPS Operators](https://eps.eko.in/docs/bbps-get-operators.md) (GET)
  - [Get Operator Parameters](https://eps.eko.in/docs/bbps-get-operator-parameters.md) (GET)
  - [Get District Discome (UPPCL)](https://eps.eko.in/docs/bbps-district-discome.md) (GET)
- **Recharge Lookups**
  - [Get Operator Code and Circle](https://eps.eko.in/docs/bbps-operator-code-circle.md) (GET)
  - [Get Recharge Plans](https://eps.eko.in/docs/bbps-recharge-plans.md) (GET)
- [Fetch BBPS Bill](https://eps.eko.in/docs/bbps-fetch-bill.md) (GET)
- [Pay BBPS Bill](https://eps.eko.in/docs/bbps-pay-bill.md) (POST)

## API Documentation

- [Full developer docs](https://eps.eko.in/docs/bbps-fetch-bill)

- [Site index](https://eps.eko.in/index.md): Full list of API products, industries, and solution packs