Building with it
Errors and idempotency
Robust integrations handle errors and retries. Every non-2xx response uses one consistent error envelope with a code, a message and a documentation link, so you can handle failures programmatically. Common ones: 401 auth, 402 insufficient credits, 429 rate limit (back off with Retry-After).
And for safety, the API supports idempotency so a retried request doesn't double-charge or double-act. Build with retries confidently.
Predictable errors and safe retries - production-grade.
Key takeaway: One consistent error envelope + idempotency for safe retries - handle 401/402/429 programmatically, no double-charging.
Try this in your dashboard
The best way to learn AI92 is to use it - open your dashboard and follow along.
Knowledge check
1. How does AI92 notify you of events without polling?
2. What makes retries safe?