Hotel Inventory API
Pilot APIUse 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
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.
Agree the organisation, properties, inventory source, operations, channels, credentials, rate limits, support owner, and commercial boundary.
Connect property and room identifiers, occupancy, policies, restrictions, pricing, media, and source references.
Request the dated availability and commercial state relevant to the customer's stay rather than relying on an undated catalogue flag.
Temporarily reserve the requested quantity with expiry, channel, source reference, and idempotency context.
Revalidate the hold and availability state, then create one canonical booking for the approved payment or confirmation outcome.
Propagate booking state, changes, release, cancellation or refund context, channel incidents, and support handoff according to the implementation contract.
Product scope
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 for authorised integrations.
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
Bind access to the authorised organisation, workspace, properties, scopes, and service account rather than issuing a context-free key.
Preserve both Boni identifiers and the approved source-system references needed to reconcile property and room records.
Separate search, availability, hold, confirmation, booking, cancellation, and release so each transition can be validated.
Design asynchronous booking and inventory changes as observable work with retries and ownership.
Carry the references needed for support without pretending the inventory API owns every payment or guest-data decision.
Measure integration outcomes beyond raw request counts.
AI inside the operation
Prepare mapped property, room, restriction, and rate drafts from approved files or source exports.
Draft records remain non-sellable until reviewed.
Explain why a room is available, restricted, scarce, or excluded using the current structured state.
The explanation cannot override the authoritative sellability response.
Summarize failed syncs, stale data, affected dates, and the safest next action for the operator.
Retries and stop-sell actions follow policy and audit.
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.
Return a recommendation with evidence and constraints to an operator workflow.
The API does not silently publish AI-generated prices.
Surface mismatches between inventory, bookings, external source references, payments, and channel events.
Exceptions go to an accountable owner before corrective action.
Implementation paths
Use approved hotel inventory inside a travel, concierge, employee-benefit, or marketplace product with a defined booking and support path.
Synchronise a bounded inventory or reservation lane with an existing PMS, channel tool, or hotel data source.
Give an approved agent safe read, search, draft, and policy-bound action access over actual reservation state.
Each rollout names the workflow, participants, source records, owner, success measures, and the parts that remain in existing systems.
API access is approved for a named product, tenant, inventory scope, and workflow. It is not an unrestricted public feed.
The working V0 covers core inventory, availability, holds, bookings, hotel views, and AI signals. Full connector, webhook, cancellation, refund, and settlement depth is implementation-specific.
A search result is not a booking guarantee. Confirmation must revalidate the authoritative hold and availability state.
Boni sells a supported product and operating integration, not access to an upstream network credential or an unexplained provider payload.
Connected products
Give operators the workspace that owns inventory, guest operations, channel exceptions, and review work behind the API.
Explore Hotel OSUse approved inventory in a customer-facing search and booking journey with a clear support and fulfilment owner.
See Bino bookingConnect guest conversations, calls, changes, reminders, and escalation to the booking record.
Explore guest operationsQuestions
Not yet. The current API is available through controlled implementations. Access is scoped to the approved organisation, workspace, properties, operations, and commercial use case.
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 pilot as they mature.
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.
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
