Who can reach what
Access binds to your organisation, workspace, properties, scopes, and service account rather than issuing a context-free key.
- Organisation and workspace scope
- Read/write operation scope
- Credential, rotation, and support ownership
Hotel Inventory API
AvailableAdd hotel availability and booking operations to your product.
Use Boni's Hotel Inventory API for approved property, room, dated availability, rate, hold, booking, channel, and AI-operations workflows with source-of-truth and audit boundaries defined for each implementation.
For: Travel platforms, hotel groups, booking products, concierge services, channel partners, enterprise software teams, and approved AI agents.
What the product connects
One operating record across the workflow
Inventory
Property and room-type records with capacity, pricing, policy, channel, and operator context.
Sellability
Date-level availability, restrictions, buffers, holds, booked state, and available-to-sell capacity.
Operations
Booking source, guest context, channel health, risk signals, and the operator work behind an API response.
How it works
Treat availability as an operating contract, not a static hotel feed.
Search and display can use fast projections. A hold or confirmation must resolve to the approved source of truth, carry its source and tenant context, and remain explainable to the operator supporting the booking.
- 01
Scope the integration
Agree the organisation, properties, inventory source, operations, channels, credentials, rate limits, support owner, and commercial boundary.
- 02
Map property inventory
Connect property and room identifiers, occupancy, policies, restrictions, pricing, media, and source references.
- 03
Read live sellability
Request the dated availability and commercial state relevant to the customer's stay rather than relying on an undated catalogue flag.
- 04
Create a bounded hold
Temporarily reserve the requested quantity with expiry, channel, source reference, and idempotency context.
- 05
Confirm once
Revalidate the hold and availability state, then create one canonical booking for the approved payment or confirmation outcome.
- 06
Operate the lifecycle
Propagate booking state, changes, release, cancellation or refund context, channel incidents, and support handoff according to the implementation contract.
Product scope
What the product covers.
Approved property and room-type inventory reads and writes.
Date-level hotel availability with restrictions and sellability fields.
Hotel rate views over the current inventory and date context.
TTL-based holds with channel, source, customer, quantity, and idempotency context.
Hold confirmation into a canonical booking with the related availability update.
Hotel booking, PMS-board, channel, and AI-operations views, scoped to your properties.
Organisation and workspace identifiers carried with the operational record.
Audit-friendly source references for imported or connected inventory.
A path into Bino hotel booking and Bow Chat guest operations when the rollout includes them.
Operating areas
The API contract has to cover correctness, integration operations, and the human support path.
Inventory mapping
Preserve both Boni identifiers and the approved source-system references needed to reconcile property and room records.
- Property and room keys
- Rate, policy, restriction, and channel mapping
- Import evidence and last-known source state
Booking correctness
Separate search, availability, hold, confirmation, booking, cancellation, and release so each transition can be validated.
- Idempotency and expiry
- Availability revalidation
- Conflict and stale-data behavior
Events and channel health
Design asynchronous booking and inventory changes as observable work with retries and ownership.
- Typed lifecycle events
- Delivery, retry, and failure state
- Operator-visible channel incidents
Customer and payment boundaries
Carry the references needed for support without pretending the inventory API owns every payment or guest-data decision.
- Booking and customer reference
- Payment or refund state reference
- Consent, retention, and support handoff
Operational reporting
Measure integration outcomes beyond raw request counts.
- Hold-to-confirm outcomes
- Latency, expiry, conflict, and error rates
- Channel lag and reconciliation exceptions
AI inside the operation
AI should prepare work, explain risk, and improve decisions—not invent operational truth.
Inventory onboarding
Prepare mapped property, room, restriction, and rate drafts from approved files or source exports.
Draft records remain non-sellable until reviewed.
Search explanation
Explain why a room is available, restricted, scarce, or excluded using the current structured state.
The explanation cannot override the authoritative sellability response.
Channel incident triage
Summarize failed syncs, stale data, affected dates, and the safest next action for the operator.
Retries and stop-sell actions follow policy and audit.
Booking support context
Prepare a guest or agent reply using the real booking, policy, payment-reference, and channel state.
The model must not invent a confirmation or refund.
Rate review
Return a recommendation with evidence and constraints to an operator workflow.
The API does not silently publish AI-generated prices.
Reconciliation review
Surface mismatches between inventory, bookings, external source references, payments, and channel events.
Exceptions go to an accountable owner before corrective action.
Implementation paths
Start where the operating gap is real.
Embed a booking journey
Use approved hotel inventory inside a travel, concierge, employee-benefit, or marketplace product with a defined booking and support path.
Connect an operator system
Synchronise a bounded inventory or reservation lane with an existing PMS, channel tool, or hotel data source.
Power an AI workflow
Give an approved agent safe read, search, draft, and policy-bound action access over actual reservation 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.
Access you control
Every integration is provisioned to a named product, organisation, inventory scope, and workflow — never an unrestricted public feed.
Built to your operation
Inventory, availability, holds, bookings, hotel views, and AI signals come as standard. Connectors, webhooks, cancellation, refund, and settlement behaviour are shaped to the rules your property already runs on.
No stale confirmation
A search result is not a booking guarantee. Confirmation must revalidate the authoritative hold and availability state.
No raw protocol resale
Boni sells a supported product and operating integration, not access to an upstream network credential or an unexplained provider payload.
Connected products
Use it alone, or connect the next part of the operation.
Boni Hotel OS
Give operators the workspace that owns inventory, guest operations, channel exceptions, and review work behind the API.
Explore Hotel OSBino hotel booking
Use approved inventory in a customer-facing search and booking journey with a clear support and fulfilment owner.
See Bino bookingBow Chat hospitality operations
Connect guest conversations, calls, changes, reminders, and escalation to the booking record.
Explore guest operationsQuestions
Common questions
How do we get access to the hotel API?
Scope it with us and we provision it. Access is granted to your organisation, workspace, properties, operations, and commercial use case — so your inventory and holds stay under your control rather than sitting on an open feed.
What can an approved integration do?
The working foundation supports hotel properties, room inventory, date-level availability, rates, holds, confirmation into bookings, channel views, and AI-operations signals. Cancellation, refund, settlement, webhooks, connector depth, and external-channel rules are defined per implementation.
How do you prevent duplicate bookings?
Mutating integrations use an idempotency and source-reference model, and booking confirmation revalidates the relevant availability state. The production design also requires explicit ownership and concurrency rules for every connected channel.
Can an AI agent call the API directly?
An approved agent can receive narrowly scoped access, but high-impact actions remain governed. AI may search, prepare, explain, or propose; booking, price, payment, refund, cancellation, and channel actions must follow the customer's policy and audit requirements.
Start with one bounded workflow