Skip to main content
POST
Submits a manifest that groups multiple parcels under an Air Waybill (AWB) for a single shipment. This is typically done before parcels are handed over to the carrier.

Request Body

string
Optional unique key to prevent duplicate submissions (8-64 characters).
string
required
Air Waybill number (8-20 characters). Format: XXX-XXXXXXXX (carrier prefix + 8 digits).
string
Flight number (e.g., LA2480).
string
Scheduled flight date in YYYY-MM-DD format.
string
Origin airport code (e.g., MIA).
string
Destination airport code (e.g., UIO).
string
Carrier name (e.g., LATAM Airlines).
string
Destination country code (2-letter ISO).
array
required
List of parcels to include in the manifest.
string
Base64-encoded AWB PDF document.

Response

boolean
Whether the manifest was submitted successfully
object
The created shipment details
integer
Number of parcels successfully linked to the shipment
array
Tracking numbers that were not found in the system

Validation Rules

  • All tracking numbers must exist in the system
  • Parcels must be in LABEL_GENERATED or ORDERED status
  • Parcels cannot already be assigned to another manifest
  • AWB number format: 3-digit carrier prefix + 8 digits (e.g., 180-12345678)
  • Cannot reuse an AWB that has already been submitted
  • Cannot modify a manifest after submission
  • Ecuador: Receiver ID (Cédula/RUC) validated against SRI database
  • Mexico: RFC format validated if provided
  • Colombia: Cédula format validated

Bag Codes

Parcels can be grouped into bags using the bagCode field. This is optional but recommended for large shipments.
Bags help with:
  • Physical grouping during shipping
  • Customs documentation
  • Weight tracking per container