Sign up for a ClickPost account and obtain your API key and username from the dashboard; all requests are authenticated by passing these as query parameters or in the request headers as documented.
Register your carrier shipments by POSTing the AWB (tracking number), carrier code, and order reference to the ClickPost shipment registration endpoint so ClickPost can begin polling the carrier.
Configure a webhook URL in the ClickPost dashboard under Settings > Webhooks; ClickPost will POST a JSON event payload to this URL on each carrier status update.
Parse the webhook body: key fields include waybill, current_status, status_code, location, and timestamp; map ClickPost unified status codes to your internal delivery state machine.
Respond to each webhook with HTTP 200 within the timeout window to prevent retries; implement idempotency using the event's unique identifier to handle duplicate deliveries.
Use the ClickPost tracking API (GET /track) to pull historical events on demand for reconciliation or customer-support queries when webhooks may have been missed.
Known gotchas
ClickPost uses a unified status taxonomy across carriers — always map ClickPost status codes to your states rather than relying on raw carrier status strings, which vary widely.
Carrier polling frequencies differ by plan and carrier; for premium last-mile carriers, confirm the polling SLA in your ClickPost contract to set accurate customer-facing ETA promises.
Webhook delivery order is not guaranteed; build your state machine to accept out-of-order events (e.g., an 'out_for_delivery' event arriving after 'delivered') without corrupting the order record.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp