SATIK DEVELOPER DOCS · V1 BETA
Errors with a next step.
Every API error returns a stable code and a request ID.
Input and authentication
Correct the input or credentials before sending the request again.
| Error | What to do |
|---|---|
Invalid requestinvalid_request | Check the request fields and their expected types. |
Address too shortaddress_too_short | Provide an address with at least 5 characters. |
Address too longaddress_too_long | Keep the address within 280 characters. |
Invalid DIGIPINinvalid_digipin | Check the location code and resend corrected input. |
Coordinates outside the gridout_of_bounds | Provide coordinates inside the supported DIGIPIN grid. |
Invalid API keyinvalid_api_key | Send a valid API key in the Bearer authorization header. |
Revoked keykey_revoked | Replace the revoked key with a valid key. |
Expired keykey_expired | Use a current key; the previous key may have passed its rotation grace period. |
Capacity and retries
Check capacity and request state before retrying.
| Error | What to do |
|---|---|
Rate limit reachedrate_limited | Wait for the duration given in the Retry-After header. |
Quota exhaustedquota_exceeded | Monthly capacity is exhausted. Check workspace usage and available quota. |
Idempotency key already in useidempotency_key_in_use | The same key has a different payload, or its request is still processing. Wait for the original request, or use a new key for a genuinely different request. |
Provider errors
Provider failures never produce invented verdicts. Keep the request ID when contacting support.
| Error | What to do |
|---|---|
Provider timeoutupstream_timeout | Retry the same request with the same idempotency key, or contact support with request_id. |
Provider unavailableupstream_unavailable | Retry the same request with the same idempotency key, or contact support with request_id. |
Internal service errorinternal_error | A Satik-side failure occurred. Contact support with request_id if it persists. |