Appendix

Ocean Carrier Identifiers

Here, you can find SCAC information for Ocean carriers connected to project44's network.

Official Name	Main SCAC	Alternate SCACs
Aliancia Navegacao e Logistica	ALIU	ALIU, ANRM
American Global Logistics	AGQA	AGQA
American President Lines	APLU	APLU
ANL Container Line	ANLC	ANLC, ANNU
Antillean Marine	AMLU	AMLU
Arkas Container Transport	ARKU	ARKU
Atlantic Container Line	ACLU	ACLU
Avana Logistek	AVNU	AVNU
Bayline	BAXU	BAXU
BDP International, Inc.	BOPT	BOPT
Bengal Tiger Line	TIGA	TIGA
Bertchi	BNAI	BNAI
Borchard Lines Ltd	BORU	BORU, MCLU
Cargo-Partner GmbH	CPNU	CPNU
Cargosmart Limited	XXCS	XXCS
CEVA Logistics	CEVA	CEVA, CEVAB2BSC
C.H. Robinson Worldwide, Inc	CHSL	CHSL, RBTW
Cheng Lie Navigation	CNCX	11DX, 42NY, CNCX
China Shipping Container Lines	CHNJ	CHNJ
China United Lines Ltd.	CULX	43FM, CULU, CULV, CULX
CIMC Worldwide Logistics	CWQG	CWQG
CK LINE Co., LTD.	CKCO	CKCO
CMA CGM	CMDU	CDMU, CMACGM, CMAU, CMCG, CMDU
Cobelfret	CLDN	CLDN
Compañía Chilena de Navegación Interoceánica S.A.	CNIU	CCNR, CNIU
Containerships	CSFU	CNAH, CSFU, CSOY
COSCO Shipping Lines	COSU	COAU, COEU, COSU
Crowley Liner Services	CMSN	CAMN, CLAM, CMCU, CMSN, CPRC, CWLQ
Damco	MZLY	DMCQ, MZLY
Delmas	DAAE	DAAE
Deutsche Africa-Linien	DALU	DALD, DALU, DAYU
DFDS	DFDS	DFDS
DHL Global Forwarding	DHLC	071695233, DHLC, DHLY, DNZA
Dole Ocean Cargo Express	DOLQ	DOLQ
DongJin Shipping	DJSC	DJSC
DSV A/S	DSVF	DSVF, DSVT
EFL	EFLR	EFLR
EIMSKIP	EIMU	EIMU
Emirates Shipping Line DMCEST	ESPU	EPIR, ESPU
EUKOR Car Carriers Inc.	EUKO	EUKO
Evergreen Line	EVRG	EGLV, EISU, EMCU, EVRG
Expeditors International of Washington, Inc.	EXPD	EXDO, EXPD
Far-Eastern Shipping Company	FANE	FANE, FESO
Gatehouse Maritime	GHMX	GHMX
Gemadept	GSC	GSC
Gold Star Line	GSLU	GMSU, GOSU, GSLU
Great White Fleet Corp.	GWFC	GWFC
Grimaldi Group	GRIU	GDSL, GRIMALDI, GRIU
Hamburg Sud	SUDU	SUDU
Hanjin Shipping Co., Ltd.	HJSC	HJSC
Hapag-Lloyd	HLCU	HLBU, HLCU, HLUS, HPET
Heung-A Shipping Co., Ltd	HALU	11QU, HALU, HASL
Hoegh Autoliners	HOEG	HOEG, HUAU
Hyde Shipping	HYDU	HYDU
Hyundai Glovis Co., Ltd.	HDGL	HDGL, HDGL0001
Hyundai Merchant Marine	HDMU	HDMU
ICL INDEPENDENT CONTAINER LINE	IILU	IILU
Ignazio Messina	LMCU	LMCU
Interasia Lines	IAAU	IAAU
JI ZHOU SHIPPING COMPANY	13UQ	13UQ
Kawasaki Kisen Kaisha, Ltd.	KLNE	KKLU, KLIS, KLNE
Kerry Logistics Network Limited	KRBG	KRBG
King Ocean	KOSL	KOSL
Kintetsu World Express	KWEO	KWEO
Korea Marine Transport	KMTU	KMDU, KMT9, KMTC, KMTU
Khuehne + Nagel	KHNN	BANQ, KHNN, KNPROD
Log-in Logística	LGIX	LGIX
LX Pantos	PNSG	PNSG
MacAndrews	MCAW	MCAW
MACS Shipping	MACS	MACS, MCSM
Maersk Line	MAEU	MAEU, MSKU
Marfret Compagnie Maritime	MFTU	MFTU, MFUS
Mariana Express Lines Pte Ltd.	MELL	MELL, MEPE
Matson	MATS	MATS, MATU, MNC001
Mediterranean Shipping Company	MSCU	MEDU, MSCU
Mercosul Line Navegacao e Logistica	MERX	MERX
Mitsui O.S.K. Lines	MOLU	MOLU
Namsung Shipping Co. Ltd.	NSSL	NSRU, NSSL
Newport Tank Lines	NPTC	NPTC
Nile Dutch Africa Line	NIDU	NDAV, NDSU, NIDU
Nippon Express Co., Ltd	NIPP	NIPP, NPNE
NYK Line (Nippon Yusen Kaisha)	NYKS	NYKS
Ocean Network Express	ONEY	ONEY
OPDR	OPDU	OPDU
Orient Overseas Container Line	OOLU	OOLU
Pan Continental Shipping Co. Ltd.	PCLU	15AC, PCLU
Pan Ocean	POBU	POBU
Panstar Co., Ltd.	PTMA	7PAN, PTMA
PIL Shipping	PILU	PABV, PCIU, PILU
PSL Navegacao SA	PSLU	PSLU
Qatar Navigation Line	QNLU	QNLU
Regional Container Lines	RCLU	RCLU, REGU
RIM Logistics LLC	RIML	RIML
Safmarine	SAFM	SAFM
Samudera Indonesia	SIKU	SIKU
San-ei Shipping co.,Ltd	SEIU	SEIU
Savino Del Bene S.p.a	SDBJ	SAVD, SAVI, SAVINODELBENE, SDBE, SDBJ, SVDL, SVFD
Schenker AG	SHKK	GOLA, SCNK, SHKK
Seaboard Marine	SMLU	SMLU
SeaLand	SEAU	MCCQ, MCPU, MMCQ, SEAL, SEAU, SEJJ, SGLU
SeaTrade International SA	STRD	SGNV, STRD
SEKO Logistics	SWOE	SWOE
Seth Shipping Corporation	SSPH	SSPH
Shanghai Jin Jiang Shipping Co.	JJCS	11WJ, JJCS, SHJJ
Shanghai PanAsia Shipping	SPAU	SPAU
Sinokor Merchant Marine	SKLU	SKHU, SKLU, SMM9, SNKO
Sinotrans Container Lines	SNTU	SNBG, SNBU, SNTU
SITC	SITU	12PD, SITU
SM Line	SMLM	SMLM
Stena Line	STNL	STLN
Stolt-Nielsen Limited	STZW	STZW
SUN HOPE SHIPPING CO LTD	SHBG	SHBG
Swire Shipping	CHVW	CHNL, CHVW, SWIRECNCO, SWSP
Tanto	TAKU	TAKU
Tarros S.p.a	TARR	GETU, TARR
TopOcean	TOPO	TOPO
TOTE Maritime	TOTE	TMGT, TOTE
Transmar Shipping Company	TMCU	TMCU
Tropical Shipping	TSGL	TSCW, TSGL
T.S. Lines	TSQD	13DF, TLWN, TSQD, TSSU, TSTU
Turkon Line Inc.	TRKU	TRKU
Unifeeder	UFEU	UFEE, UFEU
Unique Logistics	UNQL	UNQL
United Africa Feeder Line	UAFU	UAFU
United Arab Shipping Company	UACU	UACU, UASC, UASU
United European Car Carriers	UECC	UECC, VENT
United States Lines	USLU	USLU
UTC Overseas, Inc.	XUTC	ACDF, XUTC
UWL, Inc.	UWLD	UWLD
Wallenius Wilhelmsen ASA	WLWH	WLWH
Wan Hai Lines	MWHL	22AA, MWHL, WANHAI, WANU, WHLC, WHLU
West European Container Lines	WECC	WECC, WECU
Westwood Shipping Lines	SSBF	SSBF, SSBT, WWSU
X-Press Feeders Group	XCLX	XCLX
Yang Ming Marine	YMLU	YANGMING, YMJA, YMLU, YMPR
ZIM Integrated Shipping	ZIMU	LNLU, ZIMU

