Integrate with the same operational order model.
Technical documentation for shipment execution, tracking, labels, manifests, customs and status handling. This data does not stand alone: it feeds the same order context MMCore uses to connect execution, actual cost and result.
GET /get_tracking_information/{API_KEY}/{barcode}
?type=barcode
&flight_tracking_setting=include
&lang=ENOverview
MMCore connects operational shipment data to the wider order context: execution, tracking, carrier cost and financial control. Use the documented authentication method for each endpoint family and keep credentials server-side.
Authentication
Authentication is endpoint-specific. The tracking route below uses the existing MMCore structure where the API key is part of the server-side request path. Never expose this key in browser code.
Shipments
Shipment creation uses the v2 shipment route. Request and response fields should be taken from the current MMCore API reference.
POST /v2/shipmentsTracking
Barcode tracking uses this request shape. The website uses the same route through a server-side proxy so the key is never exposed to the client.
/get_tracking_information/{API_KEY}/{barcode}?type=barcode&flight_tracking_setting=include&lang=ENhostMMCore=https://api.mmcore.techAPIKEYCARRIERTESTER=••••••••Labels
Labels are retrieved using the shipment UUID.
GET /v2/shipments/{uuid}/labelsManifests
Use the validated MMCore API reference for field definitions and current response contracts. This website does not add unverified parameters.
Customs
Use the validated MMCore API reference for field definitions and current response contracts. This website does not add unverified parameters.
Status codes
Use the validated MMCore API reference for field definitions and current response contracts. This website does not add unverified parameters.
Errors
Use the validated MMCore API reference for field definitions and current response contracts. This website does not add unverified parameters.
