---
title: "Get User's Services API Reference"
description: "Check the activation status of every service for one of your agents."
canonical: "https://eps.eko.in/docs/get-user-services"
---


> **Canonical URL:** https://eps.eko.in/docs/get-user-services
> 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 User's Services API Reference

`GET https://staging.eko.in/ekoapi/v3/user/account/services`

Check the activation status of every service for one of your agents.

Returns the list of services for the given `user_code` with each service's status (ACTIVATED / PENDING), verification status, and timestamps.

> View product & pricing details: [User & Agent Management](https://eps.eko.in/products/user-management-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 |

## 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_status_list ⭐ | array | Per-service status for the user. |
| data.service_status_list.service_code ⭐ | string | Service code. |
| data.service_status_list.status_desc ⭐ | string | Human-readable status (ACTIVATED / PENDING). |
| data.service_status_list.status | number | Numeric status (1 = active, 2 = pending). |
| data.service_status_list.verification_status | number | Verification state of the service. |
| data.service_status_list.createdAt | string | When the service was created. |

## Example response

```json
{
  "response_status_id": -1,
  "data": {
    "user_code": "20110341",
    "initiator_id": "9962981729",
    "service_status_list": [
      {
        "comments": null,
        "status_desc": "ACTIVATED",
        "city": null,
        "user_name": null,
        "mobile": null,
        "service_provider": null,
        "verification_status": 3,
        "createdAt": "2019-11-11 13:21:25.0",
        "user_code": null,
        "service_code": "43",
        "state": null,
        "status": 1,
        "updatedAt": "2019-11-11 13:21:25.0"
      },
      {
        "comments": null,
        "status_desc": "PENDING",
        "city": null,
        "user_name": null,
        "mobile": null,
        "service_provider": null,
        "verification_status": 0,
        "createdAt": "2019-11-11 13:22:44.0",
        "user_code": null,
        "service_code": "1",
        "state": null,
        "status": 2,
        "updatedAt": ""
      }
    ]
  },
  "response_type_id": 1299,
  "message": "Status of services for this user",
  "status": 0
}
```