---
title: "Activate BBPS Service API Reference"
description: "Onboard an agent/retailer for BBPS bill payment services using service code 53."
canonical: "https://eps.eko.in/docs/bbps-activate-service"
---


> **Canonical URL:** https://eps.eko.in/docs/bbps-activate-service
> 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.

# Activate BBPS Service API Reference

`PUT https://staging.eko.in/ekoapi/v3/user/service/activate`

Onboard an agent/retailer for BBPS bill payment services using service code 53.

Before a retailer can process BBPS payments, the BBPS service (service_code = 53) must be activated for their `user_code`. This is a one-time setup call per agent. After activation, verify the status using the User Service Enquiry API. The agent's GPS coordinates (`latlong`) are mandatory for production compliance.

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

## Body 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 |
| client_ref_id | string | no | Unique reference id per API call, generated by your system. e.g. REQ-20260101-001 |
| service_code | number | yes | Service identifier for BBPS. Always 53. e.g. 53 |
| latlong | string | yes | Agent's GPS coordinates as `latitude,longitude`. Mandatory for BBPS agent activation. e.g. 28.6139,77.2090 |

## 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.service_code ⭐ | number | The service code that was activated. |
| data.service_status ⭐ | string | Activation status for the service on the agent's account. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "service_code": 53,
  "latlong": "28.6139,77.2090"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "BBPS service activated successfully",
  "response_type_id": 1388,
  "data": {
    "service_code": 53,
    "service_status": "activated"
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Service already activated for this agent |