This topic categorizes responses and errors into groups to help you identify and take appropriate actions in each case.
Success responses | HTTP code | Description | Action |
|---|
200 OK | Request succeeded and returned data. | Parse and use the response. | 202 Accepted | Request accepted but processing is pending. | Don’t retry; wait for callback or poll job status. |
|
Client errors | HTTP code | Description | Action |
|---|
401 Unauthorized | Missing or invalid API key. | Ensure API key is included in request to the API. Include Authorization: Bearer <API_KEY>. | 403 Forbidden | TLS error or IP not whitelisted. | Use HTTPS and confirm firewall settings. | 404 Not Found | Endpoint or resource doesn’t exist. | Verify endpoint path and IDs. | 413 Payload Too Large | Request size exceeds ~1 MB (sandbox). | Reduce payload; no limit in production. |
|
Server errors | HTTP code | Description | Action |
|---|
504 Gateway Timeout | Upstream service didn’t respond in time. | Retry; reduce request size if common. |
|
Rate limit and retry | HTTP code | Description | Action |
|---|
425 Too Early | Request sent too soon after previous action | Transaction checks Customer checks | 429 Too Many Requests | Rate limit exceeded. | Respect Retry-After header, use exponential backoff with jitter. |
|