
A bike rental shop's web service. Staff list bikes, add one, and view, edit or remove a single bike. It must reply with the right "found / created / deleted / not-found" signals instead of misleading ones.
A training provider lists modules that live inside a course. A module is only valid under its own course, so asking for it through the wrong course returns "not found", and malformed ids are rejected before any lookup.
A reporting service where a fixed page (`/reports/summary`) keeps being mistaken for a generic "report by id" page. Routes must be ordered so named pages win, with a clean JSON not-found for anything unmatched.
An office room-booking service. Users filter rooms and request a reservation. It checks the times and party size make sense before accepting, and tells the user exactly which field was wrong.
Build real HTTP APIs in Node, one skill at a time. Easy → Hard: routing, validation, responses, middleware, data access — up to auth, caching, jobs, concurrency, transactions, streaming, resilience. Every challenge is API-only and test-driven: implement the missing piece until the supertest suite (in-memory SQLite, seeded) passes.
This path builds HTTP APIs in Node.js with TypeScript, starting with routing and controllers, request validation, status codes and middleware. You should be comfortable with basic TypeScript or JavaScript. No earlier backend experience is needed. The middleware module includes a request audit log and an access gate for an admin console.
4 modules: Routing & Controllers, Request Data & Validation, Responses & Status Codes and Middleware Basics.
16 exercises, all easy.
Challenges run on Node.js 24.
No. Every challenge runs in a browser-based IDE with everything already set up, and your code is graded automatically against a test suite.