Beds24 API
Beds24 exposes API V2 at api.beds24.com/v2, a REST API covering bookings, booking messages, inventory (prices, availability, minimum stay), properties, accounts and channel settings, authenticated with a token header obtained from a single-use invite code and a refresh token.
Written from running this integration in production. Last checked against the Beds24 API on 11 November 2026.
Beds24 API report card
From Beds24's own documentation. Checked on 11 November 2026.
- Base URL / API style
https://api.beds24.com/v2. REST, JSON. Writes take arrays and answer one result per item. API V1 is deprecated. source- Auth
tokenheader. Tokens come from a refresh token and last 24 hours; the refresh token comes from a single-use invite code with fixed scopes and lasts as long as it is used every 30 days. Read-only long-life tokens are the alternative. source- Rate limits
- 100 credits / 5 min per account by default, shared by all its tokens; each request costs credits by complexity. 200 credits / 5 min for 10 EUR a month through support. source
- Webhooks
- Booking webhooks set by the account holder in the control panel; new bookings and significant changes (dates, cancellations), message activity included. API-created bookings need
allowWebhooks=true. source - Read / write coverage
- Bookings (read, create, modify, cancel), booking messages and invoices, the inventory calendar (prices, availability, minimum stay), offers, properties and rooms with price rules, accounts, channel settings (Airbnb, Booking.com, Stripe). No property pictures. source
- Guest messaging
GETandPOST /bookings/messages; delivered through the channel’s own messaging where the channel supports it. Needsbookings-personal. source- Sandbox / test account
- “There is no sandbox so test carefully before going live.” source
- Partner / marketplace programme
- Marketplace integrations request an organization token form by support ticket. The tokens are permanent and cover the accounts that activate the integration in the Marketplace, with no invite codes. source
- Restrictions worth knowing
- Prices are not calculated for API-created bookings (send
price). Invite codes expire after 24 hours and can be limited to whitelisted IP addresses. source
What the Beds24 API is
Beds24’s API V2 is a JSON REST API at https://api.beds24.com/v2. It covers bookings with their messages and invoices, the inventory calendar (per-date prices, availability and minimum stay) and offers, properties and rooms with price rules, accounts, and channel settings, with dedicated endpoints for Airbnb, Booking.com and Stripe. API V1, the one with an API key and a property key, is deprecated, and Beds24 recommends V2 for every new integration.
Access is self-serve on every account. The account holder creates an invite code in the control panel, choosing scopes (what the code may read and change), whether linked properties are included, and optionally an IP whitelist. You exchange the code for a refresh token, and the refresh token for tokens that last 24 hours.
The API is broad and its writes are batch-shaped: one POST can create or change many items. Most of what bites is in how a batch answers, and in a credit-based limit shared by every token on the account.
How to get Beds24 API access
- 1.In Beds24, open Settings → Marketplace → API and click Generate invite code. If the API menu is missing, Beds24 support enables it.
- 2.Choose the scopes:
bookings, plusbookings-personalfor guest details and messages andbookings-financialfor prices;inventory,properties,accountsorchannelsas you need them, each read or write. Scopes cannot be changed later; a different set means a new invite code. - 3.Exchange the code within 24 hours:
GET https://api.beds24.com/v2/authentication/setupwith the code in acodeheader returns a refresh token. The code is single-use. - 4.Get a token with
GET /authentication/tokenand arefreshTokenheader, and send it as atokenheader on every call. Tokens last 24 hours; a refresh token keeps working as long as it is used at least once every 30 days.
For read-only work there is a shortcut: a long-life token from the same page needs no exchange. It can only read, and it expires after 90 days without use.
What will bite you
From running this integration in production and reading the vendor's documentation line by line.
A 201 can carry failures
POST /bookings takes an array and answers 201 with one result per item, in order. An item can fail inside that 201, with success: false and an errors list, while its neighbours succeed. Code that checks the HTTP status records a refused booking as created.
Missing scopes drop fields instead of failing
Without bookings-personal, Beds24 can save a booking and drop the guest’s details; without bookings-financial, the price. The booking exists and the warning sits in that item’s response. Since scopes are fixed when the invite code is made, fixing it means asking the host for a new code.
Cancelled bookings are left out by default
GET /bookings “will default to confirmed, request, new, black and inquiry” when you do not pass status. A sync that does not ask for cancelled explicitly never sees a cancellation and keeps the stay on your calendar. Lists also page: keep requesting while pages.nextPageExists is true, or the sync silently stops after the first page.
Credits, not requests, and shared across the account
The limit is 100 credits per 5 minutes by default, each request costing a variable number of credits by complexity. It is set per account, so every token on the account, yours and every other tool the host uses, draws from the same budget. Fetching a new token costs credits too, so keep one for its full 24 hours. Beds24 support raises the limit to 200 credits per 5 minutes for 10 EUR a month.
API bookings have no price, and no webhook, unless you ask
Prices are not calculated for bookings created through the API: send price, or the booking has no total. Booking webhooks do not fire for API-created bookings unless the request includes allowWebhooks=true.
`endDate` is the last night, and channels update later
Availability calls take the last night to be booked as endDate, the day before check-out. Pass the check-out date and you check one night too many. And a price or availability change reaches the channels the next time a price or availability changes, or within 24 hours, so a write that returned success is not yet live on Airbnb or Booking.com.
What it costs to keep working
A Beds24 connection keeps working as long as something keeps it alive.
- •Refresh tokens expire after 30 days without use. A host who pauses for a season comes back to a dead connection and has to issue a new invite code.
- •The credit budget is shared with every other tool on the account, so your sync competes with theirs.
- •Batch responses need per-item handling, and scope warnings need to reach the host, who is the only one who can issue a code with more scopes.
- •Webhooks are configured by the host in the control panel (Settings → Properties → Access → Booking webhooks), not by your code.
The same job, both ways
Beds24 directly
# Once: swap the host's single-use invite code for a refresh token.
curl -s 'https://api.beds24.com/v2/authentication/setup' -H 'code: INVITE_CODE'
# Every 24 hours: a token from the refresh token.
curl -s 'https://api.beds24.com/v2/authentication/token' -H 'refreshToken: REFRESH_TOKEN'
# Bookings modified since a date. Ask for cancelled ones explicitly,
# and keep paging while pages.nextPageExists is true.
curl -s -g 'https://api.beds24.com/v2/bookings?modifiedFrom=2026-11-01T00:00:00&status[]=confirmed&status[]=cancelled' \
-H 'token: TOKEN'Through Repull
# Connect once with the invite code. Repull refreshes the tokens.
curl -s -X POST 'https://api.repull.dev/v1/connect/beds24/credentials' \
-H 'Authorization: Bearer sk_live_YOUR_KEY' \
-H 'Content-Type: application/json' \
-d '{"credentials": {"inviteCode": "INVITE_CODE"}}'
# Reservations from Beds24 and every other connected PMS and channel,
# cancellations included.
curl -s 'https://api.repull.dev/v1/reservations?limit=100' \
-H 'Authorization: Bearer sk_live_YOUR_KEY'Why use Repull for Beds24
Your second client will not be on Beds24
If every account you serve is on Beds24, API V2 is broad enough to build on directly, and Repull would be a layer you do not need. The cost arrives with the first client on something else.
Every system authenticates differently
Beds24 is a single-use invite code that becomes a refresh token. Smoobu signs every request with a key, a secret and a nonce. OwnerRez personal tokens reach two accounts per IP per day. Guesty allows five tokens a day. Repull holds and refreshes each of them; you keep one key.
One reservation shape across every system
A Beds24 booking, a Hostaway reservation and a Lodgify one come back from GET /v1/reservations with the same fields, platform naming the channel, with no status filters to remember.
Missing scopes are named, not swallowed
When Beds24 refuses a write for a missing scope, Repull answers connection_reauth_required naming the scope the new invite code needs, instead of a booking with no guest or no price.
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 Beds24 accounts.
Connect Beds24 through Repull
Create a key, connect a Beds24 account with the credentials Beds24 issues, and read reservations in the same shape as every other system you support.
Frequently asked questions
Does Beds24 have an API?
Yes. Beds24 API V2 is a REST API at https://api.beds24.com/v2 covering bookings, booking messages and invoices, the inventory calendar, offers, properties, accounts and channel settings. It is available on every account. API V1 is deprecated.
How do I get a Beds24 API key?
API V2 has no static key. Create an invite code under Settings → Marketplace → API with the scopes you need, exchange it at GET /authentication/setup for a refresh token, then use GET /authentication/token for 24-hour tokens sent in a token header. The API key and property key belong to the deprecated API V1.
What is the Beds24 API rate limit?
100 credits per 5 minutes by default, set per account and shared by all its tokens. Each request costs credits by complexity; response headers show what is left and when the window resets. Beds24 support raises it to 200 credits per 5 minutes for 10 EUR a month.
Why are cancelled bookings missing from the Beds24 API?
Because GET /bookings defaults status to confirmed, request, new, black and inquiry. Pass status[]=cancelled (with the others you want) to see cancellations.
Does Beds24 have webhooks?
Yes. The account holder sets booking webhooks under Settings → Properties → Access → Booking webhooks. They fire on new bookings and significant changes such as date changes and cancellations, not on every guest detail change, and message activity is included. Bookings created through the API fire one only with allowWebhooks=true.
Is there a Beds24 sandbox?
No. Beds24 says there is no sandbox, so test carefully before going live, for example on a property you keep for testing.
Can I use Beds24 and Repull together?
Yes. Repull connects with an invite code the host generates, keeps the tokens refreshed, and changes nothing inside Beds24. Grant write:bookings, bookings-personal and bookings-financial if your app creates reservations.
The other systems Repull connects
Reference
Auth Type
API V2 invite code (exchanged for refresh and access tokens)
Required Fields
inviteCodeSupported Operations
Connection Guide
In Beds24, open Settings → Marketplace → API and generate an invite code (it expires after 24 hours and works once). Choose the scopes you want Repull to have, then paste the code as inviteCode.
Notes
- • API V2: an invite code with chosen scopes, exchanged for a refresh token and 24-hour tokens; the API V1 key and property key are deprecated
- • Rate limit: 100 credits per 5 minutes per account by default, shared by every token on it
- • Creating reservations needs write:bookings, plus bookings-personal for guest details and bookings-financial for the price