Eko Platform Services Logo

PUTVerify OTP

Verify the OTP entered by the customer and receive a signed verification token for downstream use.

PUT/tools/kyc/mobile/otp/verify

Validates the OTP sent by the Send OTP API. On success (status = 0) it returns a signed JWT otp_verification_token containing the verified mobile and a unique token id. The token is valid for 5 minutes and acts as proof that OTP verification was performed — pass it to any transaction that depends on a verified mobile, and use the Validate OTP-Verification-Token API to confirm its authenticity.

Request

Body parameters

initiator_idstringRequired

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

example: 9962981729

client_ref_idstringoptional

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.

example: 2026010100123456789

otpstringRequired· OTP

The OTP value the customer received via SMS from the Send OTP API. For UAT, the Send OTP API returns the OTP in the response for testing purposes; in production, the OTP is only sent via SMS.

example:

mobilestringRequired· Mobile Number

The same 10-digit mobile number the OTP was sent to.

example: 9002336768

otp_ref_idstringRequired· OTP Reference ID

Reference id returned by the Send OTP API, used to track the OTP flow.

example:

Responses

  • statusnumber

    Primary success indicator (0 = success).

  • messagestring

    Human-readable response / error message.

  • response_status_idnumber

    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_idnumber

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

  • dataobject

    API-specific response payload.

    • client_ref_idstring

      Unique reference id for this OTP flow, echoed back.

    • otp_verification_tokenstring

      Signed JWT proving the OTP was verified. Contains the verified mobile and a unique token id; valid for 5 minutes. Validate it with the Validate OTP-Verification-Token API.

    • initiator_idstring

      Registered mobile number of the API user that initiated the call.

    • mobilestring

      The mobile number that was verified.

    • tidstring

      Unique transaction id for this verification.

Next steps

NextGETValidate OTP-Verification-TokenValidate an otp_verification_token as proof that OTP verification happened within the 5-minute time limit.

Related