Vrbo notification address

Every connected Vrbo account has its own notification address. When the host adds it on Vrbo, each Vrbo notification email tells Repull that something changed, and the new guest message, inquiry or booking is in your app within about a minute. Without it, Repull still finds them, but on a scheduled check that is slower.

Why it matters

  • Faster replies. A guest who writes on Vrbo is in your inbox within about a minute, so your team or your automation can answer while the guest is still there.
  • Fewer delays. The scheduled check is the backup, and Vrbo limits how often an account can be read, so the notification is the dependable path.

Add it on Vrbo

The address looks like in+vrbo-1474-33@repull.dev and belongs to one Vrbo account. Ask the host to:

  1. Copy the address.
  2. In Vrbo, open the account settings and add it as a secondary email. The main email stays as it is.
  3. Turn on email notifications for messages and reservations.

Hosted Connect asks for this on its mapping screen and confirms when Vrbo's first email arrives. If you create sessions with "mapping": "api", that screen is skipped: show the address in your own app. Only Vrbo's notification emails go to it.

Check that it works

Each Vrbo account on GET /v1/connect/vrbo-login (and on GET /v1/connect/vrbo) carries a notifications object:

{
  "externalAccountId": "1295468",
  "name": "Lakeside Cabins",
  "connected": true,
  "notifications": {
    "state": "missing",
    "lastReceivedAt": "2026-11-02T14:10:05.000Z",
    "address": "in+vrbo-1474-33@repull.dev"
  }
}
stateMeaning
activeVrbo's notifications arrive for this account's guest messages. Nothing to do.
missingThe account had new guest messages and no notification came for them. The host has not added the address, or turned its notifications off. Ask them to add address again.
unknownNo guest messages yet to judge by, for example right after connecting.

lastReceivedAt is when the last Vrbo notification reached the address (null if none ever has). The older notificationReceivedAt field is the time of the first notification and stays set even if notifications stop later. It is kept for existing integrations; use notifications instead.

Get told when it stops

Subscribe to account.notifications_missing. It is sent once when an account's notifications.state becomes missing, with the account and its notifications object, so you can show the host a banner with the address:

{
  "event": "account.notifications_missing",
  "data": {
    "provider": "vrbo",
    "accountId": "1295468",
    "notifications": {
      "state": "missing",
      "lastReceivedAt": "2026-11-02T14:10:05.000Z",
      "address": "in+vrbo-1474-33@repull.dev"
    },
    "detectedAt": "2026-11-17T16:40:00.000Z",
    "docsUrl": "https://repull.dev/docs/channels/vrbo/notifications"
  }
}

Messages still arrive without it

A missing notification address never loses a message: the scheduled check still imports it. It only arrives later. See Guest messages on the Vrbo page.
AI