HTTP Status Code
| Code | Description |
|---|---|
| 200 | The request was successful. Results are included in the response data. |
| 401 | Unauthorized request—possible reasons include an incorrect security key, IP not whitelisted, or an account issue. |
| 404 | Incorrect request URL. |
| 429 | Request frequency exceeds the allowed limit. |
| 500 | Server error. |
| 503 | Service temporarily unavailable. |
Error Codes
An error code provides a more detailed explanation of issues beyond the general response status code:
| Code | Description |
|---|---|
| 0 | Success |
| -18010001 | IP is not in the whitelist. Set it in the dashboard. |
| -18010002 | Invalid security key. |
| -18010003 | Internal service error. Please try again later. |
| -18010004 | Account is disabled. |
| -18010005 | Unauthorized access. |
| -18010010 | Please provide the data {0}. |
| -18010011 | The value of data {0} is invalid. |
| -18010012 | The format of data {0} is invalid. |
| -18010013 | Invalid submitted data. |
| -18010014 | Tracking numbers exceed the 40 limit. |
| -18010015 | The value {0} of the field {1} is invalid. |
| -18010016 | Last-mile carrier can only be set for postal services. |
| -18010018 | The '{1}' field is required for this tracking. Provide Alpha-2 country code and postal code. Example: '{0}'. |
| -18010019 | The '{1}' field is required for this tracking. Provide postal code. Example: '{0}'. |
| -18010020 | The '{1}' field is required for this tracking. Provide phone number. Example: '{0}'. |
| -18010201 | Webhook URL is required. |
| -18010202 | Incorrect URL format of 'Webhook'. |
| -18010203 | Webhook test failed, HTTP status code: {0}. |
| -18010204 | Webhook URL not set, cannot push data. |
| -18010205 | Incorrect IP format. |
| -18010206 | Push failed. |
| -18019901 | Tracking number {0} is already registered. |
| -18019902 | Tracking number {0} is not registered yet. Register first. |
| -18019903 | Carrier cannot be detected. Visit carrier info for carrier code and send as a parameter. |
| -18019904 | Only stopped numbers can be re-tracked. |
| -18019905 | Each tracking number can only be re-tracked once. |
| -18019906 | Only numbers being tracked can be stopped. |
| -18019907 | Tracking amount exceeds daily limit. |
| -18019908 | Quotas have run out. |
| -18019909 | No tracking info at the moment. |
| -18019910 | Carrier Code {0} is incorrect. |
| -18019911 | The tracking number of this carrier cannot be registered at the moment. |
| -18019801 | The tracking number is registered with multiple carriers. Specify which tracking number to change the carrier code for by setting the carrier_old parameter. |
| -18019802 | The parameter carrier_new {0} is incorrect. |
| -18019803 | The Carrier Code to be changed cannot be the same as the current one. |
| -18019804 | The Carrier Code to be changed must be specified to carrier_new or final_carrier_new. |
| -18019805 | The tracking number {1} for the specified carrier {0} is not registered, or the existing carrier parameter carrier_old is incorrect. |
| -18019806 | Carrier cannot be changed for stopped numbers. Retrack the number before changing the carrier. |
| -18019807 | The number of times for changing the carrier exceeds the limit. |
| -18019808 | The tracking result has not been returned after the latest registration or modification. Wait for the tracking result before changing it. |
| -18019809 | The registration information of the carrier with tracking number {0} already exists and cannot be changed to duplicate registration information. |
| -18019810 | Data meeting the update condition are not unique. |
| -18019811 | The data that needs to be changed is not valid. |
For more detailed responses, please refer to the API documentation: API Documentation | Response
*If the issue persists after troubleshooting, please provide the specific error information and contact 17TRACK technical support for assistance.