Submit Manifest

Environments


Notes:

  • All parcels must be included in the manifest before being shipped. Any parcels that are not manifested may incur penalties for being un-manifested.
  • If you encounter any issues with the manifest, please contact SpeedX support as soon as possible at [email protected].

Response - Parcel Fail List

Error CodeError MessageDescriptionTrigger ConditionRecommended Action
ME100Not foundTracking number does not existTracking number not found in systemCheck if tracking number is correct and created
ME101Already submittedTracking number already manifestedAlready submitted in previous manifestNo need to resubmit
ME102Manifest is not neededManifest not requiredService type doesn't require manifestNo action needed
ME103Missing receptacle idMissing receptacle idService requires receptacle id but not providedAdd receptacle id and resubmit
ME104DuplicateDuplicate tracking numberSame tracking number appears multiple timesRemove duplicates and resubmit
ME105(Dynamic message)Processing failureVarious processing exceptions, details in errorMessageHandle based on specific error message
ME106Label does not belong to current userNo access to tracking numberUser has no permission to access this labelCheck user permissions and label ownership
ME107(Dynamic message)Update errorError updating label informationHandle based on specific error message
ME108The label is voidedLabel is voidedLabel status is VOIDEDCannot manifest voided labels
Body Params
parcelList
array of objects
required

Provide the list of tracking numbers which will be shipped. Single tracking number is not allowed. Max-size: 30000

parcelList*
string

Reference 1 of the shipment. Recommend to provide MAWB#

string

Reference 2 of the shipment

string

A brief description of the manifest

Headers
string
required

API key

Response

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json