Guest messaging and upsells for Magarental accounts
TravelPal connects to Magarental with the API key from your own user profile, then answers guests in the Booking.com and Airbnb chats Magarental carries for you. It reads your properties, your bookings and every revision of them, the chat history on each one, and the room amounts underneath the total. Connect Magarental only if it is the channel manager you hold and run yourself: if your reservations are created in a property management system that pushes into Magarental, connect that system instead.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from Magarental
Magarental sells itself as a connectivity platform for reaching the channels, so the account worth connecting here belongs to a vacation rental company that holds the Magarental subscription itself and runs no property management system above it.
Properties arrive with their address and their clock
Magarental puts the title, address, coordinates, time zone, description and photos on the property rather than on the rooms inside it, so the property is what becomes a property here, in the photo order you set. That time zone is the one every scheduled message runs on. A vacation rental account, where one property is one unit, maps one to one; a building filed as a single property with several room types arrives as a single property.
Bookings, and every revision of one
Magarental treats a booking as the latest of its revisions, so a change arrives as a new revision while the booking's own identity stays put. TravelPal follows the booking, and a guest who moves their dates keeps one stay, one guest link and one conversation instead of gaining a second of each. Magarental calls a live booking new or modified and never confirmed or pending, so a stay counts from its first revision with no approval state to wait on.
The chat, oldest message first
Magarental addresses a conversation by the booking itself, so there is no separate thread to hunt for, and every message in it is typed as the guest's or as the property's side. TravelPal reads it oldest message first, which is what lets it pick up a stay mid-conversation rather than reopening what your team already settled. See how the messaging works.
Guest language and the code on the guest's confirmation
The booking carries the guest's language, so the first reply is already in it. It also carries the channel's own reservation code, the number printed on the guest's Booking.com or Airbnb confirmation, which is the only one worth reading back to them. Magarental publishes no customer identity of its own, so a returning guest is matched from their own details and history rather than handed to us pre-linked.
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 accommodation price TravelPal works from is the room itself, in the booking's own currency and 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, because nothing about answering a guest needs it.
What TravelPal writes back
Every message goes out through Magarental, never around it, so your own inbox shows exactly what each guest was told.
Replies land in the channel thread the guest opened
The one place Magarental can put a message is the Booking.com or Airbnb chat attached to the booking, so that is where TravelPal answers. Your team keeps reading the same thread in Magarental, and the guest never leaves the app they booked in.
Upsells offered and closed in that same thread
TravelPal offers at your prices in the Booking.com or Airbnb chat, 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 make real rather than being rewritten underneath them.
A booking change is acknowledged once it is actually saved
Magarental keeps re-serving a change until it is told the change is stored, and 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 that warning email is not one you collect.
Connected in four steps
Magarental switches API access on for your account, and TravelPal does the rest itself.
Create the key in your Magarental profile
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. The key Magarental issues is a standing one with no expiry and no daily budget behind it, so a mistyped paste costs a retype and nothing more.
Properties import, bookings follow
Your properties become properties, past bookings backfill by arrival date, and every booking from then on gets its own private guest link. Booking.com and Airbnb stays arrive with their chat history attached.
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 Magarental connection will not do
Every property management system draws its own lines, and the ones Magarental draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
Only Booking.com and Airbnb guests can be reached
Magarental's chat covers those two channels and no others, and it carries no email, SMS or WhatsApp send of any kind. An Expedia booking still arrives with its dates, guest details and room amounts, and TravelPal leaves that guest alone rather than recording a message nobody ever got. If most of your volume sits outside Booking.com and Airbnb, 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 carry a notes field, but it holds the channel's own text about the guest and nothing writes to it. With one rail on this connection and the guest reading it, sale notes and anything TravelPal holds for a person go to your team channel and by email instead.
Arrival and departure times are not TravelPal's to set
Magarental publishes an arrival hour on a booking as something to read and no way to set one, publishes no departure time at all, and its only booking write moves a guest to a different room. So a paid late checkout is confirmed to the guest and handed to your team to make real, and TravelPal never claims a reservation change it cannot perform.
Availability is counted by room type, so extra nights are not sold
Magarental's calendar answers how many rooms of a type are left on a date, not whether one guest's own unit is free. Two rooms of a type with one still open reads as available for a guest whose room is not, which is exactly how a night gets sold twice. TravelPal does not read that calendar and does not sell an added night on this connection.
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.
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. If your reservations are created in a property management system that pushes availability and rates into Magarental, connect that system instead: that is where your check-in times, your guest record and your reservation changes live, and 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, and there is no email, SMS or WhatsApp send on it 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, on any account with an active subscription, but Magarental then opens production API access account by account after a check of its own, which 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 as something to read rather than something to set, publishes no departure time at all, and its only booking write moves a guest to a different room. A sold late checkout or early check-in is confirmed to the guest in the Booking.com or Airbnb thread and passed to your team, so the change is made once, by a person who meant it.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest Magarental in how widely they are used.
Updated