AI guest messaging for AvaiBook by idealista
TravelPal answers your AvaiBook guests in the conversation AvaiBook keeps on each booking. It also sells paid extras there, at your prices.
One AvaiBook by idealista connection works in both directions. Each item is explained below.
What TravelPal reads from AvaiBook by idealista
Property management companies in Spain, Portugal and Italy use AvaiBook. It gives them a channel manager, a booking engine and card payments from one vendor, idealista.
Units, not just accommodations
AvaiBook books a unit inside an accommodation. An accommodation with five bookable units becomes five properties in TravelPal. Each one is named for its unit and has its own calendar and its own guests. Check-in and check-out times, descriptions, each unit's capacity and minimum stay, and photos come across too. Two things are left out on purpose. One is AvaiBook's features list, because AvaiBook publishes no key that explains what its entries mean. The other is its booking conditions text, because that is your cancellation contract, not your house rules. Telling a guest a cancellation clause as a house rule is worse than saying nothing. Put both in your knowledge base, where you control the words.
Bookings, and only the ones that are already stays
AvaiBook has four booking states, and two of them are not a stay yet. One waits for you to accept an on-request booking. The other waits for the guest's money. TravelPal gives a concierge to confirmed bookings and holds the rest until they become stays. Every booking also says where it came from. A booking from your own site, your booking engine or the AvaiBook app counts as direct. A partner booking does not. AvaiBook writes the partner's name as free text, not from a fixed list. So TravelPal records the channel exactly as AvaiBook spells it.
One history per booking, three fields per message
AvaiBook keeps one message history on each booking. Every message in it has three parts: a date, which side sent it, and the text. There is no subject and no author name. TravelPal reads the whole history in order before it writes anything. So a concierge that joins a stay halfway does not ask a guest something your team answered yesterday.
Unit calendars stay in AvaiBook
TravelPal does not read availability from AvaiBook. Its calendars mark date ranges, and do not say which are bookings and which are your blocks. Your team checks the calendar in AvaiBook.
What TravelPal writes back to AvaiBook by idealista
Every message goes out through AvaiBook by idealista, never around it. So your AvaiBook by idealista inbox shows exactly what each guest was told.
One send surface, whatever the guest booked on
AvaiBook has one way to reach a guest: post in the booking conversation. TravelPal uses only that. It adds no side email and no SMS of its own. So everything a guest was told sits in the AvaiBook record your team already reads. AvaiBook decides how a message travels. Its own Airbnb documentation says a reply written in AvaiBook arrives in the guest's Airbnb thread. AvaiBook allows at most 3,200 characters in a message. So answers are written to fit and do not arrive cut in half.
Sales arrive with the unit named
A guest who buys an extra clean or a damage waiver pays on their own private link. The sale reaches your team with the accommodation and the unit inside it. An AvaiBook booking has no charges, extras or line items. So the money never shows on the booking record, and TravelPal does not pretend it does. On the Flat plan TravelPal takes no cut either: what upsells earn is yours.
Connected in four steps
AvaiBook by idealista turns on API access for your account. TravelPal does the rest itself.
Ask AvaiBook to switch API access on
AvaiBook grants access account by account, so you start with one email to your AvaiBook contact. They set you up in their pre-production environment first and email you the credentials. Then they run their technical check and switch the key on against your live account. AvaiBook publishes a reply time of 24 to 72 hours on that first email.
Mint a full-access key, not the narrow one
The account holder creates the key on AvaiBook's API tools page. AvaiBook offers two scopes: full access, or rates and availability only. Choose full access. The narrow key connects, passes every check and imports your accommodations without a problem. Then it refuses every guest message. Nobody finds this until a guest is waiting.
Paste the key into TravelPal
There is one field for the key. There is also an optional address. Use it to point at AvaiBook's pre-production environment and watch a real thread before it touches live guests. A mistyped paste costs a retry and nothing else.
Units import, and your local time is set with you
Your accommodations and their units become properties. Every booking made before you connect gets its own private guest link. AvaiBook publishes no time zone on a property. So we confirm the local zone with your team on that same call, before anything is scheduled.
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 AvaiBook by idealista connection will not do
Know the limits of AvaiBook by idealista before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
A booking cannot be edited once it exists
An AvaiBook booking can be created, confirmed or rejected, and that is the whole list. So TravelPal writes nothing onto an AvaiBook booking. It offers no paid late checkout or extra night on a booking that came from AvaiBook. A person makes any change in AvaiBook.
AvaiBook publishes no time zone for a property
Their property record has the address, the city, the region, the country and the coordinates, and nothing more. Nothing should be scheduled from a guessed zone. So your local time is set with your team when you connect. It decides quiet hours and when a good-morning message goes out.
Nothing is announced, so TravelPal goes and looks
AvaiBook has no event feed. Nothing tells TravelPal that a booking was made or that one moved. So TravelPal checks for itself. It reads your bookings when you connect, and then looks once an hour for bookings it does not have yet. A booking made after you connect is set up at the next check, within about an hour. TravelPal also reads the bookings it already holds, in turn. So a change to a stay that has not ended yet is picked up too. Guest messages are found the same way, on a schedule. A guest is answered at the next check, not the second they write. AvaiBook can list bookings by check-in date and by creation date. It has no way to ask what changed since yesterday.
Your team's replies and ours look the same
AvaiBook marks a message as from the guest or from the property side, and adds no author name. So a reply typed in AvaiBook by one of your people looks the same as a TravelPal reply. This has two results, and both are on purpose. First, a thread goes to a person by your own rules and quiet hours. The AI does not notice a colleague mid-thread. Second, AvaiBook has no line in the conversation that the guest cannot see. So held questions and sale notes reach your team in your own channel and by email instead.
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.
AvaiBook by idealista integration FAQ
Do I need AvaiBook's permission to connect TravelPal?
Yes, and it is one email. AvaiBook turns API access on account by account. They set you up in their pre-production environment and email you the credentials. They run their technical check. Then they switch the key on against your live account. AvaiBook publishes a reply time of 24 to 72 hours on that first contact. Your account holder creates the key afterward, on AvaiBook's own API tools page.
Which AvaiBook API key should I create?
The full-access one. AvaiBook lets you limit a key to rates and availability only. That key works fine when you connect: it signs in, and every accommodation and unit imports. Then it refuses every guest message. Nothing in the import will warn you, so choose full access when you create the key.
My accommodation has several rooms. Does that work?
Yes. AvaiBook books a unit inside an accommodation, and TravelPal does the same. Each bookable unit becomes its own property with its own guest and its own thread. Five rooms under one roof are five stays, never one shared conversation.
Can TravelPal move a checkout time on an AvaiBook booking?
No. AvaiBook bookings can be created, confirmed and rejected. There is no update call, so nothing connected to AvaiBook can rewrite one. TravelPal does not sell a late checkout on a booking that came from AvaiBook either. One of your people makes any schedule change in AvaiBook, so a person stays in control of it.
Does connecting AvaiBook cost extra?
Not beyond the flat monthly price. AvaiBook books a unit, not a building, and TravelPal runs one concierge per unit. So a unit is what you pay for on the bill.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to AvaiBook by idealista in how widely they are used.
Updated
AvaiBook by idealista is a trademark of its owner. TravelPal is not affiliated with or endorsed by AvaiBook by idealista.