API Versioning and Backward Compatibility
API Versioning and Backward Compatibility
MediumHLD0% accepted
Design an API versioning strategy for Razorpay. Compare URL versioning (/v1/), header versioning, and query param versioning. Cover backward compatibility, deprecation, and sunset policies.
Approach
Design API versioning strategy with backward compatibility and deprecation policy.
Input
Razorpay needs to change payment response schema
Output
New schema in /v2/payments; v1 still served; migration guide sent to clients; v1 sunset date announced 12 months later
More HLD problems
Browse all coding problems →Scenarios & Expected Answers
Sign in to continue
Create a free account to view answers and mark progress.
- Free forever — no credit card
- Theory Q&A with detailed answers
- Points, streaks & leaderboards