Eko Platform Services Logo

    POSTOnboard User

    Register a new agent/retailer (merchant) on the EPS platform and receive their user_code.

    POST/user/network/eps-agent

    Onboards a merchant or retailer as a user on the platform. On success a unique user_code is returned — save it; every downstream request for that agent passes this user_code.

    Body parameters

    initiator_idstringRequired

    Registered mobile number of the API user (see Platform Credentials).

    example: 9962981729

    user_codestringRequired

    User code of the retailer/agent the service is run for.

    example: 20810200

    client_ref_idstringoptional

    Unique reference id per API call, generated by your system.

    example: REQ-20260101-001

    pan_numberstringRequired

    PAN card number of the agent.

    example: ABCDE1234F

    mobilestringRequired

    Verified mobile number of the agent.

    example: 9876543210

    first_namestringRequired

    First name of the agent.

    example: Ramesh

    last_namestringRequired

    Last name of the agent.

    example: Kumar

    emailstringRequired

    Email ID of the agent.

    example: ramesh@example.com

    residence_addressarrayRequired

    Residence address of the agent as an array of strings.

    example: 123 MG Road,Bangalore,Karnataka,560001

    dobstringRequired

    Date of birth of the agent in YYYY-MM-DD format.

    example: 1990-05-15

    shop_namestringRequired

    Shop name of the agent (required for AePS onboarding).

    example: Ramesh Mobile Store

    Headers

    developer_keystringRequired

    Static API key issued to your account after KYC.

    secret-keystringRequired

    Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).

    secret-key-timestampstringRequired

    Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.

    content-typestringRequired

    application/json

    example: application/json

    Responses

    • statusnumber

      Primary success indicator (0 = success).

    • messagestring

      Human-readable response / error message.

    • response_status_idnumber

      Granular status id; see the shared error-codes table.

    • response_type_idnumber

      A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.

    • dataobject

      API-specific response payload.

      • user_codestring

        Unique code for the onboarded agent — save it and pass on every downstream request.

      • initiator_idstring

        Your registered initiator id (echoed back).