Introduction

As a supplier, you will be queried for availability, reservations and bookings for your products. This section explains in detail the different callbacks and how to implement them.

On your account you will have set a callback_url this will act as the base URL for all callbacks documented in this section. For example if you set this value to https://example.com/callbacks then an availability callback will call the URL https://example.com/callbacks/availability

City Connect will make an HTTP request to these endpoints on your server when they are requested by an agent. You must ensure your service uptime and that you follow the spec otherwise bookings will fail on the agent side.

Below is a table of the different callbacks that your system should implement:

Callback	Description
GET /products	Gets all products from your system.
GET /availability	Look up availability on your system
POST /reservation	Reserve an allocation of tickets for a given date and product/option/tour (not for freesale products)
POST /reservation_cancellation	Cancel a reservation and release the tickets back out into the wild. (not for freesale products)
POST /booking_confirmation	Confirms a booking with a reservation, or not (if its a freesale product), and returns barcodes for the tickets.
POST /booking_update	Updates an existing booking.
POST /booking_cancellation	Cancels a confirmed booking.
Booking Notifications	Whenever a successful booking completes, you will be sent a notification.
Ticket Redemption Request	When you receive the booking sent by the agent, you must redeem or scan it, using this method.