---
title: "Create a Shipping Manifest"
method: POST
path: "/ship/manifest"
tags: ["Manifest"]
---

# Create a Shipping Manifest

`POST /ship/manifest`

Group multiple shipment tracking numbers into a single manifest document that the carrier driver uses to verify packages at pickup.

**When to use:** Call this endpoint at the end of your shipping batch — typically before a scheduled pickup — to consolidate all outgoing shipments into one manifest for the carrier.

**Prerequisites:**
- Valid JWT authentication token (Bearer)
- One or more valid tracking numbers from previously generated labels

**Key behaviors:**
- Returns a manifest ID and a downloadable manifest document URL
- The manifest lists all included tracking numbers for carrier verification
- Some carriers require a manifest (also called "close-out" or "end-of-day") before pickup
- Each tracking number can only belong to one manifest

## Request body

- object
  - `trackingNumbers` string[], required — Array of tracking numbers to include in the manifest. These are the shipment identifiers that will be grouped together for warehouse pickup and handoff to the carrier.

## Response `200`

Manifest created successfully. Returns the manifest ID, creation timestamp, list of included tracking numbers, and a download URL for the manifest document.

- object
  - `meta` string
  - `data` object
    - `manifestId` string — Manifest ID
    - `manifestUrl` string — URL to download the manifest
    - `trackingNumbers` string[] — List of tracking numbers included in the manifest

---

[API](https://skmtc.net/envia/apis/envia-shipping-api-complete-documentation.md) · [All operations](https://skmtc.net/envia/apis/envia-shipping-api-complete-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/envia/envia-shipping-api-complete-documentation/revisions/39f9208959d6/schema)