APIs
Public and internal APIs: design, auth, webhooks, quotas, and what callers — including other software — need back.
- Jun- 2026 -15 June
How to Write API Errors a Developer Can Debug
An API error message has one job: give the person on the other end enough to fix the problem without opening a support ticket.
Read More » - May- 2026 -26 May
A Security Pass for a New Public Endpoint
The HTTP request arrives before anyone has decided whether the endpoint should exist.
Read More » - Apr- 2026 -5 April
How to Add Fields to a JSON Response Without Breaking Clients
A JSON response is a contract, and most teams only discover the terms of that contract after they have already violated it.
Read More » - Feb- 2026 -25 February
What to Log So an API Failure Is Traceable
An API failure at 2:14 on a Tuesday morning leaves behind three artifacts: a stack trace that points at a line of application code, a metric graph that dipped for forty seconds, and a support ticket t
Read More » - Feb- 2026 -12 February
What a Usage-Based API Costs an Indie Product
The invoice for a small API integration rarely looks like a bill.
Read More » - Feb- 2026 -4 February
Where an Internal API Should Stop and a Public One Starts
Somewhere in a codebase, there is a function that returns a customer's billing address, and three different teams call it. The mobile app calls it to prefill a checkout form.
Read More »