Docs/Knowledge Base/PMS Guides

BookingSync API

BookingSync, now Smily, exposes a REST API (v3) at www.bookingsync.com/api/v3 covering rentals, bookings, clients, availabilities, rates, fees, taxes, payments, reviews and the inbox, authenticated with OAuth 2.0 access tokens that last 2 hours and refresh tokens that rotate on every use, limited to 1,000 requests per hour per application.

Written from running this integration in production. Last checked against the BookingSync API on 12 November 2026.

BookingSync API report card

From BookingSync's own documentation. Checked on 12 November 2026.

Base URL / API style
https://www.bookingsync.com/api/v3/. REST, JSON, with paging, field limiting, sideloading and Idempotency-Key. source
Auth
OAuth 2.0: authorization code, implicit, or client credentials once the account has authorized the app. Access tokens last 2 hours; refresh tokens rotate on every refresh. Scopes per resource (e.g. bookings_read, bookings_write, inbox_write). source
Rate limits
1,000 requests / hour by default, per OAuth application. X-RateLimit-* headers; a 429 carries Retry-After in seconds. source
Webhooks
Configured per application in the partner panel; 64 events. X-Content-Signature is an HMAC-SHA1 hex digest of the Base64-encoded body with the app secret. Retries not documented. source
Read / write coverage
Rentals and their content, bookings, clients, availabilities (read-only), rates, seasons, fees, taxes, payments, payouts, reviews and replies, inbox, inquiries, special offers and tasks. source
Guest messaging
Inbox API: read conversations and messages (inbox_read), create messages (inbox_write). A message with channel set is relayed to that channel, such as Airbnb or Booking.com; without it, it stays in Smily. source
Sandbox / test account
Not documented.
Partner / marketplace programme
Free partner signup; applications registered in the partner panel. Private apps are limited to 5 connected accounts; published, reviewed apps have no cap (contact partners@smily.com, typically a revenue share). source
Restrictions worth knowing
Availability is read-only: a 1,096-character day map per rental, with no write endpoint. source

What the BookingSync API is

BookingSync is a vacation rental PMS and channel manager that now trades as Smily. Its API v3 lives at https://www.bookingsync.com/api/v3/ and is a conventional REST API: rentals, bookings, clients (guests), availabilities, rates and seasons, fees and taxes, payments, reviews and replies, the inbox (conversations and messages), inquiries, special offers and tasks. Requests and responses are JSON, with paging, field limiting, sideloading and Idempotency-Key support.

Every request is made by an OAuth application registered in the Smily partner panel. Signing up as a partner is free. An account authorizes your application with the scopes you ask for, and you get a 2-hour access token plus a refresh token that is replaced each time you use it.

Private applications are capped at 5 connected accounts by default. To go beyond that, Smily reviews and publishes the application, typically under a revenue-share agreement.

Through Repull: BookingSync rentals, bookings, guests, nightly availability and inbox threads come back in the same shape as every other connected system, and bookings can be quoted, created, changed and cancelled with POST /v1/reservations/quote, POST /v1/reservations, PATCH /v1/reservations/{id} and POST /v1/reservations/{id}/cancel. BookingSync is in beta on Repull.

How to get BookingSync API access

  1. 1.Sign up as a Smily partner (free) and open the partner panel’s Applications page. Click New Application and enter your OAuth callback URL (redirect_uri). Keep it Private while you build.
  2. 2.Send the account owner to https://www.bookingsync.com/oauth/authorize with your client ID, redirect URI, response_type=code and space-separated scopes, for example rentals_read bookings_read clients_read inbox_read. Add bookings_write and clients_write if you will write bookings.
  3. 3.Exchange the returned code at https://www.bookingsync.com/oauth/token with grant_type=authorization_code. You receive an access token (expires_in: 7200) and a refresh token.
  4. 4.To connect to Repull, send the client ID, client secret, access token and refresh token to POST /v1/connect/bookingsync/credentials as clientId, clientSecret, accessToken and refreshToken. Repull checks the access token against your rentals and refreshes it from then on.

For a quick test without a web server, Smily’s testing guide uses the redirect URI urn:ietf:wg:oauth:2.0:oob, which shows the code on screen.

What will bite you

From running this integration in production and reading the vendor's documentation line by line.

Refresh tokens rotate, so save every one

Smily: “A new refresh_token will be generated after each refresh, therefore make sure to save it.” Two processes refreshing at once, or a crash between refreshing and saving, leaves you holding a dead refresh token, and the only fix is for the account to authorize the application again. A refresh token otherwise stays valid as long as it is used, or until the application is uninstalled.

1,000 requests an hour, per application

The default limit is 1,000 requests per hour, applied per OAuth application (CLIENT_ID). Responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and a 429 includes Retry-After in seconds. Ask only for the fields and associations you need, and sync with updated_since rather than re-reading everything.

Five accounts, then you need Smily’s review

A private application can connect 5 accounts by default; the sixth installation is blocked. Published, reviewed applications have no cap, and lifting it is arranged with partners@smily.com, typically through a revenue share.

Webhooks are configured in the partner panel, and the signature is particular

Webhooks are added per application in the partner panel (64 event types), not through the API. Each request has X-Content-Signature: an HMAC-SHA1 hex digest, made with the application secret, of the Base64-encoded JSON body. Smily’s example uses Ruby’s Base64.encode64, which inserts a newline every 60 characters and at the end, so another language has to reproduce those newlines or every signature fails. Rental events arrive only for rentals the account exposes to your application.

Availability is read-only

Availability comes back as a 1,096-character string per rental, one character per day from start_date. There is no endpoint to write it: nights close when bookings cover them.

A message without a channel stays in Smily

