Tracking

List Tracked Shipments

GET /api/v1/tracking

Return resolved standalone tracking records for the API key's organization and mode.

Query Parameters

Param	Type	Description
`limit`	number	Max results (1-100, default 10)
`starting_after`	string	Cursor for forward pagination

Response

{
  "object": "list",
  "url": "/api/v1/tracking",
  "data": [
    {
      "object": "tracked_shipment",
      "id": 1,
      "tracking_number": "123456789",
      "carrier": "R+L Carriers",
      "status": "In Transit",
      "location": "Nashville, TN",
      "source": "external",
      "last_checked_at": "2026-07-01T12:00:00.000Z",
      "created_at": "2026-07-01T11:00:00.000Z",
      "updated_at": "2026-07-01T12:00:00.000Z"
    }
  ],
  "has_more": false
}

Track a Shipment

POST /api/v1/tracking

Start tracking a shipment by PRO number.

Request Body

Field	Type	Required	Description
`tracking_number`	string	Yes	PRO number (1-50 chars)
`carrier`	string	No	Carrier name (default: `R+L Carriers`)

Example

curl -X POST https://api.freightcake.com/api/v1/tracking \
  -H "Authorization: Bearer fk_test_REPLACE_WITH_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "tracking_number": "123456789" }'

Get Tracking Details

GET /api/v1/tracking/:tracking_number

Returns current tracking status for a specific PRO number.

Refresh Tracking

POST /api/v1/tracking/:tracking_number/refresh

Force a fresh tracking status check from the carrier.

If the carrier request fails, FreightCake returns the last stored tracking state instead of discarding it.

Stop Tracking

DELETE /api/v1/tracking/:tracking_number

Remove a PRO number from standalone tracking.

Errors

Status	When
`400`	The tracking number or carrier is invalid
`404`	The tracked shipment does not exist in the API key's organization or mode

See Handle API Errors for the common error envelope and retry guidance.

On this page