Bookings
Booking API for booking containers through to all major carriers.
home
10/04/2021 V0.0.1
- gross_weight field added for each package. (mandatory field)
- total_gross_weight field added on the booking object. (Read only field. Will be calculated by the API based on each individual package gross_weight)
weight_unit field added on the booking_object to globally set the weight unit
21/04/2021 V0.0.2
- bookings object now has a legs attribute which is an href to the legs sub resource. This will only be present if legs have been added to the booking
22/04/2021 V0.0.3
- Added change to the GET for the new legs object
28/04/2021 V0.0.4
- equipments has been moved to a separate sub-resource. A GET on the bookings object will now give an href to equipments. A subsequent GET on the equipments sub-resource will give a list of equipments and href to haulages
- haulages are moved to a separate sub-resource. This is work in progress
- references are added on the booking object
07/05/2021 V 0.0.5
- booking_reference renamed to reference
- booking_comments renamed to comments
- booking_response_type renamed to response_type
- removed message field in a successful response
- error message format changed to have trace, message, code, status instead of just message (WIP)
13/05/2021 V 0.0.6
- Added a 204 response for legs and haulages when they don't exist
- Messages have been removed from success responses and the error message format is changed to have trace, message, code, status instead of just message
19/05/2021 V 0.0.7
- Added the PUT API on legs sub-resource
- Added allocations attribute on the bookings.packages object
- Added container_number and reference on bookings.equipments object
02/06/2021 V 1.0.1
- Adding organisation_id (read only field) to the payload for GET on /bookings and /bookings/{ref} endpoints. (Non-Breaking)
- Changing the enum “references” list on the booking object. Removing BookingNumber, ContractPartyReferenceNumber on suggestion from intra (Non-breaking)
- Adding a rule for the frequency of some Enums on “references” list on suggestion from Inttra (Non-Breaking)
22/06/2021 V 1.0.2
- Description added for allocations object
- Description added for equipments list
- Base URL changed
- Read only added to contact id field.
25/06/2021 V 1.0.3
- Changed the URL to /v1.0 from /v1
20/08/2021 V1.0.4
- Adding a Link header to the pagination response which contains traversing information about the next, previous, fist and last pages.
- Adding the X-Total-Count to the API which gives the total number of records for the bookings resource.
- Page size defaulted to 10 if not provided in the request.
01/12/2021 V2.0.0
- Using L.H.S for the list bookings API
25/01/2022 V2.1.0
- Adding the ability to create and use templates to speed up the booking process
12/07/2022 V2.2.0
- Adding the delete template API ability. Users can now delete old templates that are not needed.
10/08/2022 V2.3.0
- Adding the Edit template API ability. Users can now edit existing templates.
04/10/2022 V2.4.0
- Adding the Pre Carriage, Main Carriage and On Carriage ability on the Legs API
07/02/2023 V2.5.0
- New APIs release to track confirmed equipment changes. A new Non-Crud resource is now available for tracking requested v/s confirmed equipment after carrier confirmation.
21/03/2023 V2.5.1
- Bookings service now write booking confirmation notifications for Cube customers
- Bookings API error responses now have 6 digit error codes in the body to provide granular insight into errors