Ocean Event Types

Ocean Shipment Event Types

Below are the available Event Types for Ocean shipments and the descriptions for each Event Type.

Event Type	Description
`LOAD`	The shipment has been loaded onto the vessel. The container has been loaded onto the ship and is now officially in transit to the next port.
`DEPARTURE_FROM_STOP`	The vessel has departed from a port or inland facility.
`ARRIVAL_AT_STOP`	The vessel has arrived at a port or inland facility.
`DISCHARGE`	The shipment has been discharged from the vessel.
`DELIVERY`	The cargo has been delivered to the consignee. This event can be used to indicate tracking for a shipment has ended.
`TRACKING_START`	The shipment has been created and tracking has been initialized.
`TRACKING_INITIATE`	The shipment has been created, but tracking has not yet been initialized.
`WARNING`	The shipment exists in the project44 system, but there is an issue that is preventing tracking. See `WARNING` Event Type below for more information on the meaning behind this event type and a sample JSON response. In the description field, potential messages include `Carrier out of network`, `Duplicate subscription`, `Invalid identifier`, or `Tracking initialization failed`.

All Event Types can sometimes return an ETA or ATA. Please connect with your project44 Customer Success Manager to identify which event types return an ETA or ATA most often for your shipments.

Ocean Container Event Types

