Reading API Docs & Using Postman

You've been handed an API and a link to its docs, and the page is a wall of endpoints, headers, and words like "bearer token" and "query parameter." You scroll, you copy something that looks right, you paste it somewhere, and you get back a number you don't understand. The frustrating part isn't that APIs are hard - it's that nobody showed you how a docs page is organized, so you don't know where to look for the five things you actually need.

That's all this guide fixes. By the end you'll open any well-structured API reference, find the exact request you need, fire it from a graphical tool (Postman) or the command line (curl), and read what comes back. Same skill, two tools, one calm process.

How to read this

Need to send one request right now? Skim Phase 1 to find the five things, then jump to Phase 2 for the Postman and curl steps.
Want it to finally make sense? Read in order - each phase builds on the last, from reading the docs to firing the call to understanding the answer.

The phases

How to Read API Docs - the five things every reference is telling you (base URL, endpoint + method, parameters, auth, example), and how to skim for the one you need.
Making the Request (Postman & curl) - two equivalent ways to fire the same request: Postman the GUI, and curl on the command line, with an annotated transcript.
Reading the Response & Iterating - status code first, then the body; tweaking and re-sending; saving requests into collections with variables - and the secret-leak trap to avoid.

This guide assumes you already know roughly what an HTTP request is (a method, a URL, headers, maybe a body) and what JSON looks like. If those are fuzzy, read HTTP & JSON API Basics first, then come back. Designing your own API, pagination, rate limits, and OAuth flows are deliberately left to follow-up guides - this one is about using an API someone else built.