See the system
Make the important pieces and their relationships visible.
How software talks to software. You build real requests by hand: read with GET, create with POST, change and remove with PUT and DELETE, authenticate the call, read the status code that comes back, and fix a broken request on your own. By the end you can assemble a working API request and explain why a broken one broke.
For people building products with AI who want a practical mental model they can use.
For people building products with AI who want a practical mental model they can use.
Make the important pieces and their relationships visible.
Use the model inside a realistic product or technical trade-off.
Leave with language you can use with product, design, and engineering teammates.
Each lesson makes one part of the system visible, then asks you to make a decision inside it.
Where an API sits between the client, server, and database, and the four actions every request maps to.
The parts of a GET request, and the status code and JSON body that come back.
How POST creates a resource, and why its data rides in the request body instead of the URL.
Updating and removing an existing resource, each aimed at one item by its id.
How an API key and OAuth prove who is calling before the server acts.
The status-code families, then a failing request you diagnose and repair on your own.
How a backend combines several API calls into one product feature.
Try the first interactive lesson without an account or a credit card.