Batch Tracking - CrossBorderly API

{
  "trackingNumbers": [
    "CBECUSD123456789",
    "CBECUSD123456790",
    "CBECUSD123456791",
    "INVALID123456789"
  ],
  "includeHistory": false
}

{
  "success": true,
  "results": [
    {
      "trackingNumber": "CBECUSD123456789",
      "status": "IN_TRANSIT",
      "statusName": "In Transit",
      "estimatedDelivery": "2024-12-28T18:00:00Z"
    },
    {
      "trackingNumber": "CBECUSD123456790",
      "status": "DELIVERED",
      "statusName": "Delivered",
      "deliveredAt": "2024-12-26T14:30:00Z"
    },
    {
      "trackingNumber": "CBECUSD123456791",
      "status": "OUT_FOR_DELIVERY",
      "statusName": "Out for Delivery"
    }
  ],
  "notFound": ["INVALID123456789"]
}

POST

api

tracking

batch

{
  "trackingNumbers": [
    "CBECUSD123456789",
    "CBECUSD123456790",
    "CBECUSD123456791",
    "INVALID123456789"
  ],
  "includeHistory": false
}

{
  "success": true,
  "results": [
    {
      "trackingNumber": "CBECUSD123456789",
      "status": "IN_TRANSIT",
      "statusName": "In Transit",
      "estimatedDelivery": "2024-12-28T18:00:00Z"
    },
    {
      "trackingNumber": "CBECUSD123456790",
      "status": "DELIVERED",
      "statusName": "Delivered",
      "deliveredAt": "2024-12-26T14:30:00Z"
    },
    {
      "trackingNumber": "CBECUSD123456791",
      "status": "OUT_FOR_DELIVERY",
      "statusName": "Out for Delivery"
    }
  ],
  "notFound": ["INVALID123456789"]
}

Retrieves tracking information for up to 100 parcels in a single request. More efficient than making individual requests.

Request Body

array

required

List of tracking numbers to look up (1-100 items).

boolean

default:"false"

Set to true to include tracking history for each parcel.

Response

boolean

Whether the request succeeded

array

Tracking information for found parcels

Show Result fields

string

The tracking number

string

Current status code

string

Human-readable status

array

Tracking events (if includeHistory=true)

array

Tracking numbers that were not found in the system

{
  "trackingNumbers": [
    "CBECUSD123456789",
    "CBECUSD123456790",
    "CBECUSD123456791",
    "INVALID123456789"
  ],
  "includeHistory": false
}

{
  "success": true,
  "results": [
    {
      "trackingNumber": "CBECUSD123456789",
      "status": "IN_TRANSIT",
      "statusName": "In Transit",
      "estimatedDelivery": "2024-12-28T18:00:00Z"
    },
    {
      "trackingNumber": "CBECUSD123456790",
      "status": "DELIVERED",
      "statusName": "Delivered",
      "deliveredAt": "2024-12-26T14:30:00Z"
    },
    {
      "trackingNumber": "CBECUSD123456791",
      "status": "OUT_FOR_DELIVERY",
      "statusName": "Out for Delivery"
    }
  ],
  "notFound": ["INVALID123456789"]
}

Use Cases

Dashboard Updates

Refresh status for all parcels on a customer’s order page

Manifest Tracking

Check status of all parcels in a shipment

Bulk Operations

Monitor large batches of orders

Scheduled Syncs

Periodic sync of parcel statuses to your database

Rate Limits

Batch tracking counts as a single request for rate limiting, but has a higher weight:

Request Size	Rate Limit Impact
1-10 parcels	1 request
11-50 parcels	2 requests
51-100 parcels	5 requests

For high-volume tracking, consider setting up webhooks to receive real-time updates instead of polling.

Single Tracking Get Label

​Request Body

​Response

​Use Cases

Dashboard Updates

Manifest Tracking

Bulk Operations

Scheduled Syncs

​Rate Limits

Request Body

Response

Use Cases

Rate Limits