Money is integer paise — ₹15,000 = 1500000. Follow GET /application/journey. Skipping a step returns 409 step_not_ready.

Request OTP

POST

https://api-dev.myemipay.com/auth/otp/request

Last modified:2026-09-09 21:03:54

Request OTP

When to call: after the customer picked a product and entered a phone. Must run before verify.

Why: the server hashes the phone, stores a one-time code in Redis, and (unless mock) sends it over WhatsApp/SMS. Verify without this returns otp_not_requested.

What it does: body { phone, product_id }. Response is only { ok: true } — the code is never in JSON. Mock: use collection otpCode (server MOCK_OTP_CODE, default 123456). Too many requests → 429 rate_limited.

What happens next: POST /auth/otp/verify with the same phone, the same product_id, and the code.

Auth: public (no Bearer).

Errors: 422 phone_required | product_id_required | invalid_phone | invalid_product · 429 rate_limited

Request

Header Params

Body Params application/json

Examples

Responses

🟢200

application/json

Bodyapplication/json

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://api-dev.myemipay.com/auth/otp/request' \
--header 'Content-Type: application/json' \
--data '{
  "phone": "{{phone}}",
  "product_id": ""
}'

Response Example

{
  "ok": true
}

Modified at 2026-09-09 21:03:54

Auth

Verify OTP