# Get a specific Consignment by its UUID

Endpoint: GET /api/v5/consignments/{UUID}
Version: v5.7
Security: BearerToken

## Path parameters:

  - `UUID` (string, required)
    The unique UUID of this Consignment

## Response 200 fields (application/json):

  - `id` (string)
    Uniquely identifies this entity. A URI can be assigned by the client to indicate where more information
 can be retrieved. Note that every entity always has a unique EntityId. However since, OTM5.2 it is not
 required to send it in the request. One can be generated for you by the server.

  - `name` (string)
    Name of the entity. For display purposes and search only.

  - `creationDate` (string)
    The creation date of this entity.

  - `lastModified` (string)
    The last modified date of this entity. If none is given the creation date is used instead.

  - `contextEvents` (array)
    The context events provides some optional information about the events that can provide additional information
 on the current state of this entity.

For example: your system might send ETA information for the arrival of a vehicle on a location. To make it clear
what caused this ETA to be updated, we can include some information about what caused this ETA update by including
an event as context. If your ETA update was caused by a location update, this event can be included as context. If
the ETA was caused by a traffic accident on the route of the vehicle, you can include that event in the context.

  - `externalAttributes` (object)

  - `description` (string)
    General description of consignment in Free text. e.g 20 europallets fruit. Meant for human inspection, not for automating processes.

  - `status` (string)
    Whether this consignment is a draft, requested, confirmed, in transit, completed or cancelled. The values accepted
(replaced by confirmed) and modified (replaced the lastModified field on every entity) are deprecated since
OTM5.1, but will be supported for the whole OTM5.X line.
    Enum: "draft", "requested", "confirmed", "inTransit", "completed", "cancelled", "accepted", "modified"

  - `type` (string)
    Free text to describe type of consignment. Usually used to indicate the property types of the products being transported (e.g. frozen, fragile, etc.).

  - `goods` (array)
    The various goods that need to be transported, together they are part of this consignment.

  - `transportOrder` (any)
    The transport order this consignment belongs to.

  - `documents` (array)
    Documents that are relevant for this consignment. Such as an official agreement between consignee and consignor.

  - `remark` (string)
    Remark concerning the complete consignment, to be printed on the transport document.

  - `actors` (array)
    The actors associated with this consignment, for instance the shipper and carrier. One should inline the actors only on the top-level entity (such as the transportOrder or trip)

  - `actions` (array)
    General description of actions related to the consignment f.e. loading, unloading, hand over, drop of.

  - `constraint` (any)
    Constraints this consignment has to abide to, such special equipment (tail lift, truck mounted forklift), special
vehicle, special instructions related to consignor and consignee. Note that you can put the constraints on the
individual goods. However using constraints on the consignment is simpler and therefore recommended when
possible.

  - `relatedConsignments` (array)
    Consignments that have replaced the current consignment. Because of various reasons a consignment can be
cancelled and replaced by one or more other consignments. An example is that the consignment is too large
to be transported as a single 'transportable unit'. You can use the relation field in the association to
indicate the type of relationship.


## Response 404 fields