AI guest messaging for NOBEDS guesthouses and hostels
TravelPal answers your NOBEDS guests in the chat attached to their booking, on Booking.com, on Airbnb, and through your own direct engine. You connect it with a single API token you generate yourself in NOBEDS, and it reads your rentals, your bookings, your availability, and the conversation already sitting on each booking. NOBEDS gives a conversation no record of its own, so the booking is the thread, and every answer reads back on the booking your team already has open.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from NOBEDS
NOBEDS is run by guesthouses, small hostels, and independent hosts, usually one property with its rooms under it, and it is a Lithuanian product whose home market is the Baltics.
Your rooms, minus the door code
NOBEDS calls a unit a rental, and one account is one property with its rooms under it. TravelPal takes the title, description, photos, the unit type, how many it sleeps, and your check-in and check-out hours, then fills in the address, city, and currency from your account profile, because a room carries none of its own. NOBEDS also gives you a field on the rental where properties keep smart lock PINs and wifi passwords: TravelPal leaves that one out of what the concierge can read from, so an access code reaches a guest under your rules and not before, see how access is handled.
Bookings, with the channel and the guest's own reference
An order, which is what NOBEDS calls a booking, arrives with its dates, nights, party size, guest name, email, phone, and the referral behind it: Airbnb, Booking.com, Expedia, Agoda, Trip.com, Hostelworld, or your direct engine. The concierge quotes back the channel's confirmation code, the one printed on the guest's Booking.com email, rather than the internal order number. Money is reported in your account currency, and where an account lists more than one, TravelPal reports no amount at all instead of picking one.
New means waiting on you, Approved means live
NOBEDS marks a channel booking Approved and leaves a direct order New until you accept it. TravelPal reads New as not yet yours, so a guest whose order is still sitting in your queue is never greeted, never asked for a deposit, and never sent a guest link. Approve it in NOBEDS and the stay is provisioned on the next sweep. NOBEDS publishes no word for a canceled booking either, so when a booking stops reading as one of those two, TravelPal stands the stay down rather than keep talking to a guest who may not be coming.
The conversation, in the order it happened
NOBEDS keeps one chat row per exchange, the guest's line and the property's answer together under a single timestamp. TravelPal splits the pair and holds them in the order they were said rather than the order they arrive in, so a stay that is already half discussed carries on from where your team left it. An arrival time is read the same careful way: NOBEDS writes midnight on a channel booking when the channel never stated an hour, so TravelPal takes that as no time given and works from the room's own check-in hour rather than telling a guest they are expected at 00:00.
Availability by room, dorm beds included
A NOBEDS room can have several of itself, which is how it handles hostel dorms, so availability comes back as a count of what is left plus whether the night is closed, alongside your rate, minimum stay, and any closed to arrival or closed to departure rule. A night NOBEDS does not answer for is treated as unknown rather than free, so nothing is ever offered on a bed that may already be sold.
What TravelPal writes back
Every message goes out through NOBEDS, never around it, so your own inbox shows exactly what each guest was told.
Replies into the guest's own chat box
NOBEDS has one send, and it relays into the chat the guest is already using: the Booking.com thread, the Airbnb thread, or your direct engine chat. Because the booking is the thread, everything said sits on the booking itself, so your team reads the exchange in the same place they read the reservation.
Chat is the only rail, so nothing is promised elsewhere
A NOBEDS booking carries a guest email and phone number, but NOBEDS publishes no email or SMS send, so TravelPal never routes around the chat and never claims a message went out somewhere it cannot reach. One conversation, one place.
Sales settle on the guest link, and the booking is left alone
A late checkout or an extra bed is offered, priced, and paid for on the guest's own private link, and the confirmation and the amount go to your team, see how upselling works. The NOBEDS booking itself stays exactly as you have it, because this API publishes no way to change one. TravelPal takes no commission on any of it, see what it costs.
Connected in four steps
The credentials are yours to create inside NOBEDS. TravelPal does the rest itself.
Generate the token in NOBEDS
Developer API, then Generate New API Token. You make it yourself: no application to file, no partner review, and 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.
Paste the token into TravelPal
It is checked with a live read of your account the moment you save, because NOBEDS reports a bad token as nothing found rather than as a refusal, and only a real call can tell those apart. NOBEDS also carries this token in the address of every request rather than in a header, so treat it like a password that travels: keep it out of tickets and chat threads, and generate a fresh one in NOBEDS if it ever lands somewhere public.
Tell us your time zone
NOBEDS publishes no time zone on a room, on the account profile, or anywhere else, and a country can span more than one, so we set yours with you during setup instead of guessing. Quiet hours, scheduled arrival messages, and upsell cutoffs all run on it.
Rooms import and the sweep starts
Your rooms arrive in one pass, because NOBEDS serves the whole list at once and publishes no second page to walk, and each booking on them is given a private link of its own for the guest. The first sweep reaches back well before today, since NOBEDS filters bookings by check-in date, so the guest who checked in last week and is standing in the room the day you connect is picked up too.
The dashboard shows the connection the whole way: connected, last sync, and any error in plain words. The rest of going live is covered in what onboarding involves.
What the NOBEDS connection will not do
Every property management system draws its own lines, and the ones NOBEDS draws are worth knowing before you switch anything on. TravelPal works inside them rather than 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 rather than posting into a channel with no relay behind it. The send reports back no message identifier either, which is the other reason nothing is fired blindly.
TravelPal asks, because NOBEDS does not announce
This API has no push notification and no changed-since filter, so the only way to learn that anything moved is to sweep the booking list. A booking made a minute ago is known on the next sweep rather than the second it happens, and a same-day change made in NOBEDS reaches the concierge the same way.
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 carry a sold time back onto the record. A paid late checkout is confirmed to the guest and handed to your team with the time on it, and somebody on your side moves it in NOBEDS. Your calendar is left untouched for a related reason: closing a night here means resending that night's rate, and TravelPal will not rewrite a price you set.
One rail for everyone, and it names no author
Every message this API carries is relayed into the guest's chat, so there is nowhere in the thread for a line meant only for your team. Sale notes and anything held for a person go to your team channel and by email instead. The history records no sender either, only 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, and it never concludes from an unattributed reply that a colleague has picked the stay up. Handover runs on the rules and quiet hours you set.
Where the AI is not sure, it stops and asks your team rather than guessing. That is the same on every system: see the guardrails.
NOBEDS integration FAQ
Does NOBEDS have to approve the connection first?
No. You generate the token yourself under Developer API, then Generate New API Token, and paste it 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, so if you run more than one NOBEDS account, each connects on its own token.
Which of my channels can TravelPal actually reply on?
Booking.com, Airbnb, and your direct bookings. Those are the chat channels NOBEDS names for its message relay. Bookings from Expedia, Agoda, Trip.com, and Hostelworld still arrive with their dates and guest details, so your team sees them in context, but TravelPal does not message those guests, because 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 and publishes no update call in between, so nothing on the record can be moved from outside. The guest pays on their private link, the sale reaches your team with the new time on it, and one of your people makes the change in NOBEDS. Every reply and every offer still happens inside the NOBEDS chat.
How soon does TravelPal see a new booking?
On its next sweep of your booking list. NOBEDS sends no notifications and offers no changed-since filter, so TravelPal asks rather than waiting to be told. The first sweep after you connect reaches back well before today as well, so guests already mid-stay are picked up rather than missed.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest NOBEDS in how widely they are used.
Updated