Identity and access
Bind credentials to an approved organisation, operator, workspace, routes, actions, and partner role.
- Operator and organisation scope
- Read/write operation scope
- Credential, rotation, rate-limit, and support ownership
Bus Inventory API
Pilot APIAdd routes, trips, availability, and booking operations to your product.
Use Boni's Bus Inventory API for approved route, trip, capacity, fare, hold, booking, channel, manifest, and AI-operations workflows with operator ownership and booking correctness built into the implementation.
For: Bus operators, travel platforms, corporate transport products, agent networks, channel partners, enterprise software teams, and approved AI agents.
What the product connects
One operating record across the workflow
Network
Operator, route, stop, trip, vehicle or capacity, seat-map, fare, and sales-channel context.
Sellability
Time-bound availability, held and booked state, buffers, source references, and confirmation rules.
Operations
Booking, agent, manifest, channel health, risk signals, and operator review behind the API response.
How it works
Design the booking API around a real departure and accountable operator.
A route listing is only the start. The integration needs live trip context, bounded holds, confirmation rules, lifecycle events, passenger support, and a clear operating owner when something changes.
- 01
Scope the operator
Agree the organisation, routes, trips, inventory authority, operations, partner role, credentials, rate limits, and support responsibility.
- 02
Map the network
Connect route, stop, timing, trip, vehicle or capacity, seat layout, fare, policy, and source identifiers.
- 03
Read trip sellability
Request the dated departure and commercial state relevant to the passenger's exact journey.
- 04
Create a hold
Temporarily reserve the approved quantity or seat context with expiry, source, channel, customer, and idempotency information.
- 05
Confirm once
Revalidate the hold and trip inventory, then write one canonical booking for the approved commercial outcome.
- 06
Operate changes
Propagate manifest, boarding, change, cancellation, release, refund context, channel failure, and passenger handoff according to the contract.
Product scope
What the product covers.
Approved bus route and trip inventory reads and writes.
Bus-specific seat-map, fare, agent, manifest, channel, booking, hold, and AI-operations views.
Time-bound trip capacity with available, held, booked, safety-buffer, and available-to-sell state.
TTL-based holds with customer, quantity, channel, source, and idempotency context.
Hold confirmation into one booking with the related trip-availability update.
Organisation and workspace identifiers carried with the operational record.
Source references for imported schedules, operator systems, channels, or partner requests.
A path into Bino travel journeys and Bow Chat passenger operations when the rollout includes them.
Operator review context for channel health, scarce capacity, risk reasons, and next actions.
Operating areas
A useful bus API connects the product request to trip truth, operator work, and passenger support.
Network mapping
Preserve the identifiers and structure required to reconcile a product request with the operator network.
- Routes, stops, legs, and timings
- Trips, vehicles or capacity, and seat maps
- Fares, policies, channels, and source references
Booking correctness
Separate search, sellability, hold, confirmation, booking, cancellation, and release.
- Expiry and idempotency
- Trip-inventory revalidation
- Conflict and stale-data behavior
Events and channel health
Treat partner and operator changes as observable lifecycle work rather than silent synchronisation.
- Typed booking and inventory events
- Delivery, retry, replay, and failure state
- Operator-visible channel exceptions
Passenger operations
Carry the references needed for reminders, support, disruption, manifest, and boarding workflows.
- Passenger and booking reference
- Pickup, timing, manifest, and service context
- Support, change, cancellation, and refund handoff
Commercial reporting
Measure integration quality and operator outcomes beyond request volume.
- Hold-to-confirm outcomes
- Latency, expiry, conflict, and error rates
- Channel lag, agent state, and settlement exceptions
AI inside the operation
AI should prepare work, explain risk, and improve decisions—not invent operational truth.
Schedule onboarding
Prepare mapped routes, stops, trips, seat charts, fares, and policies from approved operator files or exports.
Draft records stay out of sale until reviewed.
Sellability explanation
Explain current availability, restriction, scarcity, or exclusion using structured trip state.
The explanation cannot override the authoritative response.
Channel incident triage
Summarize a failed sync, affected departures, passenger risk, and the safest next action.
Retry, stop-sell, and inventory actions follow explicit policy.
Passenger support context
Prepare an answer using the actual booking, trip, pickup, policy, and payment-reference state.
The model cannot invent a ticket, seat, timing, or refund.
Fare review
Return a recommendation with evidence, capacity context, and operator constraints.
AI-generated fares are not silently published.
Exception review
Surface mismatches across trip inventory, bookings, agent records, external sources, payment references, and channel events.
Corrective actions go through an accountable owner.
Implementation paths
Start where the operating gap is real.
Embed a travel journey
Use approved operator inventory inside a travel, corporate transport, concierge, or marketplace product with defined support and fulfilment.
Connect an operator system
Synchronise a bounded route, trip, agent, direct-channel, or distribution lane with the operator's current tools.
Power an AI workflow
Give an approved agent safe read, search, draft, and policy-bound action access over real trip and booking state.
Start with a defined operating scope.
Each rollout names the workflow, participants, source records, owner, success measures, and the parts that remain in existing systems.
Controlled provisioning
Access is approved for a named operator, product, tenant, inventory scope, and workflow. It is not a context-free public feed.
Current versus planned depth
The V0 covers the reservation foundation and bus-specific views. Exact seat-leg logic, mature external connectors, refunds, settlement, and webhooks remain implementation-specific.
No stale confirmation
A search response does not reserve a seat. Confirmation must revalidate the authoritative hold and trip state.
No raw protocol resale
Boni provides a supported product and operator integration, not access to upstream credentials or an unexplained provider payload.
Connected products
Use it alone, or connect the next part of the operation.
Boni Bus OS
Give operators the workspace that owns routes, trips, agents, manifests, channels, exceptions, and review work behind the API.
Explore Bus OSBino Travel
Use approved inventory in customer-facing travel discovery and booking journeys with a named support owner.
Explore Bino travelBow Chat
Connect passenger conversations, calls, changes, reminders, disruption, and escalation to booking context.
Explore Bow ChatQuestions
Common questions
Is the Bus Inventory API self-serve?
Not yet. Access is provisioned for controlled pilots and approved integrations with a named operator, organisation, route or inventory scope, credential policy, support owner, and commercial agreement.
Does the API expose seat-level inventory?
The current V0 exposes bus-specific route, trip, seat-map, fare, hold, booking, channel, agent, manifest, and AI-operations views over a working capacity ledger. Exact seat-level, route-leg, quota, and connector behavior must be verified and contracted for the implementation rather than assumed from a generic endpoint name.
Can a partner confirm a booking from an old search result?
No. Search or availability responses are time-sensitive. The approved flow creates a bounded hold and revalidates the authoritative trip inventory before confirmation.
Can AI change fares or cancel trips?
AI can prepare, explain, recommend, and route exceptions. Fare publication, booking confirmation, trip cancellation, refund, settlement, and passenger-impacting actions remain policy-controlled and auditable.
Start with one bounded workflow