Evergreen Marine Corp. Events API

openapi: 3.2.0
info:
  title: Evergreen Marine Events API
  version: '2.2'
  description: 'Operations tagged Events across 2 of this provider''s published API definitions: evergreen-marine-track-and-trace-openapi.json, evergreen-marine-track-and-trace-openapi.yml. Each path carries the servers of the definition it was published in.'
tags:
- name: Events
  description: Event Service Controller
paths:
  /tnt/v2/events:
    get:
      tags:
      - Events
      summary: Find events
      description: 'Returns all events filtered by the queryParameters.


        NB: It is possible to combine queryParameters. When combining queryParameters be aware that it is also possible to make combinations that are mutual contradicting.


        Example: shipmentEventTypeCode=DRFT and equipmentEventTypeCode=GTIN


        Since there is no event that can be a ShipmentEvent and an EquipmentEvent at the same time this will return an empty list!'
      operationId: eventGetUsingGET
      parameters:
      - name: API-Version
        in: header
        description: API-Version
        required: true
        schema:
          type: string
      - name: carrierBookingReference
        in: query
        description: A set of unique characters provided by carrier to identify a booking.<br/><br/><br/><br/>Specifying this filter will only return events related to this particular carrierBookingReference.
        required: false
        schema:
          type: string
      - name: carrierContract
        in: query
        description: Customized attribute. contract No. Not defined at DCSA.
        required: false
        schema:
          type: string
      - name: carrierServiceCode
        in: query
        description: Filter on the carrier specific identifier of the service.<br/><br/><br/><br/>Specifying this filter will only return events related to this particular carrierServiceCode.
        required: false
        schema:
          type: string
      - name: cursor
        in: query
        description: A server generated value to specify a specific point in a collection result, used for pagination.
        required: false
        schema:
          type: string
      - name: documentTypeCode
        in: query
        description: The documentTypeCode to filter by. Possible values are<br/><br/><br/><br/> - CBR (Carrier Booking Request Reference)<br/><br/> - BKG (Booking)<br/><br/> - SHI (Shipping Instruction)<br/><br/> - SRM (Shipment Release Message)<br/><br/> - TRD (Transport Document)<br/><br/> - ARN (Arrival Notice)<br/><br/> - VGM (Verified Gross Mass)<br/><br/> - CAS (Cargo Survey)<br/><br/> - CUS (Customs Inspection)<br/><br/> - DGD (Dangerous Goods Declaration)<br/><br/> - OOG (Out of Gauge)<br/><br/><br/><br/>It is possible to select multiple values by comma (,) separating them. For multiple values the OR-operator is used. For example <i>documentTypeCode=SHI,TRD</i> Matches <b>both</b> ShippingInstruction (SHI) and TransportDocument (TRD) shipment events.<br/><br/><br/><br/>Default is all documentTypeCodes.<br/><br/><br/><br/>This filter is only relevant when filtering on ShipmentEvents
        required: false
        schema:
          type: string
      - name: equipmentEventTypeCode
        in: query
        description: Unique identifier for equipmentEventTypeCode.<br/><br/><br/><br/> - LOAD (Loaded)<br/><br/> - DISC (Discharged)<br/><br/> - GTIN (Gated in)<br/><br/> - GTOT (Gated out)<br/><br/> - STUF (Stuffed)<br/><br/> - STRP (Stripped)<br/><br/> - PICK (Pick-up)<br/><br/> - DROP (Drop-off)<br/><br/> - INSP (Inspected)<br/><br/> - RSEA (Resealed)<br/><br/> - RMVD (Removed)<br/><br/>It is possible to select multiple values by comma (,) separating them. For multiple values the OR-operator is used. For example equipmentEventTypeCode=GTIN,GTOT matches both Gated in (GTIN) and Gated out (GTOT) equipment events.<br/><br/><br/><br/>Default is all equipmentEventTypeCodes.<br/><br/><br/><br/>This filter is only relevant when filtering on EquipmentEvents
        required: false
        schema:
          type: string
      - name: equipmentReference
        in: query
        description: Will filter by the unique identifier for the equipment, which should follow the BIC ISO Container Identification Number where possible.<br/><br/><br/><br/>Specifying this filter will only return events related to this particular equipmentReference
        required: false
        schema:
          type: string
      - name: eventCreatedDateTime
        in: query
        description: Limit the result based on the creating date of the event. It is possible to use operators on this query parameter. This is done by adding a colon followed by an operator at the end of the queryParameterName (before the =)<br/><br/><br/><br/>eventCreatedDateTime:gte=2021-04-01T14:12:56+01:00<br/><br/><br/><br/>would result in all events created ≥ 2021-04-01T14:12:56+01:00<br/><br/><br/><br/>The following operators are supported<br/><br/><br/><br/> - :gte (≥ Greater than or equal)<br/><br/> - :gt (> Greater than)<br/><br/> - :lte (≤ Less than or equal)<br/><br/> - :lt (< Less than)<br/><br/> - :eq (= Equal to)<br/><br/><br/><br/>If no operator is provided, a strictly equal is used (this is equivalent to :eq operator).
        required: false
        schema:
          type: string
      - name: eventType
        in: query
        description: The type of event(s) to filter by. Possible values are<br/><br/> - SHIPMENT (Shipment events)<br/><br/> - TRANSPORT (Transport events)<br/><br/> - EQUIPMENT (Equipment events)<br/><br/><br/><br/>It is possible to select multiple values by comma (,) separating them. For multiple values the OR-operator is used. For example eventType=SHIPMENT,EQUIPMENT matches both Shipment- and Equipment-events.<br/><br/><br/><br/>Default value is all event types.
        required: false
        schema:
          type: string
      - name: exportVoyageNumber
        in: query
        description: Filter on the vessel operator-specific identifier of the export Voyage.<br/><br/><br/><br/>Specifying this filter will only return events related to this particular exportVoyageNumber.
        required: false
        schema:
          type: string
      - name: limit
        in: query
        description: Maximum number of items to return.
        required: false
        x-example: 100
        schema:
          type: integer
          format: int32
      - name: shipmentEventTypeCode
        in: query
        description: The status of the document in the process to filter by. Possible values are<br/><br/><br/><br/> - RECE (Received)<br/><br/> - DRFT (Drafted)<br/><br/> - PENA (Pending Approval)<br/><br/> - PENU (Pending Update)<br/><br/> - REJE (Rejected)<br/><br/> - APPR (Approved)<br/><br/> - ISSU (Issued)<br/><br/> - SURR (Surrendered)<br/><br/> - SUBM (Submitted)<br/><br/> - VOID (Void)<br/><br/> - CONF (Confirmed)<br/><br/> - REQS (Requested)<br/><br/> - CMPL (Completed)<br/><br/> - HOLD (On Hold)<br/><br/> - RELS (Released)<br/><br/><br/><br/>It is possible to select multiple values by comma (,) separating them. For multiple values the OR-operator is used. For example <i>sshipmentEventTypeCode=RECE,DRFT</i> Matches <b>both</b> Received (RECE) and Drafted (DRFT) shipment events.<br/><br/><br/><br/>Default is all shipmentEventTypeCodes.<br/><br/><br/><br/>This filter is only relevant when filtering on ShipmentEvents
        required: false
        schema:
          type: string
      - name: sort
        in: query
        description: A comma-separated list of field names to define the sort order. Field names should be suffixed by a (:) followed by either the keyword ASC (for ascending order) or DESC (for descening order) to specify direction. <b>:ASC</b> may be omitted, in which case ascending order will be used.
        required: false
        x-example: event_create_datetime:ASC
        schema:
          type: string
      - name: transportCallID
        in: query
        description: ID uniquely identifying a transport call, to filter events by.<br/><br/><br/><br/>Specifying this filter will only return events related to this particular transportCallID
        required: false
        schema:
          type: string
      - name: transportDocumentReference
        in: query
        description: A unique number reference allocated by the shipping line to the transport document and the main number used for the tracking of the status of the shipment.<br/><br/><br/><br/>Specifying this filter will only return events related to this particular transportDocumentReference
        required: false
        schema:
          type: string
      - name: transportEventTypeCode
        in: query
        description: Identifier for type of Transport event to filter by<br/><br/><br/><br/> - ARRI (Arrived)<br/><br/> - DEPA (Departed)<br/><br/> - It is possible to select multiple values by comma (,) separating them. For multiple values the OR-operator is used. For example transportEventTypeCode=ARRI,DEPA matches both Arrived (ARRI) and Departed (DEPA) transport events.<br/><br/><br/><br/>Default is all transportEventTypeCodes.<br/><br/><br/><br/>This filter is only relevant when filtering on TransportEvents
        required: false
        schema:
          type: string
      - name: unLocationCode
        in: query
        required: false
        schema:
          type: string
      - name: vesselIMONumber
        in: query
        description: The identifier of vessel for which schedule details are published. Depending on schedule type,this may not be available yet.<br/><br/><br/><br/>Specifying this filter will only return events related to this particular vesselIMONumber.
        required: false
        schema:
          type: string
      responses:
        '200':
          description: Successful operation
          headers:
            Prev-Page:
              schema:
                type: string
            First-Page:
              schema:
                type: string
            Last-Page:
              schema:
                type: string
            Next-Page:
              schema:
                type: string
            Current-Page:
              schema:
                type: string
            API-Version:
              schema:
                type: string
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EventServiceData'
        '201':
          description: Created
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '404':
          description: Not Found
