Booking Lifecycle

Steps

Step	What happens	Who
Book	You call the Book API. The seats are blocked and a provisional booking is created, with a `booking_code`.	You, TravClan API
Send details to your ACM	You send the traveller details and documents to your ACM (account manager), quoting the same `buyer_booking_reference`.	You, ACM
Confirmation	TravClan confirms the booking in its system.	ACM, TravClan
Final booking code	TravClan sends the final booking code to your webhook (an endpoint you provide), with your `buyer_booking_reference` so you can match it to your booking.	TravClan

📘
Keep your reference unique
buyer_booking_reference links every step together: the Book request, your details to the ACM, and the final booking code. Use a new, unique value for every booking.

Booking Statuses

The Book API response has two statuses:

Field	Value after Book	Meaning
`status`	`CONFIRMED`	The booking is accepted and the seats are blocked. Show "Booking received".
`internal_booking_status`	`PENDING`	TravClan has not confirmed the booking yet. It stays pending until step 3.

The booking_code from the Book API is the provisional booking code. The final booking code from step 4 is a different code.

Seats

Seats are blocked as soon as the Book API returns 200, and total_available on the departure drops straight away. Seats count adults and children; infants do not take a seat. A failed Book call blocks no seats.

If Something Fails

When	What happens	What to do
At step 1	The Book API returns an error. No booking is made and no seats are blocked.	Fix the request, or on a `409` recalculate with the current price, and call Book again.
After step 1	The booking exists and its seats are blocked.	Contact your ACM, quoting the `buyer_booking_reference`.

Cancellations

Cancellations are made offline; there is no cancellation API. To cancel a booking, contact your ACM with the buyer_booking_reference and the booking code. Cancellation charges follow the package's cancellation_policy.