Vrbo Partner Connection and Hospitable Tasks! June 15, 2026

I have completed this upgrade and have encountered nothing but problems.  I sent help requests to both Hospitable and VRBO on Friday and here 4 days later I have not hear back from either.  Is there a way I can undo this and go back to the chrome extension?  It was better and far more reliable.

• I completed the conversion and 2 of my 8 VRBO lstings will not republish.  They ae hung in limbo and have not been active now going on four days while I wait for someone to assist.
• I am no longer getting timely notifications from VRBO (if any) of booking requests or messages received.  If they do end up coming through they are hours and hours later.
• I did not have VRBO instant book turned on so I have to accept reservation requests.  I have accepted three and after they are accepted in Hospitable it is taking hours and hours for VRBO to process them as booked.  It looks like they are only doing a a daily update at 2am.  I have had guests reaching out confused because my message says the reservation is confirmed, but what they see on VRBO says it is still pending/requested many hours later and they don’t understand.   

Hosts do yourself a favor and wait for these bugs to be worked out first.  If you make this change an encoutner issues you will be on your own since it has been 4 days and no word back from either support team.

Hello. I also want to report an issue with VRBO notifications as raised by Mqreynolds above. When I first integrated Hospitable and VRBO, I was notified of my first VRBO booking inquiry immediately via Hospitable push notification. Since then, I have not received any notification when VRBO booking inquiries are received. I only see the inquiries when I log into my Hospitable inbox of my own volition. This issue most recently happened with a VRBO booking inquiry today, June 18th, that sat in my inbox for 4 hours with no notification. I submitted a support ticket with the res id #. Can someone assist and/or provide an update on this issue? 

I have the same issue . It has been a week now . My vrbo is now in limbo . I can’t see Vrbo calendar from Vrbo because it now says the calendar is managed by hospitable , and I can’t see my Vrbo calendar from hospitable because it is not synced and it is not showing up on hospital. Now I can’t do anything . This update sucks and there is no support . I can’t get a hold on anyone . I am about to jump to Guesty instead 

I am seeing a serious Vrbo integration/payment issue and need Hospitable to clarify if this is expected behavior or a known problem.

For a current Vrbo reservation, the guest has already checked in, but I have not received the normal payment/payout notification for the primary reservation amount. Before the integration changes, I typically received Vrbo payment notifications a couple of days before guest arrival.

What makes this especially concerning is that an added pet fee payment processed immediately, while the primary reservation payment/payout notification appears delayed or missing. So the add-on payment seems to be flowing, but the main reservation payout is not showing as expected.

I also contacted support about this issue, and the Hospitable/Smarty response appears to have posted into the guest-facing Vrbo message thread through the Vrbo/HomeAway masked email chain. This was an internal support/payment question, not guest communication.

Can someone from Hospitable please confirm whether this is a known Vrbo integration issue and how hosts should urgently verify the true payment status for Vrbo reservations after guest check-in?

Clarification: I have not completed the new Vrbo Partner Connection yet. I am still on the legacy Vrbo connection.

That is part of my concern. I am already seeing Vrbo/Hospitable routing and payout-notification issues under the legacy setup, including a primary reservation payout notification not arriving after guest check-in while an added pet fee payment notification came through immediately.

This makes me hesitant to proceed with the new Partner Connection until I understand whether this is a Vrbo notification issue, Hospitable sync issue, masked-email routing issue, or an actual payout processing problem.

Is anyone not getting notifications for new vrbo booking that come in?  I see I have received a booking but the initial vrbo notification and also checkpoint hospitable notification are not coming through at all?

Just reaching out here to see if the VRBO integration has “smoothed out” yet.  We are very reluctant to start the integration process after what I’ve seen on the Community Forums.  I understand any time a change or new process is made, there are bound to be some bumps in the road and I just want to wait until the potholes are filled!

(FWIW, we are currently on the “Legacy” connection, as some of our VRBO listings are apparently adequately “antique” -- i.e. from when they were “HomeAway”). 

Word of caution as I posted this when first announced but never received an answer in the main thread:

 

