Common issues
Fix the problems people hit most often with Piloterr.
Most support tickets come down to a handful of causes. Work through this page first — it usually resolves the issue faster than waiting for a reply.
Key or header
Re-copy the secret
Empty balance
Top up
Bad parameter
Check the endpoint page
| Symptom | Most likely cause | Fix |
|---|---|---|
Every call returns 401 | Wrong header name, or a space copied with the secret | The header is x-api-key. Re-copy the secret, or create a new key. |
401 Rate limit exceeded | A per-key quota, or your plan's rate limit | Spread the traffic out, raise the key's limits, or upgrade the plan. |
Calls suddenly return 402 | Balance exhausted, or an unpaid invoice | Buy a top-up, enable auto top-up, or settle the invoice. |
| Timeouts at exactly 10s or 30s | Your platform aborts before we reply | Raise your function or client timeout to 60 seconds. |
400 on a request that used to work | A required parameter is missing or mistyped | Compare against the endpoint page in the API reference. |
| Credits drop faster than expected | Retries, or a loop calling the same endpoint | Check the request logs for repeated identical calls. |
| Balance or keys missing in the dashboard | Wrong workspace selected | Use the switcher at the top of the sidebar. |
| Playground burns credits unexpectedly | Playground calls are real API calls | Use the free usage endpoint to test auth, or the Simulator to estimate cost without traffic. |
402 with credits still showing | An unpaid invoice is blocking the account | Open Settings → Invoices, settle the invoice, then retry. |
A 60-second checklist
Read the status code
401 → key or rate limit. 402 → balance or invoice. 400 → parameters. 5xx → retry with backoff.
Find the row in API Logs
Match the timestamp. Open the detail panel for the exact parameters and error message.
Check the sidebar balance
If it is near zero, top up or enable auto top-up before retrying a production load.
Still stuck
Open a support ticket from Settings → Support → New Ticket. Include the endpoint, the timestamp, and the status code you saw — with those three, we can find the request in seconds. API Status on the same menu tells you whether the problem is on our side.