Tag: api
All the articles with the tag "api".
The Reply Arrived Twice. The Record Updated Once.
Inbound replies and webhooks must link to the right record exactly once, and generated drafts must wait for a human. Two mechanisms from production systems: key on the sender id, hold behind a gate.
The OAuth Succeeded. The Reports Still Had to Reconcile.
Hardening QuickBooks OAuth server side and structuring Profit and Loss, Balance Sheet and Cash Flow in Postgres so three reports read at different times still agree.
I Wrote the Tool for a Human. An Agent Called It.
An agent has only your response bytes to reason from, which turns error messages into control flow and makes response size a correctness property.
The Browser Never Sees the Token. The Edge Function Holds It.
Read-only social API integration through Supabase Edge Functions in Deno and TypeScript, with tokens sealed server side and scoped to the minimum.
Page 1 Was Fast. Page 400 Timed Out.
Offset pagination has to produce every row it discards, and the fix has three parts that only work together: the sort key, the cursor, and the index.
Every Deploy Reported Success. The Endpoint Had Been Unreachable for Two Weeks.
A 404 is not one thing, and the difference between text/plain, text/html and application/json was the entire diagnosis.
The Webhook Must Reply in Seconds. The Useful Work Takes Longer.
Designing a Go alerting service where every operation worth doing is slower than the budget you have to respond in, and the sender retries if you are late.