Common symptoms
1. HTTP 401 — Unauthorized on every request
Likely cause: your API key is missing, malformed, or revoked.
Confirm: open
/app, sign in, check
API keys. If your key shows
revoked, you'll need to create a new one.
Workaround: rotate to a new key. The dashboard shows the full secret once on creation; save it.
2. HTTP 429 — Rate limit exceeded
Likely cause: your account hit the per-minute rate limit (60 a minute on Free, 120 on Starter, per /v1/plans).
Confirm: the response includes X-RateLimit-Limit and X-RateLimit-Remaining headers + a Retry-After seconds header.
Workaround: back off until Retry-After; reduce concurrency in your client. Long-term: upgrade tier (returns higher rate-limit and quota).
3. HTTP 429 — quota_exceeded
Likely cause: your account used up its request quota.
Confirm: the response body includes {"error": "quota_exceeded", "used": ..., "quota": ..., "reset_at": "..."} and a recommended_plan.
Workaround: upgrade in the dashboard (the response body's upgrade_url deep-links). Paid plans reset at the start of the next calendar month (UTC). The free trial (5,000 data calls, once) does not reset.
4. HTTP 5xx on data endpoints
Likely cause: something on our side. A sustained pattern of errors is an incident.
Confirm: check the
status page. If it does not show the problem, email support.
Workaround: retry with backoff; if errors continue, email support with a sample request.
5. Webhook events not arriving (Paddle / Razorpay)
Likely cause: in-flight payment but our reconciler hasn't drained yet (max ~5min lag), OR a webhook signature mismatch.
Confirm: in your Paddle / Razorpay dashboard, check the webhook delivery log for non-2xx responses or "delivery failed" events.
Workaround: if the dashboard shows successful delivery but your account's plan hasn't flipped after 10 minutes, escalate (see below) — that's an incident on our side.