---
title: "Get Customer Information API Reference"
description: "Check whether a customer is already enrolled on the platform by mobile number."
canonical: "https://eps.eko.in/docs/get-customer-info"
---


> **Canonical URL:** https://eps.eko.in/docs/get-customer-info
> 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 Customer Information API Reference

`GET https://staging.eko.in/ekoapi/v3/customer/profile/{customer_id}`

Check whether a customer is already enrolled on the platform by mobile number.

Looks up a customer. For an enrolled customer the response returns an `otp_ref_id` to validate; if not enrolled (response_type_id 308) proceed to Onboard Customer.

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

## Path parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| customer_id | string | yes | Customer's 10-digit mobile number. e.g. 9444444444 |

## 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.intent_id | number | Intent flag for the next step (19 = onboarding). |
| data.otp_ref_id ⭐ | string | OTP session reference — pass to Verify Customer OTP. |

## Example response

```json
{
  "response_status_id": 1,
  "data": {
    "intent_id": 19,
    "kyc_request_id": "",
    "otp_ref_id": "IXrygqm0vTNbN35Lp5AfcbP69ifPhQ1Ee3u74AHY5fA9aMp2d94Yii3g+9fOBmbMsVTuaEQpDOEateP4tSTkQw=="
  },
  "response_type_id": 2129,
  "message": "Validate the OTP",
  "status": 2129
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Customer not enrolled — proceed to Onboard Customer |