TravelPal for Pxsol hotels
TravelPal reads your Pxsol hotels and bookings, but it cannot hear or answer guests on Pxsol yet. It connects with one API key, a kind of password you create yourself.
TravelPal does not reply to guests in Pxsol yet. Your team does. Each item is explained below.
What TravelPal reads from Pxsol
Independent hotels across Latin America use Pxsol, especially in Argentina. Pxsol says it is in more than 1,800 properties.
A Pxsol hotel becomes one property
TravelPal reads the hotel's name, address, coordinates, description, photos, amenities, and check-in and check-out times. TravelPal stores these facts on the property. Pxsol keeps room types as a separate record. One booking can hold up to five rooms of different types. So a forty-room hotel arrives as one property, not forty.
Bookings arrive because TravelPal asks
Pxsol does not tell other software about a booking. Its live updates are made for its own screens, in a browser. So TravelPal sweeps Pxsol: it asks on a schedule for each hotel's new or changed bookings. The first sweep covers the last 370 days, the longest period Pxsol documents.
Seven Pxsol statuses and how TravelPal reads each one
Confirmed, checked in, and checked out all count as an active stay. Pending stays pending and does not count as booked. A cancellation stops TravelPal, and so does a no-show. A guest who is not coming should not keep getting messages. Pxsol itself sends the seventh status and calls it unknown. TravelPal will not greet anybody on that status. It marks that stay for your team and does not guess.
Local time comes from the hotel record
Pxsol stores a time zone on each hotel, written in full, like America/Argentina/Mendoza. TravelPal uses it for quiet hours and for the time limits on paid extras (upsells). A time difference alone, such as -03:00, is not accepted as a time zone. A time difference does not follow daylight saving time. A clock that is one hour wrong makes every time limit wrong too.
What TravelPal writes back to Pxsol
Here is what TravelPal sends through Pxsol today, and what it leaves to your team.
Pxsol keeps a reply on the guest's own channel
Pxsol's send call takes only the words of a reply. Pxsol takes the platform, the company, the receiver, and the author from the conversation. So a WhatsApp guest stays on WhatsApp, and a widget guest stays on the widget. TravelPal cannot move a guest from one channel to another, and it does not try. Today TravelPal cannot find a guest's Pxsol conversation, so it sends nothing. See how guest messaging works.
Every reply shows the Pxsol user you chose
A Pxsol API key acts as the user it is attached to. Each message sent with the key also assigns the conversation to that user. The colleague who had the conversation loses it. So make a Pxsol user only for TravelPal before you make the key. Then a message sent with the key shows the TravelPal user. No colleague's name appears on a message they did not write.
A message counts as sent only when Pxsol says so
Pxsol marks each message sent with the key as sent or failed. The common cause of failed is the WhatsApp 24-hour window. It closes when a guest has not written for a day. TravelPal records only what Pxsol confirms. So a message nobody received never appears in your history as delivered.
TravelPal sends each message only once
Pxsol gives no way to mark two identical conversation messages as one. So if a reply is sent again, the guest gets it twice. TravelPal sends once. When Pxsol reports a failure, the conversation goes to your team. TravelPal does not try again.
Connected in four steps
You create the access details yourself, inside Pxsol. TravelPal does the rest itself.
Create a Pxsol user for TravelPal
The key you are about to make acts as a Pxsol user. Pxsol records every action the key takes under that user's name. So make a user only for TravelPal first. Then your inbox and your activity record both show what TravelPal did.
Make the key
In Pxsol, go to Integrations, then Integraciones Generales (API Keys), then Create API Key. Give the key hotel-read, booking-read, and conversation-write. You select these abilities for each key. If one is missing, Pxsol refuses the key when TravelPal uses it, not when you paste it. So check your choices twice. Pxsol shows the token, the text of the key, only once.
Paste it into TravelPal
The key goes in a single field. When you save, TravelPal checks the key against your hotel list. The key stays the same. TravelPal sends it with every request, exactly as Pxsol gave it. So no new token is made, and nothing is renewed on a schedule. The second field, for the environment, is optional. Leave it empty for production, your live account. Type staging to use Pxsol's staging gateway.
Hotels import, then the sweep begins
Every hotel your key can see becomes a property. Its description, photos, amenities, and check-in times are already filled in from Pxsol. From then on, TravelPal checks each hotel for new or changed bookings. See what it costs.
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 Pxsol connection will not do
Know the limits of Pxsol before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Pxsol has its own channels, not a travel site's inbox
Pxsol conversations run on WhatsApp, Facebook, Instagram, the website widget, and email. Pxsol has no Airbnb or Booking.com inbox to answer in. Pxsol also does not tell other software where a booking came from. A guest may book on a travel site and write inside it. That guest stays with your team, in that site's inbox. Writing to that guest somewhere else is a different act, not a backup plan. TravelPal will not make that choice for you.
TravelPal cannot answer or start a Pxsol conversation yet
Pxsol documents no way to find a guest's conversation from their booking. When TravelPal reads a booking, Pxsol never returns a phone number. So TravelPal cannot find the guest's conversation to write in. Pxsol also sends TravelPal no guest messages. So TravelPal does not answer a guest who writes first either. This connection does not send a scheduled first message to a guest who has never written.
A whole hotel is a single property
One Pxsol booking can hold several rooms of different types. So the hotel is the only place a stay can belong to. The hotel arrives with one check-in time, one check-out time, and one time zone. What you write for that property is written once, for the whole building. Room types are not separate places. So TravelPal cannot tell a suite guest something different from a standard double guest.
Nothing a guest buys is written on the Pxsol booking
Pxsol's booking actions are cancel, change state, add a memo, attach a card, and send a message. None of them moves a stay's dates, or its arrival and departure times. Pxsol gives availability by room type and rate plan, not by property. So TravelPal does not give a guest a night's price from Pxsol. It does not write a late checkout on the booking. TravelPal offers no paid late checkout on a booking that came from Pxsol.
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.
Pxsol integration FAQ
Do I need Pxsol to turn anything on before TravelPal can connect?
No. You create the API key yourself, under Integrations and then Integraciones Generales (API Keys). Do two things in order. First, create a Pxsol user only for TravelPal, because the key acts as that user. Then give the key hotel-read, booking-read, and conversation-write when you make it. Pxsol shows the token only once.
Which guests can TravelPal answer on Pxsol?
None yet. Pxsol sends TravelPal no guest messages, and TravelPal cannot find a guest's conversation from a booking. Pxsol carries no Airbnb or Booking.com messages. A guest who booked on a travel site may write inside that site. Your team answers that guest in the site's own inbox.
Will my team see what TravelPal told a guest?
Not yet, because TravelPal sends no Pxsol messages today. It cannot find a guest's conversation. A message sent with your key would sit in your Pxsol inbox. It shows the user your key belongs to and is assigned to that user. Pxsol has two places a guest cannot see: the booking memo and the message that emails the hotel. Both use the booking number, and a conversation has its own, unrelated number. So TravelPal does not write a team note into the conversation. Your team gets a message and an email about a sale, and about anything held for a person.
How does TravelPal find out about a new reservation in Pxsol?
It asks. Pxsol sends no updates to other software. So TravelPal checks each hotel your key can see for new or changed bookings. A check can cover the last 370 days, the longest period Pxsol documents. A far-future booking made before that, and never changed since, is found only when it changes.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to Pxsol in how widely they are used.
Updated
Pxsol is a trademark of its owner. TravelPal is not affiliated with or endorsed by Pxsol.