> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/package-api/package-api/core-concepts/manifests.md).

# Manifests

A manifest is the air freight consolidation document that groups physical pallets onto a specific flight. It drives customs pre-clearance and is required for all cross-border air shipments.

{% stepper %}
{% step %}

#### **Update packages**

When packages are physically loaded onto pallets at the hub, update each package with its `palletId` via `PUT /Package`.

The pallet ID must match the barcode affixed to the physical pallet at the airport.
{% endstep %}

{% step %}

#### **Confirm all packages are Complete**

Every package referenced in the manifest must be in `shippingStatus:Complete`.

Pending packages cannot be manifested. They haven't been physically tendered to the carrier.
{% endstep %}

{% step %}

#### **Submit the manifest**

`POST /Manifest` — Submit with the manifest number, airport codes, carrier ID, ground handling agent, flight details, and the full pallet-to-package mapping using `eShopPackageReferences`.
{% endstep %}

{% step %}

#### **Pre-clearance transmits automatically**

ESW's customs filing engine transmits Advance Electronic Data (AED) to the destination country customs authority.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
For US shipments, CBP requires this at least 2 hours before departure (ACAS rules).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.esw.com/package-api/package-api/core-concepts/manifests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.