In order to use this API you will need to generate a TrackingMore API key in the API Keys.
The base URL
In order to verify and authenticate your application (e.g. your site), all of the requests that you make to the API must
include your unique TrackingMore API Key header (
Trackingmore-Api-Key), which you can generate and/or find in the
List of Tracking Statuses
|New shipments added that are pending to track|
|Item is not found at this moment.|
|Item has shipped from originating and is en route to its destination|
|Item is out for delivery or arrived at local facility, you may schedule for delivery or pickup|
|The shipment was delivered sucessfully.|
|Carrier attempted to deliver but failed, and usually leaves a notice and will try to delivery again.|
|Item might undergo unusual shipping condition, this may due to several reasons, most likely item was returned to sender, customs issue, lost, damaged etc.|
|Item was in transportation period for a long time still has no delivered results.|
Typical Server Responses
We will respond with one of the following status codes.
OK - The request was successful (some API calls may return 201 instead).
Created - The request was successful and a resource was created.
Created - The request was successful but exceeding the limit.
Unauthorized - Authentication failed or user does not have permissions for the requested operation.
Unauthorized - Invalid API key.
Unauthorized - API key has been deleted.
Bad Request - The request could not be understood or was missing required parameters.
Bad Request - Tracking_number is required.
Bad Request - The value of `tracking_number` is invalid.
Bad Request - The value of `carrier_code` is invalid.
Bad Request - Tracking already exists.
Bad Request - Tracking does not exist.
Bad Request - Due to overload risks this feature requires custom activation. Contact [email protected] for more information.
Bad Request - Limit up to 200 at a time
Bad Request - Your remaining balance is not enough, so you can not call the API request data.
No Content - The request was successful but the response is empty.
No Content - Cannot detect courier.
Payment Required - Payment required.
Forbidden - Access denied.
Not Found - Resource was not found.
Method Not Allowed - Requested method is not supported for the specified resource.
Conflict - The request could not be completed due to a conflict.
Too Many Requests - Exceeded API limits. Pause requests, wait two minute, and try again.
Service Unavailable - The service is temporary unavailable (e.g. scheduled Platform Maintenance). Try again later.
Request Rate Limiting
We do enforce a small amount of rate limiting. Please be aware that should you exceed these limits, you will receive a 429 error.
Real-time tracking: each IP, maximum 3 requests per second.
List all trackings; each IP, maximum 1 request with up to 200 trackings per second.