My EMI Pay
  1. Applications
  • My-EMI Lending API
  • System
    • Health check
      GET
  • Products
    • List published loan products
      GET
  • Auth
    • Request OTP
      POST
    • Resend OTP
      POST
    • Refresh tokens
      POST
    • Verify OTP
      POST
    • Select a family account after OTP
      POST
    • Add a family member on this phone
      POST
    • Logout
      POST
    • List family profiles on this phone
      GET
    • Send email verification link
      POST
    • Email verification status
      GET
    • Confirm email verification (Bearer)
      GET
    • Confirm email verification token (Bearer)
      POST
    • iOS Universal Links association
      GET
    • Android App Links association
      GET
  • Profile
    • Get customer profile
      GET
    • Update customer profile
      POST
  • Application journey
    • HTML origination document pack
    • Start bank statement consent
    • Poll bank statement consent
    • Application journey
    • Start PAN KYC via DigiLocker
    • PAN KYC status
    • Start Aadhaar KYC via DigiLocker
    • Aadhaar KYC status
    • Edit Aadhaar communication address
    • Verify bank account (KYC)
    • Start eSign
    • eSign status
    • Complete PAN KYC (poll DigiLocker)
    • Complete Aadhaar KYC (poll DigiLocker)
    • Start mock e-NACH
    • Pull bureau report
    • Mock e-NACH status
    • Bureau report
    • Loan eligibility
  • Webhooks
    • Resolve or fail bureau claim
    • Resolve or fail KYC claim
    • Resolve or fail eSign claim
    • Resolve or fail income claim
  • Ops
    • Confirm queued payouts
    • Wake steps that are waiting on a clock
    • Retry one failed payout row
  • Other
    • List published originators
    • HTML origination pack for one originator
  • Application
    • Get current application screen
    • Begin verification
    • Verify PAN
    • Acknowledge credit score
    • Accept offer
    • Create loan
    • Request payout
  • Applications
    • Get current application screen
      GET
    • Begin verification
      POST
    • Verify PAN
      POST
    • Acknowledge credit score
      POST
    • Accept offer
      POST
    • Create loan
      POST
    • Request payout
      POST
  1. Applications

Get current application screen

GET
https://api-dev.myemipay.com/applications
Last modified:2026-09-27 17:56:10
Get current application screen
Description: this is the customer screen (message, status, actions). 404 means no open application for this JWT product. Writes with a stale revision → 409.
Usage: after login, before any application write, and after each transition to refresh revision / youCanNow.
Details: JWT-resolved open application. No id in the path. After sanction, keyFacts carries loanAmountPaise, totalToRepayPaise, interestRateBps, interestRatePercentage, tenorMonths, estimatedEmiPaise, coolingOffUntil (Asia/Kolkata +05:30) for the app UI. Accept stays in youCanNow only once the statement is issued. After e-sign, paperwork has sanctionLetter and executedAgreement (integers, no HTML) so the borrower can open them later. documentPack is the same origination binder as journey (ordered sections, live fee-schedule paise, optional https lenderLogoUrl from the eligible product). After payout is asked for, payout is in_flight / arrived / failed with integer paise and Asia/Kolkata timestamps — never vendor refs. After arrival, servicing is pending / handed_over / failed. request_payout drops off youCanNow while money is in flight or already arrived; a failed payout shows canRetry: true.
Next: follow youCanNow[0].submitTo (begin-verification, verify-pan, acknowledge, accept-offer, start-enach, create-loan, request-payout) or GET /application/journey for the KYC pipeline.
Auth: Authorization: Bearer {{accessToken}}
Errors: 401 unauthorized | session_expired · 403 Forbidden · 404 Application not found

Request

Header Params

Responses

🟢200Application screen
application/json
Bodyapplication/json

🟠401Unauthorized
🟠404No open application
Request Request Example
Shell
JavaScript
Java
Swift
curl --location 'https://api-dev.myemipay.com/applications' \
--header 'Authorization: Bearer '
Response Response Example
200 - Application screen
{
  "application": {
    "id": "app_1735123456789",
    "reference": "PME-A1B2C3D4"
  },
  "status": "started",
  "message": "Your application has been started.",
  "youCanNow": [
    {
      "action": "begin_verification",
      "title": "Begin verification",
      "submitTo": "/applications/begin-verification"
    }
  ],
  "revision": "1"
}
Modified at 2026-09-27 17:56:10
Previous
Applications
Next
Begin verification
Built with