After purchasing all labels for the day, collect the warehouse_id for the origin location you want to manifest
POST to /v1/manifests with 'carrier_id', 'ship_date', and 'warehouse_id'; ShipEngine queues the manifest generation
Poll GET /v1/manifests/{manifest_id} until 'status' is 'completed'; then download the manifest from the 'manifest_download.href' URL
Print and tender the manifest to the carrier driver along with the day's packages; the manifest barcode enables bulk acceptance scanning
Manifests must be created on or for the same ship_date as the labels; post-dating or back-dating manifests is not supported by most carriers
Known gotchas
Not all carriers support manifest generation via ShipEngine; check the ShipEngine carrier documentation for manifest support before relying on it in production
Creating a manifest does not automatically include all labels — only labels associated with the specified warehouse_id and ship_date are included; verify the package count matches expectations
USPS requires SCAN form submission before the carrier induction cutoff time; generate the manifest well before driver arrival to avoid missed pickups
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp