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

Application journey

GET

https://api-dev.myemipay.com/application/journey

Last modified:2026-09-09 21:56:13

Application journey

When to call: after every successful write in onboarding. This is the source of truth for “what screen now?”.

Why: current.step + upcoming + isOnboardingFinished tell the app which API to call next. After Aadhaar, current is under_verification until staff evaluate — do not jump to bank/eSign. A skip-ahead call on any later step returns 409 step_not_ready with requiredStep.

What it does: JWT-resolved application (no id in the path). isOnboardingFinished is true once Aadhaar KYC is verified.

What happens next: call current.method + current.path from the payload (PAN start, status poll, bureau GET, etc.).

Auth: Authorization: Bearer {{accessToken}}

Errors: 403 Forbidden

Request

Authorization

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Responses

🟢200

application/json

Bodyapplication/json

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://api-dev.myemipay.com/application/journey' \
--header 'Authorization: Bearer <token>'

Response Example

{}

Modified at 2026-09-09 21:56:13

Application journey

Start PAN KYC via DigiLocker