History

API Changelog

All notable changes to the LOAN4BANK API. Breaking changes are called out in red — anything else is safely additive.

v1.3.0
Feature
2026-02-01
  • New endpoint · `POST /sandbox/quick-key` — anonymous, no-signup sandbox keys.
  • Public sandbox meter at `/sandbox/status?key=…`.
  • Sandbox key modal in-app runner across all 8 endpoints with plan-gate hints.
v1.2.0
Feature
2026-01-14
  • Referrals + leaderboard: ₹500 credit for every new dev you refer.
  • Streak freeze support for the daily-call streak system.
v1.1.0
Feature
2025-12-05
  • Webhooks graduated to GA. Per-webhook secret rotation, delivery logs, test events.
v1.0.1
Fix
2025-11-22
  • Fix: `kyc-verification` name-match false-negatives on hyphenated surnames.
v1.0.0
Release
2025-10-01
  • General Availability — 8 v1 marketplace APIs live.
  • Free / Starter / Growth / Enterprise plans + Razorpay checkout.
Subscribe to updates

New endpoint drops, deprecation notices, and status incidents are announced on the marketplace newsletter — sign up on the marketplace footer.

Understanding the LOAN4BANK API changelog

The LOAN4BANK API changelog is the single source of truth for every additive, deprecating and breaking change we ship to the v1 loan, KYC, credit-decisioning, EMI, gold-loan, wallet and corporate-rewards APIs. Every entry links back to the affected endpoint in the API reference, so teams can move directly from a release note to the exact request/response contract that changed. Version numbers use semantic versioning: a MAJOR bump means a breaking change is coming, a MINOR bump means new fields, endpoints or webhook events have been added without disturbing existing consumers, and a PATCH bump is reserved for bug fixes and clarifications.

We publish breaking-change notices at least 90 days before removal, mirror them into your account dashboard, and email every developer who has hit the affected endpoint in the last 30 days. Non-breaking additions — new optional fields, extra webhook events, new sandbox fixtures — are enabled the moment the changelog entry lands, so you can adopt them in the same day. If you rely on a specific behaviour, pin the API version with the `Loan4Bank-Version` header; the platform will keep serving that contract for the full deprecation window regardless of the current default.

Every changelog entry is machine-readable via `GET /api/marketplace/v1/changelog` — the same feed powers this page, the RSS button in the sidebar, and the Slack changelog bot that partners can install in their engineering channels. Use the feed to trigger internal release notes, to check compatibility inside your CI pipeline before a deploy, or to power a status widget inside your own admin console.

Frequently asked questions

How often does the LOAN4BANK API changelog get updated?
The changelog is updated on every production deploy. That is typically 2–4 times per week for MINOR releases (new fields, new sandbox fixtures, new webhook events) and roughly once a quarter for MAJOR releases. Deprecation notices are announced at least 90 days before an endpoint is removed.
How do I subscribe to LOAN4BANK API release notes?
Add the RSS feed at https://loan4bank.com/developer/changelog.xml to your reader, install the Slack changelog bot from the marketplace, or opt in to email notifications from your developer account. Each channel receives the same payload, so pick whichever suits your team's workflow.
What is the deprecation policy for breaking changes?
Every breaking change is announced at least 90 days in advance, tagged 'Breaking' in the changelog, and documented in the affected endpoint's reference page. During the window the old and new contracts co-exist, and you can lock to the previous version by sending the Loan4Bank-Version header until you migrate.
Can I request an API change or new endpoint?
Yes — file a request from your developer account or open a discussion on GitHub. Requests are triaged monthly; anything that ships lands here first with a Feature tag so you can track adoption without having to search commit history.

Looking for the exact request or response schema behind a changelog entry? Jump into the API Reference and use ⌘K to search for the endpoint name.