Skip to main content

Tracking And Events

Aquiline exposes shipment visibility through both pull and push patterns.

Pull model​

Use GET /tracking/{trackingNumber} when you need the latest shipment state on demand.

Typical use cases:

  • Customer self-service pages
  • Support dashboards
  • Exception handling tools
  • Periodic reconciliation jobs

Push model​

Use webhook subscriptions for near real-time updates in operational systems.

Recommended event subscriptions:

  • shipment.created
  • shipment.in_transit
  • shipment.out_for_delivery
  • shipment.delivered
  • shipment.exception

Status handling​

Downstream systems should treat status values as operational events rather than purely visual labels. A shipment may move through multiple transit and exception states before final delivery.

Best practices​

  • Treat webhook delivery as the primary event stream
  • Use polling as a controlled fallback
  • Persist the full event timeline for auditability
  • Surface exceptions to support and operations teams immediately