Hostwise Developer Documentation

Hostwise is the availability source of truth for short-term rentals. Your booking website (a brand) runs on top of Hostwise: it reads the catalogue and live availability from Hostwise, books through Hostwise, and is notified by Hostwise the moment anything changes — while Hostwise keeps every other sales channel the property is sold on consistent underneath.

The model

ConceptWhat it is
AccountOne Hostwise customer (a property manager). All data is isolated per account.
BrandOne booking website belonging to an account. An account can run several brands; each brand holds its own API keys and webhook subscriptions and sees only the listings published to it.
ListingA bookable unit (an apartment, or a room type with several identical units). Identified by a stable listingId string.
CalendarThe single availability answer, per listing and per date. Every booking, from your site or from any other sales channel, lands in the same calendar — so there is exactly one truth to read.

The one rule that shapes everything

Hostwise is the source of truth for availability. Your site mirrors it; it never owns it. Three practices follow, and every section of these docs assumes them:

A typical integration

  1. Your account manager creates your brand in Hostwise and issues API keys (see Authentication).
  2. Pull the catalogue and availability from the Storefront API into your site's own cache; refresh on a schedule.
  3. Read what the account can sell alongside a stay from the same API (/api/storefront/partners): the connected partners' services and prices. Sell those; Hostwise carries each booking to the partner.
  4. Register a webhook endpoint so changes reach you in seconds instead of on the next poll.
  5. At checkout, confirm the stay through the Gateway API — an idempotent, atomic booking that also closes the dates on every other sales channel the property is sold on.
  6. If your site takes bookings Hostwise should merely record (payment handled by you), push them via the Ingest API.
All endpoints are HTTPS on https://hostwise.fr. Requests and responses are JSON. Dates are ISO 8601 YYYY-MM-DD; a stay occupies checkin through the night before checkout — the checkout day itself is free for the next arrival.

Monitoring

GET /health is public and unauthenticated: {"status":"ok","db":"ok","version":"…"}. Point your uptime monitor at it. A non-200 or db not ok means degrade gracefully: serve from your cache, and fail closed at checkout as always.

For AI integrators

The complete documentation is also published as a single plain-text file at /docs/llms-full.txt — load it into your model's context and it carries every endpoint, field and rule on this site.