Errors
This section defines how and when errors may be returned as a response to your API request.
Example
// Error Example
{
"header": {
"status": "Error",
"code": 181,
"type": "Invalid data",
"ref": "unique-id"
},
"errors": [
"Collection Country Code is required"
]
}
// Error Example
<response>
<header>
<status>Error</status>
<code>181</code>
<type>Invalid data</type>
<ref>unique-id</ref>
</header>
<errors>
<error>Collection Country Code is required</error>
</errors>
</response>
| Element | Description |
|---|---|
| response | Root element |
| header | Header element |
| status | Error |
| code | Error code |
| type | Error type |
| ref | In most cases, this will be the unique reference you supply to us and will help us identify a request from the logs |
| errors | Array of errors |
| error | Error message |
Error response codes
| Code | Reason |
|---|---|
| 120 | Method does not exist |
| 125 | Invalid schema |
| 135 | Unique ID already exists |
| 140 | Invalid credentials |
| 145 | Token authentication failed |
| 150 | Unauthorized use of the API |
| 166 | API is currently unavailable |
| 170 | No services available |
| 181 | Invalid data |
| 182 | Invalid parcels data |
| 183 | Invalid address data |
| 184 | Invalid collection address data |
| 185 | Invalid destination address data |
| 190 | Customs invoice data required |
| 191 | Invalid Customs importer details |
| 192 | Invalid Customs exporter details |
| 250 | No funds available |
| 270 | Collection date invalid |
| 290 | Shipments not found |
| 501 | Invalid request |