Hospitable API
Hospitable exposes a REST Public API (v2) at public.api.hospitable.com covering properties, calendar, reservations, messaging, reviews and webhooks, authenticated with OAuth2 for approved vendors or a personal access token for your own account, on paid plans.
Written from running this integration in production. Last checked against the Hospitable API on 11 November 2026.
Hospitable API report card
From Hospitable's own documentation. Checked on 11 November 2026.
- Base URL / API style
https://public.api.hospitable.com/v2. REST, JSON, version in the path, related resources through?include=. source- Auth
- OAuth2 authorization code for approved vendors (access token 12 h, refresh token 90 days), or a personal access token for your own account (1 year, read or write, optional IP allowlist). source
- Rate limits
- Per endpoint, not global. Examples: calendar reads 1,000 / min; a reservation’s messages 2 reads / min per reservation; sending 2 / min per reservation and 50 / 5 min. Counted per vendor client, or per account for personal tokens. source
- Webhooks
- Reservation created and changed (with
triggers), property, message, review, integration disconnected, owner statements. HMAC-SHA256Signatureheader. Up to 5 retries (1 s, 5 s, 10 s, 1 h, 6 h). Sent from 38.80.170.0/24. source - Read / write coverage
- Read properties, reservations, inquiries, messages, reviews, payouts, transactions and owner statements. Write the calendar, manual reservations, messages, review responses, tasks and owner-statement items. source
- Guest messaging
- Send on a reservation or inquiry thread, with up to 3 images, optionally as an Airbnb co-host. 2 messages a minute per reservation, 50 every 5 minutes. source
- Sandbox / test account
- Not documented.
- Partner / marketplace programme
- Approved-vendor application, then the Partner Portal for OAuth clients, webhook URLs and logs. A Marketplace listing requires OAuth. Connect is a separate partner API. source
- Restrictions worth knowing
- No API access on the Essentials plan. Personal access tokens are meant for your own account; Hospitable does not recommend storing other users’ tokens and asks integrations built for other hosts to use OAuth. source
What the Hospitable API is
Hospitable’s Public API v2 is a JSON REST API at https://public.api.hospitable.com/v2 (not api.hospitable.com). It covers properties, the calendar (prices, availability, minimum stay, check-in and check-out restrictions), reservations and inquiries, guest messages, reviews, tasks, smart locks, owner statements, payouts and transactions. Related data comes back through ?include=.
There are two ways in. A host on a paid plan creates a personal access token for their own account. A company building for other hosts applies to become an approved vendor and uses OAuth2; Hospitable’s Marketplace requires OAuth. Hospitable also runs Connect, a separate partner API, and an MCP server for AI agents.
Bookings that came from Airbnb, Vrbo, Booking.com or Hospitable’s own direct booking site are mostly read-only through the API: only manual reservations can be created, fully changed and cancelled.
How to get Hospitable API access
- 1.Check the plan. API access is not available on Essentials; the Host, Professional and Mogul plans include it.
- 2.Sign in as the account owner or a full-access admin and open Apps → API access (or Settings → Integrations), then the Access tokens tab, then + Add new.
- 3.Name the token and choose read or write. Write is what calendar and reservation changes need. The token lasts one year, and you can restrict it to up to 20 IP addresses or ranges.
- 4.Call the API with
Authorization: Bearer <token>againsthttps://public.api.hospitable.com/v2.
Building for other hosts? Hospitable asks you to use OAuth rather than collect personal tokens. Apply through its vendor form; once approved you get the Partner Portal, OAuth client credentials and one webhook URL for all your customers. Access tokens last 12 hours and refresh tokens 90 days, so a connection that sits idle has to be refreshed on a schedule or the host reconnects.
What will bite you
From running this integration in production and reading the vendor's documentation line by line.
Reservations need a property list and a date window
GET /reservations requires properties[]. Without start_date and end_date (or booked_at) it returns only check-ins in the next two weeks, which looks like a complete answer. There is no updated-since filter, so an incremental sync re-reads a window of stays to catch changes and cancellations.
Reading messages is two requests a minute per reservation
GET /reservations/{uuid}/messages is limited to 2 requests a minute per reservation. Sending is 2 a minute per reservation and 50 every five minutes. A history backfill across many bookings has to be paced, and the message webhook does not carry messages older than 12 hours.
Tokens expire, all of them
A personal access token lasts one year, then every call fails until the host makes a new one. OAuth access tokens last 12 hours and refresh tokens 90 days. After a refresh the old refresh token can stay valid for up to 60 minutes, and Hospitable asks you to keep it as a fallback. Tokens are around 1,200 characters, so check your column width.
Only manual reservations are writable
Create, full update and cancel work on manual reservations only. A full update must resend check-in, check-out, adults, guest name and email, language and financials. A vendor token can only change bookings it created, and once the host edits one in Hospitable every vendor update answers 409.
Money is in minor units, dates are local
Amounts are integers in the currency’s minor unit: 45050 is 450.50 USD, and currencies such as JPY have no minor unit. arrival_date and departure_date are property-local timestamps with an offset; take the date part rather than converting to UTC.
Calendar writes land later
PUT /properties/{uuid}/calendar accepts dates up to three years ahead and processes the change asynchronously, so a read straight after a write can still show the old value.
What it costs to keep working
Hospitable’s API is broad and well documented. The ongoing cost is in token lifetimes and per-reservation limits.
- •Token refresh on a schedule: one-year personal tokens, 12-hour access tokens, 90-day refresh tokens with a short grace period after rotation.
- •Pacing message reads and sends per reservation and per account, and queueing what does not fit.
- •Webhook verification: an HMAC-SHA256
Signatureheader. Vendors get the secret in the Partner Portal; for a host’s own account it is the primary user’s email address in base64. - •Reservation sync by date window, because there is no changed-since filter.
- •Plan changes: a host who moves to Essentials loses API access, which shows up as failed calls on your side.
The same job, both ways
Hospitable directly
# Reservations need properties[] and a date window,
# or you only get check-ins in the next two weeks.
curl -s -G 'https://public.api.hospitable.com/v2/reservations' \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Accept: application/json' \
--data-urlencode 'properties[]=PROPERTY_UUID' \
--data-urlencode 'start_date=2026-01-01' \
--data-urlencode 'end_date=2027-12-31' \
--data-urlencode 'include=guest,financials' \
--data-urlencode 'per_page=100'
# Reply to the guest. Two messages a minute per reservation.
curl -s -X POST 'https://public.api.hospitable.com/v2/reservations/RESERVATION_UUID/messages' \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"body": "Your door code is ready."}'Through Repull
# Connect once with the host's access token.
curl -s -X POST 'https://api.repull.dev/v1/connect/hospitable/credentials' \
-H 'Authorization: Bearer sk_live_YOUR_KEY' \
-H 'Content-Type: application/json' \
-d '{"credentials": {"accessToken": "YOUR_ACCESS_TOKEN"}}'
# Every reservation, every property, one call. No window to remember.
curl -s 'https://api.repull.dev/v1/reservations?limit=100' \
-H 'Authorization: Bearer sk_live_YOUR_KEY'
# Reply on the conversation.
curl -s -X POST 'https://api.repull.dev/v1/conversations/CONVERSATION_ID/messages' \
-H 'Authorization: Bearer sk_live_YOUR_KEY' \
-H 'Content-Type: application/json' \
-d '{"message": "Your door code is ready."}'Why use Repull for Hospitable
Your next client will not be on Hospitable
If you run your own Hospitable account and that is all you will ever connect, use the Public API directly with a personal access token. Repull would be a layer you do not need. If you are building for other hosts and only for Hospitable, apply to be a vendor: its Marketplace requires the OAuth flow.
One reservation shape across every system
A Hospitable reservation comes back from GET /v1/reservations with the same fields as one from Hostaway, Guesty or Cloudbeds. Amounts are in major units and dates are plain dates, whatever the source sent.
Hospitable’s write rules, checked before the call
Changing or cancelling an Airbnb, Vrbo or Booking.com booking, a group booking or a specific unit is refused with 422 pms_write_unsupported naming Hospitable before anything is sent. Manual bookings can be created, quoted, changed and cancelled through POST /v1/reservations and PATCH /v1/reservations/{id}.
Every system authenticates differently
Hospitable tokens expire after 12 hours or a year. Hostaway tokens last two years, Guesty allows five a day, Cloudbeds keys die after 30 unused days. Repull holds each credential; you keep one key.
Channels next to the PMS
The same Repull key connects Airbnb, Booking.com and Vrbo directly, and more, for clients who have no PMS, alongside Hospitable accounts.
What Repull does not carry for Hospitable yet
Hospitable’s API can write the calendar and respond to reviews. Repull does not offer either for Hospitable today, so call Hospitable directly for those.
Connect Hospitable through Repull
Create a key, connect a Hospitable account with the credentials Hospitable issues, and read reservations in the same shape as every other system you support.
Frequently asked questions
Does Hospitable have a public API?
Yes. The Hospitable Public API v2 is a REST API at https://public.api.hospitable.com/v2 covering properties, calendar, reservations, inquiries, messaging, reviews, tasks, owner statements and webhooks. Hosts use a personal access token; companies building for other hosts use OAuth2 as approved vendors.
Which Hospitable plans include API access?
The paid plans: Host, Professional and Mogul. Hosts on Essentials have to upgrade before they can create a token or connect an app. Only the account owner or a full-access admin can create a personal access token.
What are the Hospitable API rate limits?
They are set per endpoint rather than globally. Reading the calendar is 1,000 requests a minute; reading a reservation’s messages is 2 a minute per reservation; sending is 2 a minute per reservation and 50 every five minutes. Limits count per vendor OAuth client, or per account for personal tokens.
Why does the Hospitable API return only a few reservations?
Without start_date and end_date (or booked_at), GET /reservations returns only check-ins in the next two weeks. It also requires properties[], so list the properties first and pass their UUIDs.
How do I verify Hospitable webhooks?
Each delivery carries a Signature header: an HMAC-SHA256 of the raw body with your webhook secret. Vendors manage the secret in the Partner Portal; for a host’s own account it is the primary user’s email address in base64. Deliveries come from 38.80.170.0/24 and are retried up to five times.
Does Hospitable have a sandbox?
Hospitable’s developer documentation does not describe a sandbox or test account. Vendors can create separate OAuth clients for development, staging and production in the Partner Portal.
Can I connect Hospitable to Repull?
Yes. Repull connects with an access token the host creates in their own Hospitable account (read access to read, write access to create and change manual reservations), and returns their reservations, conversations and calendar in the same shape as every other system.
The other systems Repull connects
Reference
Auth Type
Personal access token
Required Fields
accessTokenSupported Operations
Connection Guide
In Hospitable, open Apps → API access (or Settings → Integrations), Access tokens tab, and click + Add new. Choose read or write access, then send the token as accessToken.
Notes
- • Strong messaging automation
- • Good Airbnb, Booking.com and Vrbo integration
- • API access needs a paid Hospitable plan (not Essentials)
- • Personal access tokens last one year