> ## 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

# Inbound Shipments

> Advance shipping notices from a supplier to a warehouse, with statuses and receipt tracking

An Inbound Shipment (also known as an Advance Shipping Notice, ASN, or Receiving Order) is a record of a shipment from a supplier
(usually a vendor or factory) to a warehouse. Shipments are often associated with a Purchase Order, which represents the order
that the warehouse sent to the supplier.

The Inbound Shipment contains information about the items being sent, including their individual
`inventory_item_id`s. These IDs can be passed into the [`/wms-api/inventory/{inventory_item_id}`](/api-reference/wms-api/inventory/get-item) endpoint for more details.

### Inbound Shipment Statuses (in order of lifecycle)

| Status | Definition |
| :- | :- |
| `open` | Shipment record has been created and items are not yet in the warehouse. |
| `in-transit` | Items are on their way to the warehouse. |
| `receiving` | The warehouse has begun the receiving process for the shipment. |
| `received` | Items have been received in the warehouse. |
| `cancelled` | Shipment has been cancelled by either the warehouse or the customer. |
| `other` | Status of the shipment can't be determined. Often due to a custom status being used. See raw\_status field for more info. |


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