Guest messaging and upsells for Magarental accounts
TravelPal uses the API key from your Magarental profile to read your Booking.com and Airbnb guest chats. Connect Magarental only if you run it yourself as your channel manager.
One Magarental connection works in both directions. Each item is explained below.
What TravelPal reads from Magarental
Magarental describes itself as a connectivity platform for reaching the booking channels. The account to connect here belongs to a vacation rental company. It holds the Magarental subscription itself and has no property management system above it. If your bookings are created in a property management system that pushes into Magarental, connect that system instead.
Properties arrive with their address and their time zone
Magarental puts the title, address, coordinates, time zone, description and photos on the property. It does not put them on the rooms inside it. So the property is what becomes a property here, with the photos in the order you set. That time zone is the one every scheduled message uses. In a vacation rental account, where one property is one unit, each property maps to one unit. A building filed as one property with several room types arrives as one property.
Bookings, and every revision of one
Magarental treats a booking as the latest of its revisions. A change arrives as a new revision, and the booking keeps the same identity. TravelPal follows the booking. So a guest who moves their dates keeps one stay, one guest link and one conversation. They do not get a second of each. Magarental calls a live booking new or modified, never confirmed or pending. A stay counts from its first revision, with no approval state to wait for.
The chat, oldest message first
Magarental addresses a conversation by the booking itself, so there is no separate thread to find. Every message in it is marked as the guest's side or the property's side. TravelPal reads it oldest message first. See how the messaging works.
Guest language and the code on the guest's confirmation
The booking carries the guest's language, so TravelPal knows it before the guest writes. It also carries the channel's own booking code. That is the number printed on the guest's Booking.com or Airbnb confirmation. It is the only one worth reading back to them. Magarental publishes no customer identity of its own. So TravelPal does not remember a guest who books again.
Room amounts come in, card details do not
Magarental keeps the room amounts apart from service lines such as city tax, VAT and breakfast. So the price TravelPal works from is the room amount alone. It stays in the booking's own currency and is never converted. The same booking also carries the guest's card, down to the balance on a Booking.com virtual card. TravelPal drops that on the way in and never stores it. Answering a guest does not need it.
What TravelPal writes back to Magarental
Here is what TravelPal sends through Magarental today, and what it leaves to your team.
Your team replies in the Magarental chat
The only place Magarental can put a message is the Booking.com or Airbnb chat attached to the booking. Magarental sends TravelPal no notice when your team replies there. So TravelPal does not answer in that chat, because a person may have answered already. Your team gets each guest message by email and in the TravelPal inbox.
Upsells offered and closed on the private page
TravelPal offers at your prices on the guest's private page. It takes the yes there and confirms it there. See what it sells. Magarental publishes no way to write a time or a date onto a booking. So the arrangement goes to your team to carry out. TravelPal does not rewrite the booking under them.
A booking change is acknowledged once it is actually saved
Magarental keeps sending a change again until it is told the change is stored. After thirty minutes it emails the account a warning that one is still outstanding. TravelPal acknowledges each change only after the stay is saved on our side. So a booking is never marked received and then lost, and you do not get that warning email.
Connected in four steps
Magarental turns on API access for your account. TravelPal does the rest itself.
Create the key in your Magarental profile
Go to Magarental, then your user profile, then API keys. The account needs an active subscription before a key can be created. One key covers every property, so there is nothing to repeat per unit.
Ask Magarental to turn production access on
Magarental opens production API access account by account, after a check it runs itself. So your account needs switching over before it carries live traffic. That is one note to your Magarental contact and a call we join. Their staging environment is self-signup. So your connection can be built and watched on test data in the meantime.
Paste the key into TravelPal
Wrong credentials are refused on the first read. So a mistyped paste costs a retype and nothing more.
Properties import, bookings follow
Your properties become properties, and past bookings are loaded by arrival date. Every booking from then on gets its own private guest link. Booking.com and Airbnb stays arrive with their chat history attached.
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 Magarental connection will not do
Know the limits of Magarental before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Only Booking.com and Airbnb guests can be reached
Magarental's chat covers those two channels and no others. It carries no email, SMS or WhatsApp send of any kind. An Expedia booking still arrives with its dates, guest details and room amounts. TravelPal leaves that guest alone, rather than record a message nobody got. Most of your volume may be outside Booking.com and Airbnb. Then the system that holds those reservations is the better connection.
No line on a booking that only your team can see
The only write against a conversation posts into the channel thread the guest is reading. So there is nowhere in Magarental to leave a note for your own people. The booking does have a notes field. It holds the channel's own text about the guest, and nothing writes to it. This connection has one place to write, and the guest reads it. So sale notes go to your team in a message and by email instead. So does anything TravelPal holds for a person.
Arrival and departure times are not TravelPal's to set
Magarental publishes an arrival hour on a booking to read, with no way to set one. It publishes no departure time at all. Its only booking write moves a guest to a different room. So no paid late checkout is offered on a booking that came from Magarental. TravelPal never claims a booking change it cannot make.
Availability is counted by room type, so extra nights are not sold
Magarental's calendar tells you how many rooms of a type are left on a date. It does not tell you whether one guest's own unit is free. Say two rooms of a type exist and one is open. It reads as available for a guest whose room is not. That is how a night gets sold twice. TravelPal does not read that calendar and does not sell an added night on this connection.
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.
Magarental integration FAQ
Should I connect Magarental or the system my bookings are created in?
Connect Magarental only if it is the channel manager you hold and run yourself. Your reservations may be created in a property management system that pushes availability and rates into Magarental. Then connect that system instead. Your check-in times, your guest record and your reservation changes live there. Magarental keeps carrying the channel traffic underneath it either way.
Which guests can TravelPal actually message through Magarental?
Booking.com and Airbnb guests. Those are the only two channels Magarental's chat covers. It has no email, SMS or WhatsApp send at all. An Expedia booking still arrives with its dates, guest details and room amounts. So you see the stay in TravelPal. But nothing is offered, priced or scheduled for a guest who cannot be reached.
Do I need Magarental's permission to connect TravelPal?
Partly. You make the API key yourself, in your user profile under API keys. Any account with an active subscription can do this. Then Magarental opens production API access account by account, after a check of its own. That is one note to your account contact and a call we join. Their staging environment is self-signup. So your connection can be built and watched on test data in the meantime.
Can TravelPal change a booking in Magarental?
No, and it does not pretend to. Magarental publishes a booking's arrival hour to read, not to set. It publishes no departure time at all. Its only booking write moves a guest to a different room. So TravelPal offers no paid late checkout or early check-in on a booking that came from Magarental. Any change is made by a person who meant it.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to Magarental in how widely they are used.
Updated
Magarental is a trademark of its owner. TravelPal is not affiliated with or endorsed by Magarental.