---
title: "Activate Service for User API Reference"
description: "Activate a specific service (by service code) for one of your agents/retailers."
canonical: "https://eps.eko.in/docs/activate-user-service"
---


> **Canonical URL:** https://eps.eko.in/docs/activate-user-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 Service for User API Reference

`PUT https://staging.eko.in/ekoapi/v3/admin/network/agent/{user_code}/service/{service_code}/activate`

Activate a specific service (by service code) for one of your agents/retailers.

Enables a service for the given user (agent/retailer/distributor) so they can begin transacting on it. Activating a service is mandatory before your users can use it in production. The user is identified by their `user_code` and the service by its `service_code`, both supplied as path parameters. Look up service codes via the Get All Services API. After activation, confirm the status with the Get User's Services API.

> View product & pricing details: [User & Agent Management](https://eps.eko.in/products/user-management-api.md)

## Path parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| user_code | string | yes | Unique code of your user/agent/retailer the service is run for. Use `Onboard Agent` API to register your users e.g. 20810200 |
| service_code | string | yes | Unique code of the service to activate for the user. See the service codes reference. e.g. 53 |

## Body 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 |

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

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Service activated successfully.",
  "response_type_id": 0,
  "data": {}
}
```

## Error scenarios

| Status | response_type_id | Scenario |
| --- | --- | --- |
| 200 | `1295` | Service already activated |