In our Track and Trace API, we offer the options to either
subscribe to an AWB and automatically receive a call back every time we detect a change in milestone
OR call the APIs every time you want to retrieve the latest status update on an AWB.
In a nutshell the first mechanism PUSH-es you the updates whenever they are available and the second one requires you to PULL (call or query) the API for a status update.
The 2 options fit different workflows and also largely depend on your estimation of how many status updates you'll need (on average) per MAWB, due to the different pricing structure.
If you want to subscribe to the Push or Pull API, you will have to decide whether you want to proceed with the Pro or Ultra version. Both models include an API Push or Pull subscription coverage per month and a variable price component.
Principally, for the Push API you are billed per AWB subscription that you create. We take care of the tracking and update you on new events via email or callback url. The price stays the same regardless of how many status updates are associated with the subscribed AWB.
At hand of the Push API - Pro pricing model, we will explain what the different numbers mean:
So in the example of the Pro plan, you have 2 AWB subscriptions included which means that all status updates related to 2 AWBs are included in the price.
For any additional AWB that you would like to track, you would have to pay 1 $US per new AWB subscription request. The 1 $US includes all status updates (n status updates) related to that subscribed AWB.
Please note, that you are charged for any AWB subscription that you make, even if you have been previously signing up for the same AWB.
So if you have subscribed to the Pro plan and you have 3 AWBs that you are tracking over the course of a month you would end up paying $US 50:
$US 49 (Pro price per month, including 2 AWBs)
1 additional AWB, priced at $US 1
Regarding the Pull API you would have 10 calls for status updates included to any AWB you are calling. The pricing model follows the same logic as described for the Push API.