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

Confirm email verification (Bearer)

GET

https://api-dev.myemipay.com/auth/email/verify/confirm

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

Confirm email verification (Bearer)

When to call: web / Universal Link landing. Prefer POST from the app after it parses the deep link.

Why: the token is bound to the logged-in customer. Confirming without Bearer, or with another customer's token, fails (401 / 403).

What it does: query token. Success { ok: true, email } and the email is ingested into the profile. Replay of the same token works for a short window (double-tap).

What happens next: GET /auth/email/verify/status or GET /application/profile (emailVerified: true).

Auth: Authorization: Bearer {{accessToken}}

Errors: 401 unauthorized | email_verify_invalid · 403 forbidden

Request

Authorization

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Query Params

Responses

🟢200

application/json

Bodyapplication/json

Request Example

Shell

JavaScript

Java

Swift

curl --location --globoff 'https://api-dev.myemipay.com/auth/email/verify/confirm?token={{emailVerifyToken}}' \
--header 'Authorization: Bearer <token>'

Response Example

{}

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

Email verification status

Confirm email verification token (Bearer)