⇣ POST /booking

An existing booking can be updated by the agent, for example to add or remove the number of tickets, or change the customer details / travel date.

If the poduct has freesale = false; to be able to update the travel date, number of tickets or the product/option/time slot, the agent must have made a reservation request, which will be provided in this request as reservation.

The /booking_update request will be made as a POST request to your callback_url for example: POST https://api.example.com/cc/callbacks/booking_update.

{
  "booking": "BOOKING00004232",
  "reservation": "RESERVATION00004215",
  "agent": "viator.com",
  "date": "2017-10-08",
  "time_slot": "11:00",
  "pickup": "City Sightseeing Tour Office & Travel Depot",
  "adult": 3,
	"child": 1
}

The parameters are identical to the /booking_confirmation callback, except for the initial request which will contain a booking field which is equal to the reference you returned in the original booking confirmation.

Your response to this should be a HTTP 200 OK response, and the body should be identical to the booking confirmation response.

Note it must contain ALL the tickets and barcodes, even if no changes were made to the tickets. You may change the barcodes and booking reference if you chose to.

{
  "mobile": true,
  "reference": "BOOKING00004232",
  "barcode": "128465552",
  "tickets": [
    { "type": "adult", "barcode": "7485936482" },
    { "type": "adult", "barcode": "2512356846" },
    { "type": "adult", "barcode": "1212482144" },
    { "type": "child", "barcode": "9257377533" }
  ]
}

City Connect will not allow an agent to update a booking either:

On or after the travel date
If one or more of the tickets have been redeemed already

There should be no reason for you not to accept the booking update request for any other reason, so City Connect will except a successful response for every booking update request.