Build with the API
Errors and limits
Every error code, what it means and what to do, plus the request limits.
Error codes
A refused request has "status": false, a message you can show your customer, and error.code to branch on.
| error.code | HTTP | What to do |
|---|---|---|
| unauthorized | 401 | Check the key on your API page. |
| ip_not_allowed | 403 | Add the address on your API page. |
| invalid_request | 422 | Fix the field and send the SAME reference again. |
| insufficient_balance | 402 | Fund your wallet and send the SAME reference again. |
| duplicate_reference | 409 | Use a new reference. |
| try_again_later | 409 | Wait a moment and send the SAME reference again. |
| request_refused | 400 | Show the message to your customer. |
| not_found | 404 | For a lookup: it is safe to send the order again. |
| rate_limited | 429 | Wait the seconds in Retry-After. |
| server_error | 500 | Send the SAME reference again. |
A refused request
{
"status": false,
"message": "Your balance is too low for this purchase. Please fund your wallet and try again.",
"error": {
"code": "insufficient_balance",
"field": null
},
"request_id": "req_8b1e2d3c4f5a6b70"
}
Limits
| What | Limit |
|---|---|
| Orders | 60 a minute per API key. |
| Other requests (balance, lists, order checks) | 120 a minute per API key. |
| Meter, smartcard and internet account checks | 30 a minute per account. |
| Wrong API keys | 30 in 10 minutes from one address, then that address waits 10 minutes. |
Over a limit you get 429 with a Retry-After header in seconds. Test keys have their own limits.
Using the Classic / MSORG address instead?
A refused request there is HTTP 400 with
{"error": ["the reason"]}. You can show the reason to your customer.
Updated 2026-11-20. Questions? Contact support.

