Bus API integration
Bus API integration for Indian and international routes
Bus API integration connects your travel portal to bus operators and aggregators so customers and agents can search routes, pick seats, choose boarding points and pay, with tickets confirmed in real time. We integrate bus APIs for B2B and B2C travel portals, mainly for Indian intercity routes where bus ticketing is a core agent product, and for international operators where coverage exists.
Request a quote for bus API integration
What bus API integration covers
Bus API integration is the work of connecting a bus ticketing API, from an aggregator or an operator, into your booking platform so the full flow runs without manual steps. It is one of the modules within our travel API integration services and is usually added to a portal that already sells flights or hotels. A complete integration handles these calls:
- Cities and routes: source and destination lists, route availability by date, and the operators running each route
- Operator details: bus type (seater, sleeper, AC, non-AC), amenities, operator rating where provided, and cancellation policy
- Seat maps: live seat layout with availability, gender-reserved seats, lower and upper deck, and per-seat fares
- Boarding and dropping points: point names, landmarks, times and contact numbers for the chosen trip
- Fare check: a block or re-quote call before payment so the price and seat are held for the payment window
- Booking: passenger details, ticket confirmation, operator PNR and ticket number returned and stored
- Cancellation: policy lookup, refund calculation by time before departure, and the cancellation call with refund status
- Webhooks and status: operator-side cancellations, schedule changes and refund settlements pushed to your system rather than polled
The calls look simple on paper. The difficulty is in the details: seat holds that expire mid-payment, operators that cancel trips at short notice, and refund rules that differ by operator and by hours before departure. A good integration handles each of these without a support ticket.
India focus, with international options
In India, bus ticketing is a volume product for travel agents, especially outside the metro cities, where a large share of intercity travel still happens by bus. For a B2B portal serving sub-agents, bus is often the add-on that gets agents logging in daily, even if flights earn more per booking. Indian bus aggregator APIs give access to thousands of private operators and, in several states, to state transport corporations as well, through a single connection. We have integration experience with the Indian bus aggregator APIs that agent portals commonly use and can work with whichever provider you have signed. [TO CONFIRM: specific bus API providers you want named]
Outside India, bus coverage is fragmented. Some markets have a dominant aggregator; others require direct operator integrations. For agencies in the US, UK and Canada that want intercity coach options, we scope the available APIs for your target routes before quoting, rather than promising coverage that does not exist.
What we deliver
Search and results
City auto-complete, date picker, results with operator, departure and arrival times, duration, bus type, fare range and seats left, with filters for time of day, bus type and boarding point.
Interactive seat layout
Rendered from the API seat map with deck, berth and gender rules applied, showing the fare for each seat, on desktop and mobile.
Payment and confirmation
Payment gateway or agent wallet deduction, ticket confirmation, SMS and email ticket with boarding point details, and a PDF ticket in your branding.
Admin and markups
Markup rules by operator, route or agent tier, booking list with cancellation controls, refund tracking and supplier reconciliation reports.
Failure handling
Timeouts, seat-hold expiry, payment-success-but-booking-failed cases and operator cancellations all handled with defined outcomes, refunds and notifications.
Monitoring
API health checks, error-rate alerts and logs for every supplier call so disputes with operators can be resolved from records.
Where bus API integration plugs in
| Platform | How bus is added | Notes |
|---|---|---|
| B2B travel portal | As a module beside flights and hotels, sharing agent login, wallet, credit and markup tiers. | The most common request from Indian consolidators; see B2B travel portal development |
| B2C travel website | Public bus search with gateway payment and self-service cancellation. | Works with an existing travel website or a new build |
| White label portal | Enabled as an extra product in a white label travel portal. | Fastest path when you do not need a custom flow |
| Mobile app | Same API powering a white label travel app on iOS and Android. | Seat map is built to work on small screens |
Process and timeline
Scope
Confirm your bus API provider, target markets, platform (B2B, B2C or both) and markup rules. Written scope and fixed quote follow.
Sandbox integration
Connect to the provider test environment, build search, seat map, boarding points, fare check, booking and cancellation.
Failure testing
Simulate expired holds, failed payments, operator cancellations and refund flows before anything goes live.
Production and support
Switch to live credentials, monitor the first bookings with you, then hand over with a support plan for API changes.
Bus integrations are usually quicker than flight or hotel work because the data model is smaller, provided the provider sandbox is stable and credentials arrive promptly. [TO CONFIRM: typical delivery window to state publicly]
Pricing approach
Fixed quote per provider integration, with a lower rate when bus is added to a portal we have already built. Ongoing support is a monthly plan covering provider API changes and monitoring. [TO CONFIRM: whether to publish starting prices]
Frequently asked questions
What is bus API integration?
Bus API integration connects your website or portal to a bus ticketing API so users can search routes, see operators and live seat maps, choose boarding and dropping points, pay and receive a confirmed ticket. It also covers cancellations, refunds and webhooks for operator-side changes, with an admin panel for markups and bookings.
Which bus APIs can be integrated?
Any aggregator or operator API that exposes search, seat map, block, book and cancel endpoints. In India this usually means one of the established bus aggregator APIs that give access to private operators and several state transport corporations. For other countries we check available providers for your target routes before quoting. [TO CONFIRM: providers to list by name]
Can bus ticketing be added to my existing B2B portal?
Yes. Bus is added as a module that reuses your existing agent login, wallet or credit limit, markup tiers and reporting. If your portal was built by someone else we review the codebase first to confirm how the module can be attached, then quote on that basis.
How are cancellations and refunds handled?
The integration reads the operator cancellation policy for the ticket, calculates the refund based on hours before departure, sends the cancellation call and records the result. Refund to the customer or agent wallet is triggered from the confirmed response, and operator-initiated cancellations arrive by webhook so your team is alerted rather than finding out from the passenger.
Does the seat map work on mobile?
Yes. The seat layout is rendered from the API data rather than as a fixed image, so it adapts to phone screens, supports upper and lower decks and sleeper berths, and applies gender-reserved seat rules. The same component is used in the web portal and in a white label mobile app.
Related pages
Add bus ticketing to your travel portal
Tell us your bus API provider and platform. You will receive a written scope and fixed quote within two business days.