> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trackstarhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Trackstar is a unified REST API for WMS, cart, and carrier systems. Base URL: https://production.trackstarhq.com. There is no SDK; call the API with plain HTTP.
> Send x-trackstar-api-key on every request. Endpoints scoped to one connection also need x-trackstar-access-token. Read both from environment variables and never print them.
> Reads return data Trackstar has already synced from the connected system. Writes (POST, PUT, PATCH, DELETE) are forwarded to the connected system immediately.
> A new connection has no data until its initial sync finishes. Wait for the connection.historical-sync-completed webhook, or poll GET /connections/{connection_id} and check historical_sync_completed.
> List endpoints page with page_token and next_token (limit is capped at 1000). Repeat every filter on every page. Filters use field[operator]=value, for example created_date[gte]=2026-01-01T00:00:00Z.
> Write bodies must not contain null or empty strings; omit the field instead. Call GET /integrations/{integration_type}/{integration_name}/write-info first to learn the exact fields an integration accepts.
> To test without real credentials, POST /sandbox/generate-sandbox/{wms|cart|carrier} with the API key returns a sandbox access token. Start at https://docs.trackstarhq.com/how-to-guides/build-with-ai.md and install the skills with: npx skills add https://docs.trackstarhq.com

# Sample Files Overview

> Per-integration reference for the invoice CSV format each carrier delivers, with downloadable synthetic samples.

Each carrier delivers invoice data in its own CSV format. The pages in this group document those formats individually — what columns appear, what each column means, how multi-row shipments are structured, and where line-item charges live. Each integration has a downloadable synthetic CSV you can parse against without needing a live integration.

Most of these files are the **raw carrier file** served as-is, so they keep each carrier's own column names and casing. Royal Mail is the exception: its invoice and tracking data arrive separately, so Trackstar combines them into a single line-item file with normalized column names.

<Note>
  All sample data on these pages is **synthetic**. Tracking numbers, account numbers, addresses, and reference fields are fabricated and do not correspond to any real shipments or customers.
</Note>

## Integrations

| Integration | Regional variants | Delimiter | Column count | Charge structure |
| :- | :- | :- | :- | :- |
| [DHL eCommerce](/api-reference/carrier-api/sample-files/dhl-ecom) | — | `,` | 79 (no header row) | One row per shipment; charges spread across named columns (`Charge*`, `ZFuel*`, `ZSC*`, `ZRM*`) |
| [DHL Express](/api-reference/carrier-api/sample-files/dhl-express) | — | `,` | 153 | `Line Type` marker (`I` / `S`); charges in `XC1`–`XC9` column groups |
| [DPD](/api-reference/carrier-api/sample-files/dpd) | English (Dutch column aliases accepted) | `;` | 43 | One row per shipment; charges in named columns (`Base price`, `Energy surcharge`, `Fuel surcharge`, etc.) |
| [FedEx](/api-reference/carrier-api/sample-files/fedex) | US, International (UK / NL) | `,` | 210 (US) / 168 (International) | One row per shipment; charges in repeating `Label` / `Amount` column pairs |
| [Royal Mail](/api-reference/carrier-api/sample-files/royal-mail) | — | `,` | 16 | Trackstar-combined line-item file (not a raw carrier file); one row per tracked item |
| [UPS](/api-reference/carrier-api/sample-files/ups) | — | `,` | 250 | One row per **charge**; multiple rows per shipment share a tracking number |
| [USPS](/api-reference/carrier-api/sample-files/usps) | — | `,` | 21 | One row per transaction (1:1 with line items) |

## How to use these samples

* **Prototype your integration** without needing a live carrier connection. Download the CSV, run it through your own ingestion code, and compare against the schema documented on each page.
* **Understand the Trackstar `invoice_line_items` schema in context.** Each page lists which raw columns Trackstar maps to which normalized field (`tracking_number`, `invoice_id`, `charge_description`, `gross_cost`, `net_cost`, etc.).
* **Test your downstream systems** against realistic-shaped data, including multi-row shipments, multi-currency invoices, and empty optional columns.

For the normalized API that sits over all these formats, see [Invoice Line Items](/api-reference/carrier-api/invoice-line-items/info). For the raw-file endpoint that returns presigned URLs to a customer's actual (non-synthetic) files, see [Files](/api-reference/carrier-api/files/info).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.