What’s next
You made it.
Seven chapters. From "what's JSON?" to evaluating APIs, testing endpoints, and having real conversations with your engineering team. Let's take a second to see how far you've come.
Everything you've learned
| Chapter | What you learned | Key concept |
|---|---|---|
| 1. JSON | How to read the data format behind every API | Objects, arrays, key-value pairs |
| 2. API requests | How apps talk to servers: URLs, methods, headers, bodies | GET, POST, PUT, DELETE |
| 3. API design | How APIs are structured and why REST conventions exist | Resources, endpoints, relationships |
| 4. Authentication | Why some requests get rejected and how credentials work | API keys, OAuth, Bearer tokens |
| 5. Documentation | How to navigate real API docs and find what you need | Endpoints, parameters, response schemas |
| 6. Webhooks | How external services notify your app when something happens | Events, payloads, signatures |
| 7. APIs at work | How to evaluate, test, and talk about APIs in your job | DX, Postman, rate limits, integration patterns |
That's not a small list. Six months ago, most of this was a foreign language. Now you have a mental model for every piece.
What to do tomorrow
This course gave you the concepts. The next step is to use them. Here are a few things you can do right away:
Open Postman and send your first real request. Download it (it's free), create a GET request to https://dummyjson.com/products/1, and hit Send. You'll get back a JSON object with a product's name, price, description, and rating. Same tool your engineers use every day, same kind of response you've been reading throughout this course.
Read a real API's documentation. Pick one your team actually uses (Stripe, Twilio, Intercom, whatever). Open the docs, find an endpoint, and try to understand what it does: what method, what parameters, what response. You'll be surprised how much you can follow now.
Ask your engineers one good question. Next time an integration comes up, try one of the questions from the glossary: "What auth does it use?", "Are there rate limits?", "Do they support webhooks?" Watch how the conversation changes when you speak the same language.
Look at your product with API eyes. Does your product expose a public API? If so, try the DX checklist: sign up as a new developer, read the docs, send a test request. You'll see your product from a completely different angle.
The next time you're in a meeting and someone mentions webhooks, pagination, or OAuth, you won't just nod. You'll know what it means, why it matters, and what to ask next.
Thanks for taking this course. If it helped you, share it with a colleague who's in the same spot you were seven chapters ago.