Below are the available Event Types for Ocean containers and the descriptions for each Event Type.

Event Type	Description
`AVAILABLE`	The data/time when this container was available.
`CUSTOMS_CLEARANCE`	The date/time when customs released this container.
`GATE_OUT_EMPTY`	The container has left the origin port of loading, origin place of receipt, or port of discharge to be filled by the manufacturer or shipper. This event can be used to indicate tracking for a shipment has ended.
`GATE_IN_FULL`	The container has been brought back to the origin port of loading or to the place of receipt/destination to be loaded onto the ship.
`DEPARTURE_FROM_STOP`	The vessel has departed from the port.
`ARRIVAL_AT_STOP`	The vessel has arrived at the port.
`GATE_OUT_FULL`	The container has left the port full at the origin, destination, or port of discharge to be unloaded.
`GATE_IN_EMPTY`	The container has returned empty to the port.
`RECEIVE_FROM_CARRIER`	The data/time when the carrier released this container.
`WARNING`	The shipment exists in the project44 system, but there is an issue that is preventing tracking. See `WARNING` Event Type below for more information on the meaning behind this event type and a sample JSON response. In the description field, potential messages include `Carrier out of network`, `Duplicate subscription`, `Invalid identifier`, or `Tracking initialization failed`.

All Event Types can sometimes return an ETA or ATA. Please connect with your project44 Customer Success Manager to identify which event types return an ETA or ATA most often for your shipments.

`WARNING` Event Type

The WARNING event type is returned when the shipment has been successfully created with project44 but there is an issue preventing tracking. An explanation of this issue is included in the description field for the event. Potential values for the description field include:

Carrier out of network
Duplicate subscription
Invalid identifier
Tracking initialization failed

Sample JSON response code with the WARNING event type:

{
   "shipment":{
      "id":"1a060d95-b135-4cb1-9146-2a805a2ebf50",
      "identifiers":[
         {
            "type":"CARRIER_SCAC",
            "value":"MWHL"
         },
         {
            "type":"BILL_OF_LADING",
            "value":"WHLC031C588296"
         }
      ],
      "shipmentShareLink":"https://na12.voc.project44.com/portal/v2/public/ma/tracking-details?shipmentShareToken=fcfb2857-5210-4cc7-912d-e0156e189c3e",
      "createdDateTime":"2023-01-17T17:05:46+0000"
   },
   "events":[
      {
         "dateTime":"2023-01-17T17:05:47+0000",
         "receivedDateTime":"2023-01-17T17:05:47+0000",
         "type":"WARNING",
         "description":"Ocean carrier out of network"
      }
   ]
}

Ocean Shipment State Types

Below are the accepted State Type values for Ocean shipments and the Event Types that trigger a State Type start or stop.

State Type	Start Event	Stop Event
`SCHEDULED`	`TRACKING_STARTED`	Any next event.
`IN_TRANSIT`	`DEPARTURE_FROM_STOP`, `GATE_OUT_EMPTY`, `GATE_OUT_FULL`	`ARRIVAL_AT_STOP`, `GATE_IN_EMPTY`, `GATE_IN_FULL`
`AT_STOP`	`GATE_IN_FULL`, `ARRIVAL_AT_STOP`	`DEPARTURE_FROM_STOP`, `GATE_OUT_FULL`, `GATE_OUT_EMPTY`
`COMPLETED`	`GATE_IN_EMPTY`	N/A
`UNKNOWN`	N/A	N/A

Ocean Shipment Stop Types

