Response Codes
Response Codes
Here's how the status_code and status_description fields correspond to each other and how they correspond to the tracking_status field of a label:
| Code | Message | Description |
|---|---|---|
| 200 | OK | Request response success |
| 101 | Request method GET/POST not supported | Wrong GET/POST method |
| 102 | Header error | e.g.: [API-Key] header missing |
| 103 | Invalid JSON data | Request is not application/json |
| 104 | Invalid signature | Fail to verify the signature |
| 105 | Parameter error | e.g.: [carrier_id] must not be blank |
| 106 | The request is understood, but it has been refused, or access is not allowed. | The request has inappropriate content. It is now blocked by security protection. |
| 401 | Unauthorized | This account has run out of quota. Please replenish the account to use this service. |
| 404 | Invalid API key. | KeyDelivery fails to verify your account information. |
| 405 | The carrier_id is invalid | The carrier ID is incorrect. |
| 406 | Cannot detect the carrier | KeyDelivery fails to match the tracking number with a carrier. |
| 500 | Internal Server Error | Something is wrong with the KeyDelivery server. Please contact us:support@kd100.com |
| 60101 | No result found | No result is found. Please check again later. |
| 60201 | Tracking already exists. | Recurring command, you don’t have to do the tracking again. |