API Error Codes
Error codes and recommended actions are listed in the tables below.
Best Practice for Retry Mechanism
When interacting with Reltio APIs, various error codes may be returned based on the request conditions or service availability. Proper handling of these errors ensures resilient and reliable application behavior. This document outlines common error codes, appropriate actions, and retry mechanisms following industry best practices.
| Error Code | Actions |
|---|---|
| 401 | Do not retry until fixing of auth problem on your side, re-ask access token and try again, ask support. |
| 403 | Request is Forbidden. No retry. |
| 404 | Do not retry. |
| 429 | Too Many Requests. |
| 500 | Do not retry, service failed to serve your request, check your request / documentation, ask Support. |
| 502 | Retry with exponential backoff, fail after 10 sequential tries, ask support. |
| 503 | Retry with exponential backoff, fail after 12 sequential tries, ask support. |
| 504 | Retry with exponential backoff, fail after 5 sequential tries, check your request / documentation, ask Support. |
Note: Time slot for exponential backoff is 1 second for the first retry and increases exponentially for others. See also Exponential backoff on Wikipedia.
Exponential Timing Reference
| Iteration | Waiting Time, seconds | Waiting Time, minutes |
|---|---|---|
| 1 | 1 | 0 |
| 2 | 3 | 0 |
| 3 | 7 | 0 |
| 4 | 15 | 0 |
| 5 | 31 | 1 |
| 6 | 63 | 1 |
| 7 | 127 | 2 |
| 8 | 255 | 4 |
| 9 | 511 | 9 |
| 10 | 1023 | 17 |
| 11 | 2047 | 34 |
| 12 | 4095 | 68 |