# Publish parcel data

This endpoint allows the Carriers to publish parcel data into the OOH Platform. It should be used to push parcel data at the time when the locker booking is expected to take place or to pre-check if a parcel can be accepted in the locker.


Endpoint: POST /parcels/data
Version: 1.1.0
Security: ApiKeyAuth

## Request fields (application/json):

  - `eventType` (string, required)
    The type of booking request.
    Enum: "PRE_CHECK", "BOOKING"

  - `lockerUid` (string, required)
    The unique identifier of the locker in the GLS/NXT Platform.
    Example: "locker_567890"

  - `carrierParcelId` (string, required)
    The identifier of the parcel in the carrier's system.
    Example: "A123456789"

  - `shipmentType` (string)
    The possible types of last-mile shipments accepted.
    Enum: "LAST_MILE", "ALTERNATIVE_DELIVERY"

  - `consignee` (object,null)
    The details of the consignee.

  - `consignee.name` (string,null)
    Example: "John Doe"

  - `consignee.email` (string,null)
    Example: "john.doe@google.com"

  - `dimensions` (object, required)
    The dimensions of the parcel.

  - `dimensions.depth` (integer,null)
    Depth in mm
    Example: 190

  - `dimensions.height` (integer,null)
    Height in mm
    Example: 100

  - `dimensions.width` (integer,null)
    Width in mm
    Example: 140

  - `weight` (integer)
    Weight in grams
    Example: 400

  - `allocationType` (string)
    The allocation type of the shipment.
    Enum: "HARD_RESERVATION", "SOFT_RESERVATION"

## Response 200 fields (application/json):

  - `status` (string)
    The status of the event processing.
    Example: "success"

  - `message` (string)
    A message providing additional information about the event processing.
    Example: "Parcel event received and processed successfully"

  - `timestamp` (string)
    The timestamp when the event was processed.
    Example: "2023-06-18T10:45:00Z"

## Response 400 fields (application/json):

  - `errorCode` (string)
    A code representing the type of error.
    Example: "INVALID_REQUEST"

  - `message` (string)
    A message describing the error.
    Example: "Bad request due to invalid input"

## Response 401 fields (application/json):

  - `errorCode` (string)
    A code representing the type of error.
    Example: "UNAUTHORIZED"

  - `message` (string)
    A message describing the error.
    Example: "The requested resource requires authentication"

## Response 500 fields (application/json):

  - `errorCode` (string)
    A code representing the type of error.
    Example: "SERVER_ERROR"

  - `message` (string)
    A message describing the error.
    Example: "The server encountered an internal error"