Skip to main content
If your properties run on Beds24, guest messages from Booking.com, Airbnb, Expedia and Vrbo already arrive in your Beds24 inbox. Sensbot reads them there, together with the booking and your property information, and writes the reply in the guest’s language. You start with drafts: every reply waits for you in the Sensbot Inbox, and you send it yourself. Later you choose which routine questions (for example check-in and check-out times) may be answered automatically. Questions about money, booking changes and complaints always stay with you.
Connecting is done together with us for now. You create an invite code in Beds24 and send it to us, and we connect your properties and go through your house information with you.

Before you start


Step 1 · Open the API page in Beds24

  1. Log in to the Beds24 control panel.
  2. Open Marketplace → API, or go straight to beds24.com/control3.php?pagetype=apiv2 while logged in.
The page shows three lists: Invite Codes, Refresh Tokens and Long Life Tokens. The Beds24 Marketplace > API page with the Invite Codes list and the Generate invite code button

Step 2 · Create an invite code

  1. Click Generate invite code. A window opens with a table of scopes and the columns READ, WRITE, DELETE and ALL.
  2. Tick these boxes, and nothing else:
  1. Select which properties this token can access: leave All owned by account, or choose only the properties Sensbot should answer for.
  2. IP address whitelist: leave it empty.
  3. Name for this token: Sensbot.
  4. Click Generate invite code. Do not use Generate long life token.
The Beds24 Generate invite code window with bookings READ, bookings-personal READ and WRITE, properties READ and channels READ ticked, all properties selected, no IP whitelist and the name Sensbot The new code appears in the Invite Codes list.
Beds24 fixes the permissions when the code is created. If you leave out bookings-personal → WRITE, Sensbot can still prepare drafts, but to switch on automatic replies later you would need to create a new code.
Sensbot posts nothing to your guests while you work with drafts. A reply only goes out through Beds24 after you have switched automatic sending on for that type of question.

Step 3 · Send the code to us

Copy the code from the Invite Codes list and send it to support@sensbot.ai. The code works only once and expires 24 hours after you create it, so send it the same day. We then:
  1. Connect your Beds24 account. The code is used up, and Sensbot’s access appears in the Refresh Tokens list on the same API page.
  2. Load your properties, upcoming bookings and recent guest conversations.
  3. Check your house information with you (house rules, check-in and check-out, directions, parking), because that is what the replies are written from.

What Sensbot reads from Beds24

If something is not in Beds24, Sensbot does not guess: the question stays with you as a draft.

Drafts and automatic replies

  • New guest messages appear in the Sensbot Inbox with a draft reply. You check it, edit it if needed and send it.
  • When you keep sending a type of reply without changes, it can become a candidate for automatic sending. Before anything is switched on, we check Sensbot’s answers against how you actually replied to past guests.
  • Automatic sending starts with standard check-in and check-out times. Anything wider is agreed with you first.
  • Payments, refunds, prices, booking changes, early check-in, late check-out and complaints are never sent automatically.
Your guests change nothing: they keep writing on Booking.com, Airbnb, Expedia or Vrbo, and replies arrive in the same conversation, which you also see in Beds24.
Guests who booked directly (on your own booking page) have no message thread in Beds24, so Sensbot does not see their messages there.

Disconnecting

On the Beds24 API page (Marketplace → API), delete the Sensbot token in the Refresh Tokens list. Sensbot can no longer renew its access, and the last access key it holds expires within 24 hours. Let us know at support@sensbot.ai and we also remove the connection on our side.