Tag: APIs for non-devs
-
How to read an API error like a business person, not a developer
An API error code usually tells you whose problem it is — yours, your team’s, or the vendor’s. Here’s the triage map CS and RevOps can use before escalating everything to engineering.
-
Asking for exactly what you want
You write the shape of the answer you want and the answer comes back in that shape. Part 3 of GraphQL, from zero to governance: how to read a query.
-
The schema is the contract
A schema is the list of every field an API has and what type each one holds. Here’s how to read one, and why it’s a contract both teams have to sign rather than documentation anyone can ignore.
-
What GraphQL was actually built for
GraphQL wasn’t built to fix over-fetching. Facebook built it because the News Feed didn’t have an API at all — here’s the real origin story, from the source.
-
When two tools can’t talk, a person becomes the API
When two tools don’t share an API, someone bridges them by hand. Here’s the arithmetic for pricing that hidden integration tax on your own workflow.
-
What is an API? A plain-language guide
A plain-language guide to APIs for non-developers: what a request, endpoint, response, status code, key, and rate limit actually mean.