Bus travel is one of the largest travel segments in India, and many travel portals add bus booking through an API from an aggregator or operator platform. Bus content looks simple, but it has details that do not exist in flights or hotels: visual seat maps, sleeper berths, dozens of boarding points and cancellation rules that differ by operator. Getting these right is what makes a bus booking flow work. This article explains each part.
Search and results
A bus search uses source city, destination city and travel date. Results show operators, departure and arrival times, bus type (AC or non-AC, seater, sleeper or semi-sleeper), duration, starting fare, available seats and ratings where provided. Filters for bus type, departure time, operator and price help travellers narrow down long lists on busy routes.
Seat layouts
Bus travellers choose specific seats, so the seat map is the heart of the booking flow:
- Render lower and upper decks for sleeper buses.
- Show seat types: seater, sleeper, single and double berths.
- Mark booked, available and ladies-reserved seats clearly.
- Show seat-wise prices, because seats on the same bus can have different fares.
Seat layout data from the API must be translated into a clear, touch-friendly map, especially on mobile.
Boarding and dropping points
A single bus may stop at many points in a city. The traveller chooses a boarding point with its time and address, and a dropping point at the destination. Showing landmarks and contact numbers for each point reduces missed buses and support calls.
Seat blocking and ticketing
- When the traveller selects seats and enters passenger details, the system blocks the seats through the API for a short time.
- Payment is collected during this window.
- After payment, the system confirms the booking and receives a ticket number or PNR.
- The ticket is sent by email and SMS, often with the operator's contact number.
If payment fails or times out, the block expires and the seats return to inventory.
Cancellation rules
Each operator sets its own cancellation policy, usually with refund percentages that depend on how many hours before departure the ticket is cancelled. The integration should display the policy before booking, calculate the refund when the traveller cancels and process the cancellation through the API. Some tickets are non-cancellable, which must be clearly shown.
Pricing and markups
- Apply markups or discounts by operator, route or channel.
- Show taxes and service fees transparently.
- Offer agent rates in a B2B portal, with commission where the supplier provides it.
Handling multiple suppliers
Larger portals connect more than one bus API to improve coverage. The same bus can appear from two sources, so the engine needs to detect duplicates by operator, departure time and route, and show the better option.
In practice: reducing failed bookings
A portal noticed that some bus bookings failed after payment because the seat block expired while travellers were on the bank's payment page. It extended the block time where the API allowed, showed a countdown on the payment step and added automatic refunds for any payment received after a block expired. Failed bookings dropped sharply, and travellers trusted the site more.
Common mistakes
- Seat maps that are hard to use on small screens.
- Not showing boarding point times and landmarks.
- Hiding operator cancellation policies until after booking.
Frequently asked questions
Can agents book buses in a B2B portal?
Yes. Bus booking works well in B2B portals with wallets and agent markups, alongside flights and hotels.
Can we add our own buses?
Yes. A bus extranet lets operators load their own routes and seats, which appear alongside API inventory.
Key takeaways
- Clear seat maps and boarding points are essential for bus bookings.
- Seat blocking and payment timing must be handled carefully.
- Show operator-specific cancellation rules before booking.
Add bus booking to your portal through our bus API integration services, including redBus and Bitla.
