I got our API into the Postman network in one evening — and didn't hand-write a single request

The useful part

The main barrier isn't code, it's the first half hour: open the docs, figure out which endpoints you need, put together the first request, find where the key goes. You get ready-made collections you can fork into your workspace and run with your own key. We're in there now, next to Notion, Stripe, and Twilio â€" and getting listed took one evening.

How it works

• Here's how I did it, and why I decided not to build the collection by hand.
• Postman doesn't work that way: it's self-serve, publishing is free, and there's no application or moderation.
• You can build a collection for the network by hand: create the requests, type in the paths, fields, and headers.
• About a quarter of our users access the API with a key.
• The problem is that a hand-built collection is a snapshot of your API on the day you made it.

What to take from it

Add an endpoint or rename a field a month later, and now the collection is out of date.

Details worth keeping

queue â€" Chrome, Edge, and LinkedIn have all made us wait. So the whole thing really did fit into an evening.