05: The Rosetta Stone (Reading Documentation)
Decoding the Manual
Don't read API documentation like a novel. Scan it for the "Big Three" components to understand how to talk to a new system.
Module 1: The Big Three
Before you send a single request, locate these three pieces of information:
1. Base URL
The root address for all calls (e.g., https://api.example.com/v1).
2. Authentication
Does it need a key? Where does it go? (Header vs. URL).
3. Endpoints
The specific "rooms" or actions available (e.g., /users or /reports).
Module 2: Decoding Shorthand
Technical documentation uses specific "codes" to tell you how to format your request. Let's translate them:
{id}: This is a placeholder. Replace it with your actual data (e.g.,/character/1).[Optional]: You don't need this to make the call work, but it might add more detail.Query Schema: A list of filters (parameters) you are allowed to use.
Module 3: Hands-On – The Scavenger Hunt
Your goal is to practice "vibe coding"—using your intuition and the documentation rules to find a specific result.
Final Mission
Use the Rick and Morty API to find characters who are currently "Alive".
Hint: You'll need a Query Parameter like ?status=alive.