API v1 / schema 1.0.0
Errors & limits
Handle failures without changing taxes.
Errors use {"error":{"code":"…","message":"…"}}. Read the
HTTP status first. Never replace saved property tax settings after an
unsuccessful request.
| Status | Action |
|---|---|
| 400 | Correct the request inputs. |
| 401 | Check that a valid active key was provided. |
| 403 | Check the key's scopes and permitted countries. |
| 422 | Scope exceeds the reviewed bound. Inspect a narrower jurisdiction. |
| 429 | Respect the retry delay; use bounded backoff. |
| 503 | Data or the service is unavailable. Keep existing settings and retry later. |
Keys default to 300 requests per minute unless the operator provisions a different limit. The anonymous website proxy has separate, tighter limits. Do not use it as your production integration API.
Set a bounded timeout, avoid logging keys or addresses, and do not retry validation or authentication failures indefinitely.