TrackLogy API: How Developers Can Build Custom Tracking Integrations

Who This Is For

This guide is for developers who want to:

• Integrate TrackLogy into a custom storefront or headless commerce setup
• Push shipments from an ERP or OMS into TrackLogy
• Pull tracking data into a custom customer portal
• Build automated workflows triggered by tracking events

Authentication

All API requests require a Bearer token from your TrackLogy API key:

Authorization: Bearer YOUR_API_KEY

Find your API key under Settings → API Keys.

Core Endpoints

Create a Shipment

POST /v1/shipments

{
  "tracking_number": "1Z999AA10123456784",
  "carrier_code": "ups",
  "customer_email": "[email protected]",
  "customer_name": "Jane Smith",
  "order_number": "ORD-12345"
}

Get Tracking Events

GET /v1/shipments/{id}/events

Returns all tracking events for a shipment in chronological order, normalised from carrier-specific formats into TrackLogy's standard event schema.

List Shipments

GET /v1/shipments?status=in_transit&page=1&per_page=50

Filter by status, date range, store, or carrier.

Webhooks

TrackLogy can push tracking events to your server in real time. Register a webhook endpoint in Settings → Webhooks and select which events to receive:

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

Each webhook payload includes the full shipment record and the new event that triggered it.

Rate Limits

The API allows 300 requests per minute per API key. For bulk imports, use the batch endpoint (POST /v1/shipments/batch) which accepts up to 100 shipments per request.

SDKs and Sample Code

Sample integrations in PHP, Node.js, and Python are available in the TrackLogy developer docs at docs.tracklogy.com.