ETrackings uses standard HTTP response codes to indicate success or failure. 2xx = success, 4xx = error from provided data, 5xx = server-side error.
| HTTP Status Code | meta.code | Sample Error Message |
|---|---|---|
| 400 | 400 |
Parameter is invalid. |
| 401 | 401 |
Invalid API key or Key secret. |
| 403 | 403 |
The request is understood, but it has been refused or access is not allowed. |
| 404 | 404 |
The URI requested is invalid or the resource requested does not exist. |
| 429 | 429 |
You have exceeded the API call rate limit. Default limit is 10 requests per second. |
|
500
502
503
504
|
500 502 503 504
|
Something went wrong on ETrackings' end. |
In case of wrong API key or Key Secret
{
"meta": {
"code": 401,
"message": "Invalid API key or Key secret."
}
}
In case of wrong courier name
{
"meta": {
"code": 404,
"message": "The URI requested is invalid or the resource requested does not exist."
}
}
In case the server is down
{
"meta": {
"code": 500,
"message": "Something went wrong on ETrackings end."
},
"data": {}
}
We use cookies to improve performance. and good experience in using your website You can study the details at Privacy Policy and Terms and Conditions
You can choose cookie settings by on/off. Cookies of each type are available on request, except for essential cookies.