Blog · Topic
Engineering
5 articles
Handle API errors like a pipeline, not a script
429s, 402s, timeouts and 5xx each mean something different. The retry policy that respects idempotency — and the one that double-charges you.
Design a webhook receiver that survives outages
Result delivery over webhooks means your endpoint's downtime is your problem to absorb. Receiver patterns that lose nothing.
Idempotency keys are your retry safety net
Retries are mandatory for async pipelines — and dangerous without idempotency. How keys prevent duplicate tasks and double charges.
Verify webhook signatures before trusting task results
Webhook endpoints are public by design — verify the signature, timestamp and event type before storing results. Working verification code in Python and Node.
Sync calls, async tasks or webhooks: how to call an answer API
When to wait for an answer, when to queue a task and poll, and when to let results come to you by webhook.