Start building on EPS

Integrate Eko's KYC, verification, payment and banking platform your way — drop in a signed SDK, call the REST API directly, or let an AI agent build the integration for you. Follow the steps below to go from zero to your first verified call.

Step 1

Get your credentials

Eko's UAT/sandbox is self-serve — sign up with your mobile number, verify with your PAN and address details (business or personal).

Credentials issued after organizational KYC.

Step 2

Choose how you'll build

Pick a path — we'll remember it across the docs.

Step 3

Pick your language

Your first request and SDK snippets will use this language.

Step 4

Install the SDK & make your first call

Install, construct the client, and call any endpoint by slug. We'll remember your language across the docs.

npm i @ekoindia/eps-sdk

View on npm

PAN Lite · POST /tools/kyc/pan-lite

import { EpsClient } from "@ekoindia/eps-sdk";

const client = new EpsClient({
  developerKey: process.env.EPS_DEVELOPER_KEY,
  accessKey: process.env.EPS_ACCESS_KEY,
  initiatorId: "9962981729",
  environment: "sandbox",
});

const result = await client.call("pan-lite", {
  "pan_number": "ABCDE1234F",
  "name": "Rajesh Kumar",
  "dob": "1994-08-29"
});
console.log(result);

Browse every endpoint in the left sidebar, or open the PAN Lite reference for parameters, responses and a live console.

Step 5

Handle the response

EPS APIs share a common response envelope.

status — 0 means success.
response_status_id — transaction status id (see status & error codes).
message — a human-readable description.
data — the API-specific payload.

See status & error codes for the full list.

Skip the integration work — build with AI agents

Point Claude, Cursor or Copilot at our MCP server and context packs. Correct signing on the first try, no SDK wiring.

Explore AI agents

Environments & auth

UAT / Sandbox

https://staging.eko.in/ekoapi/v3

Self-serve credentials available immediately on signup.

Production

https://api.eko.in/ekoicici/v3

Credentials issued after organizational KYC.

The full endpoint URL is always baseUrl + path — e.g. /tools/kyc/pan-lite on the sandbox base URL above.

Required request headers

developer_key — Static API key issued to your account after KYC.
secret-key — Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
secret-key-timestamp — Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
content-type — application/json

Requests accept both application/json and application/x-www-form-urlencoded bodies. Use multipart/form-data for file uploads.

The secret-key is an HMAC signature computed per request. See how auth works.

Specs & downloads

Postman CollectionEvery endpoint, pre-signed and ready to send.OpenAPI SpecificationOpenAPI 3.1 JSON for codegen and tooling.Markdown for AI agentsThe whole reference in one file to feed an LLM.