Boni

Bus Inventory API

Build around the real departure, seat and ticket.

Connect your product to company-scoped bus routes, departures, real seats, fares, holds, tickets and boarding. Use the same reservation record as the operator counter.

For: Bus operators, booking products, travel-platform teams and approved integration partners.

Bus Inventory API: operating workflow
  1. 01Agree the scope
  2. 02Review the departure
  3. 03Hold selected seats
  4. 04Confirm once

Shared context · Clear responsibility · Review where it matters

One reservation record
The operator counter and API use the same trips, seats, holds and bookings.
Explicit access
Scope each integration to its company, inventory and permitted operations.
Recover the original
Keep command, hold and booking references so a lost reply does not become a second sale.

How it works

Search, hold, confirm and operate the original ticket.

Agree the inventory authority, commercial workflow and support responsibility before connecting a new selling channel.

  1. 01

    Agree the scope

    Name the operator, company, routes, allowed actions, credentials and support responsibility.

  2. 02

    Review the departure

    Read the dated trip, schedule, physical seat map and its current version.

  3. 03

    Hold selected seats

    Submit the actual seat identities and passenger context with the original request reference and expiry.

  4. 04

    Confirm once

    Confirm the original accepted hold. If the reply is uncertain, read its result before creating any new action.

  5. 05

    Operate the ticket

    Look up the booking, use the confirmed passenger list and record per-seat boarding through permitted operations.

  6. 06

    Handle cancellation

    Review eligible seats, retain the cancellation reference and follow the configured financial refund state separately.

Product scope

What the product covers.

Company-scoped bus route and dated-departure reads and configuration.

Versioned physical seat maps and frozen per-seat booking fares.

Temporary selected-seat holds and booking confirmation.

Original command, hold and booking recovery.

Confirmed passenger manifests and per-seat boarding.

Eligible partial cancellation and explicit refund-review state.

Fleet records and reviewed, seat-compatible departure assignment.

Actor-linked command receipts and reference-only dispatch history.

Operating areas

Keep correctness in the integration, not just in the screen.

Company and action scope

A permitted screen does not grant every API action.

  • Named company and resource scope
  • Separate read, configure, book, board and cancel rights
  • Current permission checks

Seat ownership

Use the departure's actual reviewed layout.

  • Selected seat identities
  • Seat-map and fare snapshots
  • Whole-route allocation

Unknown results

Preserve a recoverable original when transport fails.

  • Original command identity
  • Read current result
  • No blind fresh-request retry

Financial handoff

Keep the reservation and money states distinct.

  • Ticket and cancellation references
  • Configured collection/refund workflow
  • Separate invoices and settlement

Implementation paths

Choose the setup that fits your team.

A booking product

Embed approved operator inventory with a named support and fulfilment responsibility.

An existing operator system

Agree mapping and which system owns each route, trip, fare, seat and booking before switching a defined scope.

Wider distribution

Connect approved channels per implementation. Partner access and financial arrangements remain part of the agreed integration.

Built around your business operations.

Connect the right people, records and systems around your workflow, with clear ownership and the controls your team needs.

No stale confirmation

A search result is not a reservation. Confirmation depends on the original accepted hold and current reservation state.

No shared credential shortcut

Use credentials and actions issued for the agreed operator scope, never another operator's identity or an upstream provider secret.

Policy-controlled actions

Booking, cancellation and financial changes remain policy-controlled and auditable. An assistant must not invent trip, seat or refund facts.

Questions

Common questions

What can a bus reservation integration do?

Read and configure approved routes, departures and seat maps; create temporary holds; confirm bookings; find original tickets; and use scoped boarding and cancellation operations. Access is limited to the agreed company, inventory and actions.

Does the API support seat-level booking?

Yes. A departure has reviewed physical seats and a seat-map version. A booking records the selected seats and fare snapshot. The current reservation model allocates seats for the whole route; stop-to-stop seat sharing needs a separately agreed operating model.

Can I confirm from an old search result?

No. Search is time-sensitive and does not reserve a seat. Create a hold against the current departure and seat-map version, then confirm that original hold before it expires.

What happens when the booking reply is interrupted?

Retain the original command and hold references. Read their current result before retrying. A fresh identifier can represent another sale, so it must not replace an uncertain original action.

Does cancellation prove a refund?

No. Inventory cancellation and financial refund are separate states. Read the actual financial result from the configured payment and accounting workflow before reporting a completed refund.

Does API access include an online travel agent account?

No. Each external channel requires its own approved access, inventory mapping, commercial arrangement and support responsibility. API access is not an unrestricted feed of other operators' inventory.

See it working for your business

Bring your process, files and team. See the workflow configured around your business.

Discuss API access