components:
  schemas:
    vessel:
      type: object
      required:
      - vesselIMONumber
      properties:
        vesselCallSignNumber:
          type: string
          example: NCVV
          description: A unique alphanumeric identity that belongs to the vessel and is assigned by the International Telecommunication Union (ITU). It consists of a threeletter alphanumeric prefix that indicates nationality, followed by one to four characters to identify the individual vessel. For instance, vessels registered under Denmark are assigned the prefix ranges 5PA-5QZ, OUAOZZ, and XPA-XPZ. The Call Sign changes whenever a vessel changes its flag.
        vesselFlag:
          type: string
          example: DE
          description: The flag of the nation whose laws the vessel is registered under. This is the ISO 3166 two-letter country code
        vesselIMONumber:
          type: string
          example: 9321483
          description: The unique reference for a registered Vessel. The reference is the International Maritime Organisation (IMO) number, also sometimes known as the Lloyd's register code, which does not change during the lifetime of the vessel
        vesselName:
          type: string
          example: King of the Seas
          description: The name of the Vessel given by the Vessel Operator and registered with IMO.
        vesselOperatorCarrierCode:
          type: string
          example: MAEU
          description: The carrier who is in charge of the vessel operation based on either the SMDG or SCAC code lists
        vesselOperatorCarrierCodeListProvider:
          type: string
          example: NMFTA
          description: Identifies the code list provider used for the operator and partner carriercodes.
      title: vessel
      description: describes a floating, sea going structure (mother vessels and feeder vessels) with either an internal or external mode of propulsion designed for the transport of cargo and/or passengers. Ocean vessels are uniquely identified by an IMO number consisting of 7 digits, or alternatively by their AIS signal with an MMSI number.
    seals:
      type: object
      required:
      - sealNumber
      - sealType
      properties:
        sealNumber:
          type: string
          description: Identifies a seal affixed to the container.
        sealSource:
          type: string
          description: The source of the seal, namely who has affixed the seal. This attribute links to the Seal Source ID defined in the Seal Source reference data entity.<br/><br/><br/><br/> - CAR (Carrier)<br/><br/> - SHI (Shipper)<br/><br/> - PHY (Phytosanitary)<br/><br/> - VET (Veterinary)<br/><br/> - CUS (Customs)
        sealType:
          type: string
          description: The type of seal. This attribute links to the Seal Type ID defined in the Seal Type reference data entity.<br/><br/><br/><br/> - KLP (Keyless padlock)<br/><br/> - BLT (Bolt)<br/><br/> - WIR (Wire)
      title: seals
    EquipmentEvent:
      type: object
      required:
      - equipmentEventTypeCode
      - eventClassifierCode
      - eventCreatedDateTime
      - eventDateTime
      - eventType
      properties:
        documentReferences:
          type: array
          description: An optional list of key-value (documentReferenceType-documentReferenceValue) pairs representing links to objects relevant to the event. The documentReferenceType-field is used to describe where the documentReferenceValue-field is pointing to.
          items:
            $ref: '#/components/schemas/documentReferences'
        equipmentEventTypeCode:
          type: string
          example: LOAD
          description: Unique identifier for equipmentEventTypeCode.<br/><br/><br/><br/> - LOAD (Loaded)<br/><br/> - DISC (Discharged)<br/><br/> - GTIN (Gated in)<br/><br/> - GTOT (Gated out)<br/><br/> - STUF (Stuffed)<br/><br/> - STRP (Stripped)<br/><br/> - PICK (Pick-up)<br/><br/> - DROP (Drop-off)<br/><br/> - INSP (Inspected)<br/><br/> - RSEA (Resealed)<br/><br/> - RMVD (Removed)<br/><br/><br/><br/>More details can be found on GitHub<br/><br/>
        equipmentReference:
          type: string
          example: APZU4812090
          description: ' The unique identifier for the equipment,  which should follow the BIC ISO Container Identification Number where possible. According to ISO 6346,  a container identification code consists of a 4-letter prefix and a 7-digit number  (composed of a 3-letter owner code, a category identifier, a serial number, and a check-digit).  If a container does not comply with ISO 6346,  it is suggested to follow Recommendation #2 “Container with non-ISO identification” from SMDG.'
        eventClassifierCode:
          type: string
          example: EST
          description: Code for the event classifier can be<br/><br/><br/><br/> - PLN (Planned)<br/><br/> - ACT (Actual)<br/><br/> - EST (Estimated)
        eventCreatedDateTime:
          type: string
          example: '2021-01-09T14:12:56+01:00'
          description: 'The timestamp of when the event was created.<br/><br/><br/><br/>NB: This field should be considered Metadata'
        eventDateTime:
          type: string
          format: date-time
          example: '2019-11-12T07:41:00+08:30'
          description: The local date and time, where the event took place or when the event will take place, in ISO 8601 format.
        eventID:
          type: string
          example: 3cecb101-7a1a-43a4-9d62-e88a131651e2
          description: 'The unique identifier for the event (the message - not the source).<br/><br/><br/><br/>NB: This field should be considered Metadata'
        eventLocation:
          description: generally used to capture location-related data, also for locations without UN Location Codes.
          $ref: '#/components/schemas/location'
        eventType:
          type: string
          example: EQUIPMENT
          description: 'The Event Type of the object - to be used as a discriminator.<br/><br/><br/><br/>NB: This field should be considered Metadata'
          enum:
          - EQUIPMENT
          - SHIPMENT
          - TRANSPORT
        isoequipmentCode:
          type: string
        references:
          type: array
          description: references provided by the shipper or freight forwarder at the time of booking or at the time of providing shipping instruction. Carriers share it back when providing track and trace event updates, some are also printed on the B/L. Customers can use these references to track shipments in their internal systems.
          items:
            $ref: '#/components/schemas/references'
        seals:
          type: array
          description: addresses the seal-related information associated with the shipment equipment. A seal is put on a shipment equipment once it is loaded. This seal is meant to stay on until the shipment equipment reaches its final destination.
          items:
            $ref: '#/components/schemas/seals'
        transportCall:
          $ref: '#/components/schemas/TransportCall'
      title: EquipmentEvent
    address:
      type: object
      properties:
        city:
          type: string
          example: København
          description: The city name of the party’s address.
        country:
          type: string
          example: Denmark
          description: The country of the party’s address.
        floor:
          type: string
          example: 5. sal
          description: The floor of the party’s street number.
        name:
          type: string
          example: Henrik
          description: Name of the address
        postCode:
          type: string
          example: 1306
          description: The post code of the party’s address.
        stateRegion:
          type: string
          example: N/A
          description: The state/region of the party’s address.
        street:
          type: string
          example: Kronprincessegade
          description: The name of the street of the party’s address.
        streetNumber:
          type: string
          example: 54
          description: The number of the street of the party’s address.
      title: address
      description: Address related information
    documentReferences:
      type: object
      properties:
        documentReferenceType:
          type: string
          description: Describes where the documentReferenceValue is pointing to
        documentReferenceValue:
          type: string
          description: The value of the identifier the documentReferenceType is describing
      title: documentReferences
    ShipmentEvent:
      type: object
      required:
      - documentID
      - eventClassifierCode
      - eventCreatedDateTime
      - eventDateTime
      - eventType
      - shipmentEventTypeCode
      properties:
        documentID:
          type: string
          example: the-id-of-the-documentTypeCode
          description: The id of the object defined by the documentTypeCode.
        documentTypeCode:
          type: string
          example: SHI
          description: The code to identify the type of information documentID points to. Can be one of the following values<br/><br/><br/><br/> - CBR (Carrier Booking Request Reference)<br/><br/> - BKG (Booking)<br/><br/> - SHI (Shipping Instruction)<br/><br/> - SRM (Shipment Release Message)<br/><br/> - TRD (Transport Document)<br/><br/> - ARN (Arrival Notice)<br/><br/> - VGM (Verified Gross Mass)<br/><br/> - CAS (Cargo Survey)<br/><br/> - CUS (Customs Inspection)<br/><br/> - DGD (Dangerous Goods Declaration)<br/><br/> - OOG (Out of Gauge)<br/><br/><br/><br/>More details can be found on GitHub<br/><br/>
        eventClassifierCode:
          type: string
          example: ACT
          description: Code for the event classifier can be<br/><br/><br/><br/> - ACT (Actual)<br/><br/> - PLN (Planned)<br/><br/> - EST (Estimated)
        eventCreatedDateTime:
          type: string
          example: '2021-01-09T14:12:56+01:00'
          description: 'The timestamp of when the event was created.<br/><br/><br/><br/>NB: This field should be considered Metadata'
        eventDateTime:
          type: string
          format: date-time
          example: '2019-11-12T07:41:00+08:30'
          description: The local date and time, where the event took place or when the event will take place, in ISO 8601 format.
        eventID:
          type: string
          example: 3cecb101-7a1a-43a4-9d62-e88a131651e2
          description: 'The unique identifier for the event (the message - not the source).<br/><br/><br/><br/>NB: This field should be considered Metadata'
        eventType:
          type: string
          example: SHIPMENT
          description: 'The Event Type of the object - to be used as a discriminator.<br/><br/><br/><br/>NB: This field should be considered Metadata'
          enum:
          - EQUIPMENT
          - SHIPMENT
          - TRANSPORT
        reason:
          type: string
          example: The following attributes are missing...
          description: Reason field in a Shipment event. This field can be used to explain why a specific event has been sent
        references:
          type: array
          description: references provided by the shipper or freight forwarder at the time of booking or at the time of providing shipping instruction. Carriers share it back when providing track and trace event updates, some are also printed on the B/L. Customers can use these references to track shipments in their internal systems.
          items:
            $ref: '#/components/schemas/references'
        shipmentEventTypeCode:
          type: string
          example: DRFT
          description: The status of the document in the process. Possible values are<br/><br/><br/><br/> - RECE (Received)<br/><br/> - DRFT (Drafted)<br/><br/> - PENA (Pending Approval)<br/><br/> - PENU (Pending Update)<br/><br/> - REJE (Rejected)<br/><br/> - APPR (Approved)<br/><br/> - ISSU (Issued)<br/><br/> - SURR (Surrendered)<br/><br/> - SUBM (Submitted)<br/><br/> - VOID (Void)<br/><br/> - CONF (Confirmed)<br/><br/> - REQS (Requested)<br/><br/> - CMPL (Completed)<br/><br/> - HOLD (On Hold)<br/><br/> - RELS (Released)<br/><br/><br/><br/>More details can be found on GitHub<br/><br/>
          enum:
          - APPR
          - CMPL
          - CONF
          - DRFT
          - HOLD
          - ISSU
          - PENA
          - PENU
          - RECE
          - REJE
          - RELS
          - REQS
          - SUBM
          - SURR
          - VOID
      title: ShipmentEvent
    TransportEvent:
      type: object
      required:
      - eventClassifierCode
      - eventCreatedDateTime
      - eventDateTime
      - eventType
      - transportEventTypeCode
      properties:
        changeRemark:
          type: string
          description: Free text information provided by the vessel operator regarding the reasons for the change in schedule and/or plans to mitigate schedule slippage.
        delayReasonCode:
          type: string
          example: WEA
          description: Reason code for the delay. The SMDG-Delay-Reason-Codes are used for this attribute. The code list can be found at http://www.smdg.org/smdg-code-lists/
        documentReferences:
          type: array
          description: An optional list of key-value (documentReferenceType-documentReferenceValue) pairs representing links to objects relevant to the event. The documentReferenceType-field is used to describe where the documentReferenceValue-field is pointing to.
          items:
            $ref: '#/components/schemas/documentReferences'
        eventClassifierCode:
          type: string
          example: ACT
          description: Code for the event classifier can be<br/><br/><br/><br/> - ACT (Actual)<br/><br/> - PLN (Planned)<br/><br/> - EST (Estimated)
        eventCreatedDateTime:
          type: string
          example: '2021-01-09T14:12:56+01:00'
          description: 'The timestamp of when the event was created.<br/><br/><br/><br/>NB: This field should be considered Metadata'
        eventDateTime:
          type: string
          format: date-time
          example: '2019-11-12T07:41:00+08:30'
          description: The local date and time, where the event took place or when the event will take place, in ISO 8601 format.
        eventID:
          type: string
          example: 3cecb101-7a1a-43a4-9d62-e88a131651e2
          description: 'The unique identifier for the event (the message - not the source).<br/><br/><br/><br/>NB: This field should be considered Metadata'
        eventType:
          type: string
          example: TRANSPORT
          description: 'The Event Type of the object - to be used as a discriminator.<br/><br/><br/><br/>NB: This field should be considered Metadata'
          enum:
          - EQUIPMENT
          - SHIPMENT
          - TRANSPORT
        transportCall:
          $ref: '#/components/schemas/TransportCall'
        transportEventTypeCode:
          type: string
          example: ARRI
          description: Identifier for type of Transport event<br/><br/><br/><br/> - ARRI (Arrived)<br/><br/> - DEPA (Departed)<br/><br/><br/><br/>More details can be found on GitHub
          enum:
          - ARRI
          - DEPA
      title: TransportEvent
    TransportCall:
      type: object
      required:
      - modeOfTransport
      - transportCallID
      properties:
        carrierServiceCode:
          type: string
          example: FE1
          description: The code of the service for which the schedule details are published.
        exportVoyageNumber:
          type: string
          example: 2103S
          description: The vessel operator-specific identifier of the export Voyage.
        facilityCode:
          type: string
          example: ADT
          description: The code used for identifying the specific facility. This code does not include the UN Location Code.
        facilityCodeListProvider:
          type: string
          example: SMDG
          description: The provider used for identifying the facility Code
        facilityTypeCode:
          type: string
          example: POTE
          description: A specialized version of the facilityCode to be used in TransportCalls. The code to identify the specific type of facility.<br/><br/><br/><br/> - BOCR (Border crossing)<br/><br/> - CLOC (Customer location)<br/><br/> - COFS (Container freight station)<br/><br/> - COYA (Deprecated - use OFFD intead)<br/><br/> - OFFD (Off dock storage)<br/><br/> - DEPO (Depot)<br/><br/> - INTE (Inland terminal)<br/><br/> - POTE (Port terminal)<br/><br/> - RAMP (Ramp)
        importVoyageNumber:
          type: string
          example: 2103N
          description: The vessel operator-specific identifier of the import Voyage.
        location:
          $ref: '#/components/schemas/location'
        modeOfTransport:
          type: string
          description: The mode of transport as defined by DCSA.
        otherFacility:
          type: string
          example: Depot location or address
          description: An alternative way to capture the facility when no standardized DCSA facility code can be found.
        transportCallID:
          type: string
          example: 123e4567-e89b-12d3-a456-426614174000
          description: The unique identifier for a transport call
        transportCallSequenceNumber:
          type: integer
          format: int32
          example: 2
          description: Transport operator's key that uniquely identifies each individual call. This key is essential to distinguish between two separate calls at the same location within one voyage.
        unlocationCode:
          type: string
        vessel:
          $ref: '#/components/schemas/vessel'
      title: TransportCall
    location:
      type: object
      properties:
        address:
          $ref: '#/components/schemas/address'
        facilityCode:
          type: string
          example: ADT
          description: The code used for identifying the specific facility. This code does not include the UN Location Code.
        facilityCodeListProvider:
          type: string
          example: SMDG
          description: The provider used for identifying the facility Code
        latitude:
          type: string
          example: 48.85855
          description: Geographic coordinate that specifies the north–south position of a point on the Earth's surface.
        locationName:
          type: string
          example: Eiffel Tower
          description: The name of the location.
        longitude:
          type: string
          example: 2.294492036
          description: Geographic coordinate that specifies the east–west position of a point on the Earth's surface.
        unlocationCode:
          type: string
      title: location
      description: Location of the facility. Can often be omitted when it is just repeating the contents of the UNLocationCode field.
    EventServiceData:
      type: object
      properties:
        equipmentEvent:
          $ref: '#/components/schemas/EquipmentEvent'
        shipmentEvent:
          $ref: '#/components/schemas/ShipmentEvent'
        transportEvent:
          $ref: '#/components/schemas/TransportEvent'
      title: EventServiceData
    references:
      type: object
      required:
      - referenceValue
      properties:
        referenceType:
          type: string
          example: FF
          description: The reference type codes defined by DCSA.<br/><br/><br/><br/> - FF (Freight Forwarder’s Reference)<br/><br/> - SI (Shipper’s Reference)<br/><br/> - PO (Purchase Order Reference)<br/><br/> - CR (Customer’s Reference)<br/><br/> - AAO (Consignee’s Reference)<br/><br/> - EQ (Equipment Reference)
        referenceValue:
          type: string
          description: The actual value of the reference.
      title: references
x-refined-from:
- evergreen-marine-track-and-trace-openapi.json
- evergreen-marine-track-and-trace-openapi.yml