Stop Type	Details
`PORT_OF_LOADING`	Where container are loaded onto a vessel. NOTE: The ORIGIN, PICKUP, RETURN, or TRANSFER stop types are often the same location as the PORT_OF_LOADING or PORT_OF_DISCHARGE. In those situations, the stop type will show either PORT_OF_LOADING or PORT_OF_DISCHARGE.
`ORIGIN`	Where the empty container is filled by the shipper with the goods to be transported.
`TRANSSHIPMENT_PORT`	Where the containers were discharged from an initial vessel to be loaded on another vessel. There could be multiple transshipment ports along the transit or there could be no transshipment ports - depending on the shipment.
`PORT_OF_DISHCARGE`	Where the containers were discharged from the vessel. NOTE: The ORIGIN, PICKUP, RETURN, or TRANSFER stop types are often the same location as the PORT_OF_LOADING or PORT_OF_DISCHARGE. In those situations, the stop type will show either PORT_OF_LOADING or PORT_OF_DISCHARGE.
`DESTINATION`	Where the container is delivered to the consignee.
`UNKNOWN`	An undefined stop type.
`PICKUP`	Where the empty container is picked up.
`RETURN`	Where the empty container is returned.
`TRANSFER`	Where the land transfer stop is.

Route Segment Identifiers

This table describes the route segment identifiers for Ocean shipments.

Route Segment ID	Description
`VESSEL_NAME`	The name of the vessel assigned to the route segment.
`VESSEL_IMO`	The IMO number of the vessel assigned to the route segment.
`VOYAGE_NUMBER`	The voyage number/ID of the voyage of the vessel assigned to the route segment.

Error Response Codes

This Appendix describes the schema and fields of the standard project44 API Error Response.

Below, find the API Error Response Schema:

400 Invalid Request

{
  "httpStatusCode": 400,
  "httpMessage": "Invalid request",
  "errorMessage": "string",
  "errors": [
    {
      "severity": "ERROR",
      "message": "string",
      "diagnostic": "string",
      "source": "SYSTEM"
    }
  ],
  "supportReferenceId": "string"
}

401 Invalid or missing credentials

{
  "httpStatusCode": 401,
  "httpMessage": "Invalid or missing credentials",
  "errorMessage": "string",
  "errors": [
    {
      "severity": "ERROR",
      "message": "string",
      "diagnostic": "string",
      "source": "SYSTEM"
    }
  ],
  "supportReferenceId": "string"
}

403 User not authorized to perform this operation

{
  "httpStatusCode": 403,
  "httpMessage": "User not authorized to perform this operation",
  "errorMessage": "string",
  "errors": [
    {
      "severity": "ERROR",
      "message": "string",
      "diagnostic": "string",
      "source": "SYSTEM"
    }
  ],
  "supportReferenceId": "string"
}

404 Not Found

{
  "httpStatusCode": 404,
  "httpMessage": "Not Found",
  "errorMessage": "string",
  "errors": [
    {
      "severity": "ERROR",
      "message": "string",
      "diagnostic": "string",
      "source": "SYSTEM"
    }
  ],
  "supportReferenceId": "string"
}

The table below describes each field of the API Error Response:

Error Response Field	Description
`httpStatusCode`	The value of the HTTP status code. Possible values are: `400`, `401`, `403`, or `404`
`httpMessage`	A brief description of the HTTP status code. Possible values are: `Invalid request` (httpStatusCode = `400`), `Invalid or missing credentials` (httpStatusCode = `401`), `User not authorized to perform this operation` (httpStatusCode = `403`), or `Not Found` (httpStatusCode = `404`)
`errorMessage`	A detailed description of the error. For example: `"errorMessage": "Text '2022-03-23T18:38:00Z' could not be parsed, unparsed text found at index 19"`
`errors`	This array contains more details about the error
`errors.severity`	The severity of this message. Possible values are: `ERROR`, `WARNING`, or `INFO`
`error.message`	More information about the error.  For example: `Appointment in the Past`
`error.diagnostic`	Diagnostic information from project44 (The System) or from the Capacity Provider/Carrier. NOTE: In a Capacity Provider/Carrier integration, it would come only from project44.
`error.source`	The originator of the error message.  NOTE: In a Capacity Provider/Carrier integration, the originator will always be SYSTEM. Possible values are: `SYSTEM` (error from project44) or `CAPACITY PROVIDER` (error from the Capacity Provider or Carrier)
`supportReferenceId`	A reference identifier used by project44 support to assist with certain error messages.