Paths/Backend Engineer/API Design / Errors & Versioning
Version Without Breaking Clients
You will ship a breaking change. Decide now how versions are named, how they are deprecated and when they are switched off.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/api/versioning.md exists○
- The document states how the version is carried in the URL○
- The document states the deprecation policy and the sunset date○
- The document states how clients are told to migrate○
02Walkthrough
1 of 4 revealed- 01
State how the version is carried
The version lives in the path - /v1/orders. It is obvious in the logs, in the dashboards and in the support tickets.
echo '# API versioning\n\n## How the version is carried\n\nThe major version is part of the path: /v1/orders.' > ~/api/versioning.md - 3 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list