openData Studio中文
Categories

Lending apps and their data APIs

Loan and credit apps — the endpoints that score applicants, quote offers, and track repayments inside the app.

Lending apps decide in seconds, and their endpoints show how: score pulls, limit checks and repayment schedules called straight from the home screen. Kredivo reads revolving headroom at GET /v1/limit/available — availableLimit against the sanctioned total_limit — and exposes the drawn credit line at GET /v1/wallet/credit-line. Intuit Credit Karma loads bureau scores with POST /v1/credit/scores, returning per-bureau score, rating, updatedAtTimestamp and delta factor tiles, then pages score history at POST /v1/credit/scores/history. Paisabazaar is OTP-first: POST /v1/auth/otp/request and POST /v1/auth/qr/verify gate every bureau pull, and Tabby signs borrowers in the same way at POST /v1/signin/otp/dispatch.

Frequently asked questions

Which lending apps expose a credit-limit endpoint?

Kredivo does: GET /v1/limit/available returns availableLimit and availableLimitAmount against the sanctioned total_limit, and GET /v1/wallet/credit-line describes the drawn credit line. Credit Karma and Paisabazaar instead lead with the score: POST /v1/credit/scores, and the bureau pulls behind Paisabazaar's OTP-gated authorize flow.

Can I get score history, not just the current score?

Yes. Credit Karma pages it at POST /v1/credit/scores/history with updatedAtTimestamp and delta per entry, and POST /v1/credit/reports/refresh triggers an on-demand bureau refresh.

How do these apps authenticate borrowers?

Mostly OTP-first. Paisabazaar starts at POST /v1/auth/otp/request and verifies a QR at POST /v1/auth/qr/verify; Tabby dispatches and verifies sign-in OTPs at POST /v1/signin/otp/dispatch; Kredivo opens a PIN session at POST /v1/auth/pin-session before reading borrower identity at GET /v1/borrower/identity.

Apps in Lending