I received an answer from the support bot on this and need a human to confirm it in writing, because it directly affects damage coverage across my XXX unit portfolio and the Partner Connection migration is hard to reverse.

The bot told me: Hospitable's included damage protection is Direct Premium only and does not cover Vrbo; Hospitable Security Deposits are not available for Vrbo; and for Vrbo I would "continue using Vrbo's own refundable damage deposit and channel-level (Generali) protection."

My concern is the mechanics. Under the Partner Connection, Hospitable becomes Merchant of Record and Vrbo stops processing guest payments. Vrbo's refundable deposit hold and Generali protection were built around Vrbo processing the card. So please confirm, specifically and on record:

1. With Hospitable as Merchant of Record, does Vrbo's refundable damage deposit still actually collect, hold, and release on the guest's card? If Vrbo no longer touches the card, what mechanism authorizes and releases the $1,500 hold?

2. Does Vrbo's Generali-underwritten guest damage protection remain in force on reservations where Hospitable is the payment processor? Yes or no.

3. If a guest causes damage on a Vrbo reservation after I migrate, exactly who do I file the claim with — Vrbo or Hospitable — and who pays out?

4. Confirm plainly: is there any scenario under the Partner Connection where a Vrbo reservation ends up with no working damage deposit and no protection (i.e., a coverage gap versus my current legacy setup)?

5. Your marketing lists "included damage protection" as a benefit of using Hospitable as MoR. The bot says it doesn't cover Vrbo. Please reconcile that contradiction directly.

I'm not looking for reassurance — I'm looking for confirmation of how this functions in practice. If any of it isn't fully built or confirmed yet, state that plainly so I can decide whether to stay on the legacy connection for now.

If you can wait, wait. (You don't actually have to migrate yet)

• It's a brand-new API — a first of its kind for both sides.
• The Partner Connection is meant to be a real upgrade, and I believe that's the intent — but the evidence so far is that it isn't ready for the current onboarding pace.
• The Legacy (Chrome extension) connection is still available and still works — Hospitable's own guidance is to stay on it if you're already connected and not in a rush.

Our experience, as facts:

• We migrated the day it launched. 20 days offline and counting — peak season. Hospitable's side completed cleanly; the block is entirely Vrbo's review queue.
• Vrbo quoted a 15–20 day review window, timed from your project creation date. We're at day 20, still dark, with not one proactive update from Vrbo.
• Five Vrbo reps, four promised 48-hour callbacks, none delivered. We got a case number only after chasing it ourselves.
• Hospitable has been trying to advocate for those of us who are stuck — but the activation itself sits with Vrbo, and there's no fast-tracking it.

So if your listings are working on the Legacy (Chrome extension) connection, I'd let this current rush clear before jumping. No reason to risk weeks offline in summer when the door you're on is still open.

I would personally hold off.  I converted and am still working through a ton of issues and I was told there is no way to convert back.  I find I am more limited under the new integration and when I have reached out for assistance support is super slow on both sides (a week plus).  I would wait and make sure you are super sure before you switch.  I wish I would have waited to see all the issues befire I decided.

I wish I had held off on integrating. I’ve accepted bookings that have no damage protection, even though I’ve chosen that in VRBO. Both Hospitable and VRBO are saying it’s each other’s responsibility - that the answers each platform is giving are inaccurate-if I can even get answers. Very frustrating when you are trying to run your business. I also had several days last week after integrating that properties were unable to be booked, almost causing me to lose clients. If I could go back, I would.  I’m currently spending time I don’t have to find options or I will have to switch to another PMI. I’m sure once these kinks are worked out it will be great but when you’re running the day to day, and trying to expand this is a hassle I didn’t need. 

Hi everyone - I’m really sorry for the confusion here, that was my mistake. To clarify, Hospitable currently supports chargeback protection, not damage protection as of today.

I understand how that would have caused a lot of confusion and was misleading, and I apologize for not making it clearer how we’re able to protect your business.

We’re actively working on security deposits for Vrbo, which should help address these property damage use cases more directly.

Please let us know if you have any questions and, again, very sorry for the confusion.