Creating an inbox message needs a conversation, a sender (an inbox participant id), an origin, a visibility and sent_at. Only when channel is set is the message relayed to that channel, such as Airbnb or Booking.com; without it, the message stays inside Smily and the guest never sees it.

What it costs to keep working

The API itself is well documented. What you own is the token chain, the hourly budget and the account cap.

  • •A refresh routine that saves each rotated refresh token atomically, and reconnects an account whose chain broke.
  • •A request budget of 1,000 an hour per application, shared by every sync.
  • •The 5-account cap on private applications, and a conversation with Smily before account six.
  • •Webhook signature code that matches Ruby’s Base64 output byte for byte.

The same job, both ways

BookingSync directly

# Access tokens last 2 hours. Refresh, then save the NEW refresh token.
curl -s -X POST 'https://www.bookingsync.com/oauth/token' \
  -d grant_type=refresh_token -d refresh_token=YOUR_REFRESH_TOKEN \
  -d client_id=YOUR_CLIENT_ID -d client_secret=YOUR_CLIENT_SECRET \
  -d redirect_uri=YOUR_REDIRECT_URI

curl -s 'https://www.bookingsync.com/api/v3/bookings?updated_since=2026-11-01T00:00:00Z' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Through Repull

# Connect once. Repull refreshes the token and keeps each new refresh token.
curl -s -X POST 'https://api.repull.dev/v1/connect/bookingsync/credentials' \
  -H 'Authorization: Bearer sk_live_YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"credentials": {"clientId": "YOUR_CLIENT_ID", "clientSecret": "YOUR_CLIENT_SECRET", "accessToken": "YOUR_ACCESS_TOKEN", "refreshToken": "YOUR_REFRESH_TOKEN"}}'

# Bookings from BookingSync and every other connected system, one shape.
curl -s 'https://api.repull.dev/v1/reservations?limit=100' \
  -H 'Authorization: Bearer sk_live_YOUR_KEY'

Why use Repull for BookingSync

Your next client may not be on Smily

If you serve one Smily account, call its API directly: it is a clean REST API, and Repull would be a layer you do not need. If you plan to serve many Smily accounts, talk to Smily’s partner team about review early. The cost of doing it yourself arrives with the second system.

The token chain, kept

Repull refreshes the 2-hour access token and stores each rotated refresh token, so the connection does not die the first time two refreshes overlap.

One reservation shape

BookingSync bookings, Hostaway reservations and Guesty’s airbnb2 bookings all come back from GET /v1/reservations in one schema, with platform naming the channel.

Writes checked before they are sent

A change to a booking Smily imported from a channel is answered 422 pms_write_unsupported naming BookingSync, and capabilities.pms on the connection says what BookingSync can do before you try.

Every system authenticates differently

BookingSync rotates its refresh token on every use. iGMS puts an OAuth token in the query string, Smoobu signs each request, Guesty allows five tokens a day. Repull holds each one; you keep one key.

Channels next to the PMS

The same Repull key connects Airbnb, Booking.com and Vrbo directly, and more, alongside BookingSync accounts.

Connect BookingSync through Repull

Create a key, connect a BookingSync account with the credentials BookingSync issues, and read reservations in the same shape as every other system you support.

Frequently asked questions

Does BookingSync have an API?

Yes. BookingSync, now Smily, has a REST API v3 at https://www.bookingsync.com/api/v3/ documented at developers.bookingsync.com. It covers rentals, bookings, clients, availabilities, rates, fees, taxes, payments, reviews, the inbox and tasks.

Is BookingSync the same as Smily?

Yes. BookingSync now trades as Smily. The developer documentation is branded Smily, while the API and OAuth endpoints are still on www.bookingsync.com.

How do I get BookingSync API credentials?

Sign up as a Smily partner (free), register an application in the partner panel to get a client ID and secret, then have the account authorize it through OAuth 2.0 at www.bookingsync.com/oauth/authorize and exchange the code for an access token and refresh token.

What is the BookingSync API rate limit?

1,000 requests per hour by default, applied per OAuth application. A 429 response includes Retry-After with the seconds until the limit resets.

Does BookingSync have webhooks?

Yes. You add them per application in the partner panel, choosing from 64 events. Each request is signed in X-Content-Signature with an HMAC-SHA1 of the Base64-encoded body, made with your application secret.

What can Repull do with a BookingSync account?

Read rentals, bookings, guests, nightly availability and inbox threads, and quote, create, change and cancel bookings on a rental. Calendar and price writes, reviews and listing content are not available through Repull for BookingSync. Send guest replies from Smily for now: Repull does not yet choose the guest’s channel when it posts a BookingSync message. BookingSync is in beta on Repull.

The other systems Repull connects

Reference

Auth Type

OAuth 2.0 (authorization code, rotating refresh tokens)

Required Fields

clientIdclientSecretaccessTokenrefreshToken

Supported Operations

✓ listings
✓ reservations
✓ calendar
✓ messages
— webhooks
✓ guests

Connection Guide

Register an application in the Smily (BookingSync) partner panel, authorize it on your account with the scopes you need (rentals_read, bookings_read, clients_read, inbox_read, plus bookings_write and clients_write for booking writes), then paste the client ID, client secret, access token and refresh token into Repull Connect.

Notes

  • • BookingSync is now Smily; the API is still served at www.bookingsync.com/api/v3
  • • Connect with your Smily OAuth application’s client ID and secret plus the access and refresh token from authorizing it on your account. Without a refresh token the connection cannot sync once the first access token expires (after 2 hours)
  • • Refresh tokens rotate on every use; Repull stores each new one
  • • Smily allows 1,000 requests per hour per OAuth application
  • • Bookings can be quoted, created, changed and cancelled; bookings imported from channels cannot be changed
  • • Availability is read through Repull; Smily’s availability endpoint is read-only
AI