Do I need a particular Beds24 plan for the API?

You create the access in the Marketplace menu of your account. Check with Beds24 directly before implementation begins whether your contract includes any restrictions.

Can I keep the Beds24 booking page and still have my own room pages?

Yes. Many hosts show apartments on their own pages and link to the Beds24 booking page for booking. This is a good intermediate step before a booking flow of your own follows.

What happens to existing bookings when the website is connected?

Nothing. Bookings stay in Beds24; the website only reads availability and prices and creates new direct bookings. Existing reservations from portals are not changed.

Who gets access to guest data?

Only whoever receives the invitation code with the permission for personal booking data. For that reason, create the code with only the permissions needed and record the connection in a data processing agreement.

Beds24 website connection: API V2 with webhooks

Key takeaways

The Beds24 booking page can be embedded by iFrame; Beds24 itself recommends opening it in a new tab on mobile devices.
API V2 covers bookings, inventory with prices, and properties. You grant access with an invitation code and fixed permissions, which cannot be changed later.
Inventory webhooks report bookings, cancellations, and availability and price changes, but not changes to the minimum stay.
According to Beds24, the standard quota is 100 credits per five minutes. A cache on the website keeps usage low.

There are two ways to connect Beds24 to your own website: through the ready-made booking page, which you embed by iFrame or link, or through API V2, with which your website reads and writes availability, prices and bookings itself. The booking page is quick to set up; the API gives you a booking flow in your own design and on your own domain.

Both routes use the same data: calendars, prices and bookings stay in Beds24, and Airbnb, Booking.com and the website all access them. Our page on connecting a channel manager and PMS describes how this chain is built in principle.

Beds24 website connection: what are the two routes?

The simple route is the Beds24 booking page. According to the Beds24 wiki, you generate the code for an embedded iFrame in the Settings menu, under Booking engine, Booking widgets, iFrame generator (as of November 2025) [Q2]. Beds24 itself notes that iFrames are convenient but can compromise usability, and recommends opening the booking page in a new tab [Q2]. On mobile devices, the wiki explicitly describes iFrames as problematic [Q2].

The second route is API V2. According to Beds24, it allows third parties to access the account, properties, bookings and inventory [Q1]. Your website then shows its own pages for rooms and apartments with live prices, and booking takes place without a jump to a third-party page.

What can the Beds24 API V2 do?

API V2 is Beds24's current interface; according to the wiki, the older V1 is outdated and is not recommended for new projects (as of 17 September 2026) [Q1]. The main areas are:

Bookings: read, create, change and delete, along with messages and invoices
Inventory: offers, availability and calendars with prices
Properties: master data for the accommodation and pricing rules

You grant access yourself. In the Marketplace, API menu under Settings, you generate an invitation code, which the website exchanges for a token [Q1]. Here you set the permissions that Beds24 calls scopes, such as bookings, personal booking data, financial data, inventory and properties; according to the wiki, they cannot be changed afterwards [Q1].

The deadlines are tight: an invitation code expires after 24 hours, and a token generated from it does too; a refresh token expires if it has not been used for 30 days [Q1]. A connection must therefore renew its token itself, or the website will be left without prices one morning.

Rundbogenfenster in einer hellen Mauer mit Blick auf einen See, bewaldete Berge und verschneite Gipfel im Abendlicht

How does the website learn about new bookings?

Beds24 reports changes through webhooks, that is, automatic notifications sent to an address on your website. According to the wiki, a booking webhook is sent when a booking is created or changed; custom headers and data in the message body are possible [Q4].

For calendars and prices, there are inventory webhooks. According to Beds24, they fire on new bookings, changed travel dates, cancellations, and changes to availability or price of a room type [Q3]. Changes to restrictions such as the minimum stay, by contrast, do not fire a webhook [Q3]. If your server does not answer with a success code, Beds24 retries several times over the next 30 minutes [Q3].

The note on minimum stays matters in practice. If you change restrictions often, you also need regular polling; otherwise the website shows a minimum night that Beds24 has long since changed. Webhooks also do not replace a live check before booking, because a message can arrive only on a later attempt after an error [Q3].

Calculation: is the API quota enough for 24 rooms?

Beds24 limits API use to 100 credits per five minutes by default; according to the wiki, raising this to 200 credits costs EUR 10 per month [Q1]. How many credits a query costs depends on its complexity. The calculation below therefore uses example values, which you should replace with your own.

In our example, these assumptions apply to a house with 24 rooms:

Occupancy: 60 percent, so about 5,256 room nights per year
Length of stay: 2.5 nights, so about 2,102 bookings
Visits with a calendar query: 50 per booking, so about 105,000 per year
Peak hour: 60 visits with three queries each, so 180 queries, or 15 per five minutes

If the website queries Beds24 directly on every visit, 15 queries per five minutes is harmless in our example. It becomes critical only when one query costs several credits, when search engine crawlers call calendar pages, or when an advertising push multiplies the number of visitors. That is why a short cache and quota monitoring belong in every connection.

And with six holiday apartments?

With six apartments, the quota is rarely the issue, but allocation is. Depending on the setup, each apartment is either its own property in Beds24 or a room within a property, and the website must know which page belongs to which unit.

Typical stumbling blocks are the final cleaning fee and the tourist tax: they must appear in the total price on the website, however they are stored in the system. There are also apartments that are sometimes let individually and sometimes together. Beds24 is also on Google's partner list for holiday rentals (as of September 2026), which can open a route for rental companies to show prices directly in Google Search [Q5]. If you are comparing Smoobu or Lodgify, the differences are covered in Smoobu and your own website and connecting Lodgify to your website.

Bild: Hölzerner Schreibtisch in einer Hotelrezeption mit schwarzem Karteikasten gefüllt mit Gästekarten, Stift und bedrucktem Buchungsformular im warmen Licht, Mitarbeiter unscharf im Hintergrund.

How to prepare the connection

Tidy up properties and room types in Beds24: unique names, correct occupancy, current prices
Check additional charges: final cleaning, tourist tax, pets, each with an amount and a rule
Create the invitation code with the necessary scopes and hand it over to the implementation within 24 hours
Enter the webhook addresses for bookings and inventory that the implementation team gives you
Run through a test booking and a cancellation, and check both in Beds24 and on the portals

Why a mismatch between the system and the website can lead to double bookings if one step is missing is described in the article on keeping the channel manager and website in sync.

What we build on the interface

With us, availability on the website comes live from Beds24, briefly cached so that the page stays fast even when the response is slow. Before each booking, we check availability live again, and every direct booking is written back to Beds24 with its payment status. If the interface fails, the website shows an enquiry instead of a booking, and we are notified automatically.

Access keys are stored encrypted on the server and never reach the browser. We use Beds24's publicly documented interface and do not claim any partnership. Whether your account, with its properties and additional charges, fits will be checked in the first conversation.

On the process: the Gastgeber package (for hosts) includes the connection to a system such as Beds24; our price starts at EUR 4,900 one-off and EUR 149 per month. A website like this takes us four to six weeks from approval of the concept. During that time, we need the invitation code from you, texts and photos for each apartment, and one person who checks the test bookings in Beds24.

When the embedded booking page is enough

The Beds24 booking page is the right choice if you have few units, maintain the website yourself, and the look of the booking page is secondary for you. It costs nothing to develop and is usually quick to embed.

A Beds24 website with its own booking flow is worth it only when guests drop off on their phones, when you want to show packages and extras, or when you want the website to be found in search engines with its own room pages.

Check which scopes and additional charges your Beds24 account uses today, and have a direct booking website built from them: book a call.