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

Get customer profile

GET

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

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

Get customer profile

When to call: after OTP (pre-populate), after email confirm, after PAN/Aadhaar KYC, and on the update_profile journey step.

Why: one payload for the whole form. Unknown fields are null (not omitted), so the app can bind without guessing.

What it does: phone from OTP, email / emailVerified from confirm, pan masked only after PAN KYC, fullName / dob / address from KYC or POST profile, employmentType / employerName / monthlyIncomePaise from POST profile. dob is dd-mm-yyyy. Address is always a string.

What happens next: if the journey current step is update_profile, POST /application/profile then poll GET /application/journey.

Auth: Authorization: Bearer {{accessToken}}

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/profile' \
--header 'Authorization: Bearer <token>'

Response Example

{
  "customerId": "cust_1735123456789",
  "phone": "7989152378",
  "email": "borrower@example.com",
  "emailVerified": true,
  "pan": "XXXXXX085R",
  "fullName": "Rajavarapu Yaswanth Kumar",
  "dob": "15-08-1990",
  "address": "12 MG Road, Bengaluru, Karnataka, 560001",
  "employmentType": "salaried",
  "employerName": "GTET",
  "monthlyIncomePaise": 1500000
}

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

Profile

Update customer profile