Smoobu API
Smoobu exposes a REST API at login.smoobu.com/api covering apartments, bookings, rates and availability, guests, message threads and webhooks, authenticated by signing every request with an API key and secret (HMAC-SHA256); legacy single API keys stopped working on October 31, 2026.
Written from running this integration in production. Last checked against the Smoobu API on 11 November 2026.
Smoobu API report card
From Smoobu's own documentation. Checked on 11 November 2026.
- Base URL / API style
https://login.smoobu.com/api. REST, JSON over HTTPS. The availability check sits outside/api, at/booking/checkApartmentAvailability. source- Auth
- Every request signed with HMAC-SHA256 using an API key and secret (
X-API-Key,X-Timestamp,X-Nonce,X-Signature); timestamp within 5 minutes, each nonce used once. Legacy single keys were sunset on October 31, 2026. OAuth 2 for Smoobu partners only. source - Rate limits
- 700 requests / minute (1,000 before September 17, 2026). A 429 carries
X-RateLimit-Retry-After, a Unix timestamp. source - Webhooks
- Self-managed URLs through
/api/users/webhooks(since August 2026). Every URL gets all of a user’s events; no subset. Price element events go only to partners Smoobu configures. No payload signature documented. source - Read / write coverage
- Apartments; bookings (create, update, cancel); rates and availability (read and write); guests; message threads; custom placeholders; online check-in; price elements. source
- Guest messaging
- Read message threads and messages; send a message to the guest, or to the host, on a booking. source
- Sandbox / test account
- Not documented.
- Partner / marketplace programme
- Third-party providers serving more than one Smoobu user go through a separate authorization process; contact Smoobu, which can list you for its users. source
- Restrictions worth knowing
- Since October 22, 2026, guest personal data (name, email, phone, online check-in documents) is returned only to keys with the Guest Data (PII) option; other keys get empty strings. source
What the Smoobu API is
Smoobu’s API is a JSON REST API at https://login.smoobu.com/api, not on an api. subdomain. It covers apartments, bookings, rates and availability, guests, message threads, custom placeholders, online check-in and webhook management. You can create a booking (Smoobu treats it like one from a booking channel and syncs it to every other channel), change or cancel direct bookings, set rates and minimum stays, and send a message to a guest.
Access is self-serve for an account holder: create an API key and a secret in the dashboard and sign every request with them. The old single-key header no longer works. Software that serves more than one Smoobu user is a third-party provider with its own authorization process, and OAuth 2 is currently available only to Smoobu partners.
The API itself is small and readable. Most of the work is in the signing, and in a handful of rules about which bookings you may touch.
How to get Smoobu API access
- 1.In Smoobu, open Settings → Advanced → API Keys and click Create API Key.
- 2.Click Generate Secret. Copy the API key and the secret: the secret is shown once and cannot be retrieved later. If you lose it, generate a new one.
- 3.If you need guest names, emails, phone numbers or check-in documents, tick the key’s Guest Data (PII) option. Since October 22, 2026, keys without it get those fields as empty strings.
- 4.Sign every request with four headers,
X-API-Key,X-Timestamp,X-NonceandX-Signature, as described in the next section, and send it tohttps://login.smoobu.com/api.
Building for more than one Smoobu user? Smoobu asks you to contact it before you start: third-party providers are authorized differently, and Smoobu can list you so its users can connect your product.
What will bite you
From running this integration in production and reading the vendor's documentation line by line.
Legacy single API keys stopped working on October 31, 2026
Smoobu’s documentation: “Legacy API keys are deprecated and will be sunset on October 31, 2026 for all Smoobu API users. Requests using the legacy Api-Key header will stop working after that date.” An integration still sending Api-Key: … now gets a 401 on every call. Older tutorials, client libraries and some of the endpoint examples in Smoobu’s own reference still show the legacy header, so copy-pasted code fails.
The signature has to match the exact bytes you send
The canonical string is the method, the path, the sorted query, the timestamp, the nonce, the SHA-256 hex of the body and the API key, joined by newlines with no trailing newline. The signature is its HMAC-SHA256 with the secret, base64-encoded. Query keys and values are RFC 3986-encoded: a space is %20, not +, and [] is %5B%5D. An HTTP client that re-serializes the query after you signed it produces a request Smoobu rejects, so sign the bytes that go on the wire.
Every retry needs a new nonce
The timestamp must be within 5 minutes of Smoobu’s clock, and a nonce may be used once: “Reusing a nonce causes a 401 even if the signature is valid.” A retry wrapper that resends the same headers after a timeout turns a network blip into an authentication error that looks like bad credentials. Sign each attempt afresh, and keep the server clock on NTP.
Guest data comes back empty unless the key allows it
Since October 22, 2026, only keys with the Guest Data (PII) option receive guest names, emails, phone numbers and online check-in documents. For other keys those fields are empty strings. Nothing errors: bookings simply arrive with blank guests.
Dates cannot be changed, and channel bookings cannot be touched
Updating a booking accepts arrival and departure times, the price, guest details, guest counts and notes, but no arrival or departure date, so a date change is a cancel and rebook, or an edit in Smoobu. In production, bookings from Airbnb, Booking.com and other channels cannot be changed or cancelled through the API, only direct ones. A cancelled booking stays in Smoobu as a cancellation.
Webhooks are all-or-nothing and unsigned
Since August 2026 you register webhook URLs yourself through /api/users/webhooks. Every registered URL receives every event for that user; there is no way to subscribe to a subset. Price element events go only to partners Smoobu configures. The documentation describes no payload signature, so treat a webhook as a prompt and read the booking back. When a user disconnects a partner, that partner’s URLs are removed immediately.
The rate limit dropped to 700 a minute
On September 17, 2026 Smoobu lowered the limit from 1,000 requests per minute to 700. A 429 comes with X-RateLimit-Retry-After, which is the Unix time the window ends, not a number of seconds. The apartments list returns only ids and names, so a full sync makes one detail call per apartment and reaches the limit sooner than you would expect.
What it costs to keep working
Smoobu changed its authentication, its rate limit, its webhooks and its guest-data rules in the six months before this page was written. Keeping up is the job.
- •Read the changelog. 2026 brought HMAC signing (May), self-service webhooks (August), a lower rate limit (September), the Guest Data option on keys (October 22) and the end of legacy keys (October 31).
- •Clock and nonce hygiene: NTP on every host that signs requests, and a fresh nonce on every attempt.
- •Credentials are a key and a secret per account, and the secret cannot be shown again. A host who loses it generates a new one and has to send it to you.
- •Booking rules: the channel a booking came from decides whether you may change it, and a date change is a cancel and rebook.
The same job, both ways
Smoobu directly
# Every request is signed (HMAC-SHA256). A GET hashes an empty body.
KEY=YOUR_API_KEY; SECRET=YOUR_API_SECRET
TS=$(date -u +%Y-%m-%dT%H:%M:%SZ); NONCE=$(uuidgen | tr 'A-Z' 'a-z')
BODY_HASH=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
CANONICAL="GET\n/api/apartments\n\n$TS\n$NONCE\n$BODY_HASH\n$KEY"
SIG=$(echo -en "$CANONICAL" | openssl dgst -sha256 -hmac "$SECRET" -binary | base64)
curl -s 'https://login.smoobu.com/api/apartments' \
-H "X-API-Key: $KEY" -H "X-Timestamp: $TS" \
-H "X-Nonce: $NONCE" -H "X-Signature: $SIG"
# A retry needs a new nonce, and so a new signature.Through Repull
# Connect once with the same key and secret.
curl -s -X POST 'https://api.repull.dev/v1/connect/smoobu/credentials' \
-H 'Authorization: Bearer sk_live_YOUR_KEY' \
-H 'Content-Type: application/json' \
-d '{"credentials": {"apiKey": "YOUR_API_KEY", "apiSecret": "YOUR_API_SECRET"}}'
# Repull signs every Smoobu call. Reservations from Smoobu and every
# other connected PMS and channel come back in one shape.
curl -s 'https://api.repull.dev/v1/reservations?limit=100' \
-H 'Authorization: Bearer sk_live_YOUR_KEY'Why use Repull for Smoobu
Your second client will not be on Smoobu
If you have one Smoobu account and always will, call its API directly and sign the requests yourself: it is a few dozen lines, and Repull would be a layer you do not need. The cost arrives with the next system.
Every system authenticates differently
Smoobu signs each request with a key, a secret and a single-use nonce. Guesty allows five tokens a day. OwnerRez personal tokens reach two accounts per IP per day. Beds24 swaps a single-use invite code for refresh tokens that die after 30 days unused. Repull holds and refreshes each of them; you keep one key.
One reservation shape across every system
Smoobu’s kebab-case booking fields, Hostaway’s numeric channel ids and Guesty’s airbnb2 all come back from GET /v1/reservations in one schema, with platform naming the channel.
Refused writes are refused before anything is sent
A date change on a Smoobu booking, or any change to a booking from Airbnb or Booking.com, is answered 422 pms_write_unsupported naming Smoobu, and capabilities.pms on the connection says so in advance.
Channels next to the PMS
Some clients have no PMS at all. The same Repull key connects Airbnb, Booking.com and Vrbo directly, and more, alongside Smoobu accounts.
Connect Smoobu through Repull
Create a key, connect a Smoobu account with the credentials Smoobu issues, and read reservations in the same shape as every other system you support.
Frequently asked questions
Does Smoobu have an API?
Yes. Smoobu’s REST API at https://login.smoobu.com/api covers apartments, bookings, rates and availability, guests, message threads, online check-in and webhooks. An account holder creates an API key and secret under Settings → Advanced → API Keys; no partner application is needed for your own account.
How do I get a Smoobu API key?
In Smoobu, open Settings → Advanced → API Keys, click Create API Key, then Generate Secret. Copy both; the secret is shown once. Tick the Guest Data (PII) option if you need guest personal data. Every request must then be signed with the key and secret.
Why does my Smoobu API key return 401?
Most often because it is a legacy key: Smoobu stopped accepting the single Api-Key header on October 31, 2026. Create an API key and secret and sign each request. With signing, a 401 also means a wrong signature, a timestamp more than 5 minutes off, or a nonce used twice.
What is the Smoobu API rate limit?
700 requests per minute, lowered from 1,000 on September 17, 2026. Responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Retry-After, the last being the Unix time the window ends. Exceeding the limit returns 429.
Does Smoobu have webhooks?
Yes. Since August 2026 you register URLs through the Webhook Management API at /api/users/webhooks. Every URL receives all of a user’s events except price element events, and you cannot pick a subset. Reservation webhooks carry the same object as Get Booking, including price elements.
Why are guest names empty in Smoobu API responses?
Because the API key does not have the Guest Data (PII) option. Since October 22, 2026, only keys with it receive guest names, emails, phone numbers and online check-in documents; for other keys those fields are empty strings.
Can I use Smoobu and Repull together?
Yes. Repull connects with the same API key and secret, signs every request, and changes nothing inside Smoobu. You read through Repull’s unified schema and can still call Smoobu directly for anything Smoobu-specific.
The other systems Repull connects
Reference
Auth Type
API Key + Secret (HMAC)
Required Fields
apiKeyapiSecretSupported Operations
Connection Guide
Smoobu → Settings → Advanced → API Keys → Create API Key, then Generate Secret (shown once); paste both. Tick the key’s Guest Data (PII) option if you need guest names, emails and phone numbers.
Notes
- • Every request is signed with HMAC-SHA256; legacy single API keys stopped working on October 31, 2026
- • Guest names, emails and phones are returned only to keys with the Guest Data (PII) option
- • Rate limit: 700 requests per minute
- • Booking dates cannot be changed through the API, and channel bookings cannot be changed or cancelled