Build your own Tracking Page via API Build your own page by REST API
This article is geared towards app developers who want to build a custom Tracking Page utilizing the Tracking Page API.
Preconditions
1. Your plan should include the API Access feature. You can verify that by looking at the Settings tab features.
Activated API Access feature.
Locked API Access feature.
Note that API Access is available only in Advanced plans or in almost all yearly plans.
2. You need to have your Store API Key.
Be aware that once you implement the API tracking page, we will not be able to attribute the orders coming from your custom implementation of the page, making the Analytics report unusable.
3. Your API endpoints result is based on your tracking page configurations.
API endpoint will act in accordance with your tracking page configurations. Examples:
If carriers are hidden, it will not return carrier information:
If only customers' emails are allowed, tracking via order number, phone number, etc, will not work.
So you can see that actually, all your configurations are applicable to the API, as well as to your default tracking page. This is done to ease migration between both.
REST API implementation
Moving forward if you still want to build your own tracking page, seamlessly integrated into your website UI, you can use the Tracking Page REST API. You can read full API documentation here: https://app.swaggerhub.com/apis/rush-app/open-api/1.0 as well as test it on the fly
The basic implementation flow is:
-
Once the customer submitted a search string → email, order number, tracking number, etc, You need to call the GET /search/{query} endpoint.
-
Based on results (can be multiple if the customer has multiple orders to the same email address), you can list them, for him to pick in between.
-
To get detailed statuses of specific order/shipment, you need to call GET /track/{permlink} where the permalink is returned by the GET /search/{query} endpoint.
Examples of REST API pages
Did this answer your question?