AI guest messaging for NOBEDS guesthouses and hostels
TravelPal messages your NOBEDS guests in their booking chat, and guest replies go to your team. You connect it with one API token that you make yourself in NOBEDS.
TravelPal does not reply to guests in NOBEDS yet. Your team does. Each item is explained below.
What TravelPal reads from NOBEDS
NOBEDS is used by guesthouses, small hostels, and independent hosts. Most have one property with its rooms under it. It is a Lithuanian product, and its home market is the Baltics.
Your rooms, minus the door code
NOBEDS calls a unit a rental. One account is one property with its rooms under it. TravelPal reads the title, description, photos, and unit type. It also reads how many guests it sleeps and your check-in and check-out hours. It takes the address, city, and currency from your account profile. A room has none of its own. NOBEDS also gives each rental a field where many properties keep smart lock PINs and wifi passwords. TravelPal leaves that field out of what the concierge can read. An access code reaches a guest only under your rules, see how access is handled.
Bookings, with the channel and the guest's own reference
An order is what NOBEDS calls a booking. It arrives with its dates, nights, party size, guest name, email, and phone. It also shows the referral behind it: Airbnb, Booking.com, Expedia, Agoda, Trip.com, Hostelworld, or your direct engine. The concierge quotes the channel's confirmation code, not the internal order number. It is the code printed on the guest's Booking.com email. Money is shown in your account currency. If an account lists more than one currency, TravelPal shows no amount at all instead of picking one.
New means waiting on you, Approved means live
NOBEDS marks a channel booking Approved. It leaves a direct order New until you accept it. TravelPal reads New as not yet yours. A guest whose order still waits in your queue is never greeted. That guest is never asked for a deposit and never sent a guest link. Approve the order in NOBEDS before you connect, and the stay is set up then. Approve it later and TravelPal picks it up at the next check, within about an hour. One gap is left. NOBEDS publishes no word for a canceled booking. A booking you cancel after you connect does not reach TravelPal today.
The conversation, in the order it happened
NOBEDS keeps one chat row for each exchange. The guest's line and the property's answer sit together under one timestamp. TravelPal splits each pair. It keeps the lines in the order they were said, not the order they arrive in. A stay that is already half discussed carries on from where your team stopped. TravelPal reads an arrival time with the same care. NOBEDS writes midnight on a channel booking when the channel gave no hour. TravelPal reads that as no time given and uses the room's own check-in hour. It does not tell a guest they are expected at 00:00.
Room availability stays in NOBEDS
TravelPal does not read availability from NOBEDS. A NOBEDS room can have several copies of itself, which is how NOBEDS handles hostel dorms. Its calendar keeps your rates, minimum stays and closed to arrival or departure rules. Your team checks it when a guest asks about dates.
What TravelPal writes back to NOBEDS
Here is what TravelPal sends through NOBEDS today, and what it leaves to your team.
Messages into the guest's own chat box
NOBEDS has one send. It relays into the chat the guest already uses. That is the Booking.com thread, the Airbnb thread, or your direct engine chat. Your team reads the whole exchange in the same place as the booking.
Chat is the only way to send, so nothing is promised elsewhere
A NOBEDS booking has a guest email and phone number. But NOBEDS publishes no email or SMS send. So TravelPal never goes around the chat, and it never says a message went somewhere it cannot reach. One conversation, one place.
Sales settle on the guest link, and the booking is left alone
An extra clean or a damage waiver is offered and priced on the guest's own private link. The guest pays for it there too. The confirmation and the amount go to your team, see how upselling works. The NOBEDS booking stays exactly as you have it, because this API publishes no way to change one. On the Flat plan TravelPal takes no share of these sales, see what it costs.
Connected in four steps
You create the access details yourself, inside NOBEDS. TravelPal does the rest itself.
Generate the token in NOBEDS
Go to Developer API, then Generate New API Token. You make it yourself. There is no application to file and no partner review. Nobody at NOBEDS has to switch anything on for your account. The token covers one property, so a second NOBEDS property connects with its own token.
Paste the token into TravelPal
TravelPal checks it with a live read of your account the moment you save. NOBEDS reports a bad token as nothing found, not as a refusal. Only a real call can tell those apart. NOBEDS also puts this token in the address of every request, not in a header. Treat it like a password that travels. Keep it out of tickets and chat threads. If it ever lands somewhere public, generate a new one in NOBEDS.
Tell us your time zone
NOBEDS publishes no time zone on a room, on the account profile, or anywhere else. A country can also have more than one. So we set yours with you during setup and do not guess. Quiet hours, scheduled arrival messages, and upsell cutoffs all run on it.
Rooms and bookings import when you connect
Your rooms arrive in one pass. NOBEDS serves the whole list at once and has no second page. Each booking on them gets its own private link for the guest. The import reaches back well before today, because NOBEDS filters bookings by check-in date. A guest who checked in last week may still be in the room when you connect. That guest is picked up too.
TravelPal shows the connection at every step: connected, last update, and any error in plain words. To see the other setup steps, read what onboarding involves.
What the NOBEDS connection will not do
Know the limits of NOBEDS before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Chat reaches three of your channels, not all of them
NOBEDS documents its chat relay for Booking.com, Airbnb, and direct bookings. An Expedia, Agoda, Trip.com, or Hostelworld booking still arrives with its dates and guest details. So your team has the full picture. But TravelPal sends that guest nothing, because NOBEDS documents no relay for that channel. The send also reports back no message identifier, which is the other reason nothing is sent blindly.
TravelPal asks, because NOBEDS does not announce
This API has no push notification and no changed-since filter. The only way to learn that anything moved is to read the booking list. So TravelPal reads it: once when you connect, and once an hour after that for bookings it does not have yet. A booking made later is set up at the next check, within about an hour. What NOBEDS never says is that a booking is gone, so a booking removed in NOBEDS still reads as live here.
A booking can be created or removed, never edited
NOBEDS makes bookings and deletes them, and publishes nothing in between. So no update call exists to write anything onto the booking. TravelPal does not offer a paid late checkout on a booking that came from NOBEDS. Your calendar is left alone for a related reason. Closing a night here means sending that night's rate again. TravelPal will not rewrite a price you set.
One chat for everyone, and it names no author
Every message this API carries is relayed into the guest's chat. So the thread has no place for a line meant only for your team. Sale notes and anything held for a person go to your team by message and email instead. The history also records no sender. It only shows whether a line sat in the guest field or the answer field. So TravelPal never reads the property's side of an old thread as fact to learn from. It also cannot tell, from a reply with no sender, that your team already answered. So TravelPal does not answer in the NOBEDS chat, and your team does.
When TravelPal's AI is not sure, it stops and asks your team instead of guessing. This rule is the same on every system: see the safety guardrails.
NOBEDS integration FAQ
Does NOBEDS have to approve the connection first?
No. You make the token yourself under Developer API, then Generate New API Token. Last, paste the token into TravelPal. Nobody at NOBEDS has to switch anything on for your account, and there is nothing to apply for. One token covers one property. If you run more than one NOBEDS account, each connects with its own token.
Which of my channels can TravelPal actually reply on?
None today. TravelPal sends its own messages on Booking.com, Airbnb, and your direct bookings. Those are the chat channels NOBEDS names for its message relay. TravelPal puts a NOBEDS guest's reply in your team's TravelPal inbox and emails your team. Bookings from Expedia, Agoda, Trip.com, and Hostelworld still arrive with their dates and guest details. TravelPal does not message those guests. NOBEDS publishes no chat route to them, and a message sent that way would look delivered without arriving.
Will a paid late checkout change my NOBEDS booking?
No. NOBEDS creates and deletes bookings. It publishes no update call in between, so nothing on the booking can be moved from outside. So TravelPal does not offer a paid late checkout there. One of your people makes any change in NOBEDS.
How soon does TravelPal see a new booking?
Within about an hour. TravelPal reads your booking list when you connect, then once an hour after that. NOBEDS sends no notifications and has no changed-since filter. The first read reaches back well before today, so guests already mid-stay are picked up.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to NOBEDS in how widely they are used.
Updated
NOBEDS is a trademark of its owner. TravelPal is not affiliated with or endorsed by NOBEDS.