ClickPost receives shipment tracking updates from courier partners through two mechanisms:
Webhooks
Polling
1. Webhooks
Through webhooks, ClickPost receives real-time tracking updates directly from courier partners. As soon as an event (such as pickup, in-transit, or delivery) is updated in the courier’s system, they push this status to ClickPost.
To enable webhook integration:
ClickPost shares a webhook endpoint URL with the courier partner.
The courier partner configures this endpoint to push the tracking status updates as per the integrated payload structure.
This mechanism ensures that tracking data is updated on ClickPost immediately as the courier’s system records it.
2. Polling
In the polling mechanism, ClickPost fetches tracking updates at regular intervals (every 2 hours).
ClickPost’s system calls the courier partner’s tracking APIs for all active AWBs registered on the ClickPost dashboard.
Any new or updated tracking statuses since the last API call are fetched and stored.
This ensures periodic synchronization of tracking data, even if webhook updates are unavailable or delayed.
Data Handling Logic
ClickPost processes tracking events based on the latest timestamp, ensuring the most recent event appears on top.
Duplicate or outdated statuses are automatically ignored.
Priority Handling: Webhooks vs. Polling
When both mechanisms are enabled, ClickPost intelligently prioritizes updates as follows:
| Mechanism | Frequency | Purpose |
|---|---|---|
| Webhooks | Real-time | Primary source of live updates |
| Polling | Every 2 hours | Ensures missed webhook scans are captured |
Note:
Polling ensures continuity in case of any temporary webhook failures or network issues.
In cases where webhooks are not enabled, polling acts as the primary source for all status updates happening on ClickPost.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article