Connect Vrbo
The host signs in with their own Vrbo account on a hosted page. Choose the access first: messaging when the host keeps their PMS, full access when Repull is the channel manager. (On Airbnb the host approves your app instead: Connect Airbnb.)
Choose the access
accessType | Use it when | What Repull does on Vrbo |
|---|---|---|
messaging | The host keeps their PMS or channel manager | Reads bookings, inquiries, messages and reviews; sends messages, pre-approvals, quotes and review replies. Never pushes the calendar. |
full_access (default) | Repull is the channel manager | Everything above, plus availability, prices, minimum stay and closed to arrival / departure pushed to Vrbo for each linked listing, listings taken off sale and back, new listings created on Vrbo, and the content of existing listings edited section by section. |
Set accessType when you create the session to decide it for the host. Leave it out and the host chooses on the hosted page.
Connect an account
- Your server creates a Connect session for
vrbo-loginand sends the host to its URL. - The host signs in with their Vrbo email and password. If Vrbo sends them a verification code, they enter it on the same page. If Vrbo asks for a contact phone to complete their profile, they enter it there too, from any country.
- The host picks which Vrbo units belong to which of your listings. On a workspace with no listings yet there is nothing to pick: every unit becomes a listing on its own (past a plan limit, created inactive) and the import starts at sign-in.
- Once they confirm, the import starts: upcoming bookings and the last 30 days of messages first, then the rest of the account's history in the background.
curl -X POST https://api.repull.dev/v1/connect \
-H 'Authorization: Bearer sk_live_...' \
-H 'Content-Type: application/json' \
-d '{
"redirectUrl": "https://yourapp.com/connected",
"allowedProviders": ["vrbo-login"],
"accessType": "messaging"
}'Check the connection and the import with GET /v1/connect/vrbo-login. Each signed-in account comes back with its access and where its import stands (importing → importing_history → imported).
curl https://api.repull.dev/v1/connect/vrbo-login \ -H 'Authorization: Bearer sk_live_...'
To map units in your own UI instead of the hosted page, create the session with "mapping": "api". Connect then finishes right after sign-in and skips its mapping step. Use the connection handle vrbo:{externalAccountId}, where externalAccountId is Vrbo's own account id (accounts[].externalAccountId on GET /v1/connect/vrbo-login, e.g. vrbo:7001234): GET /v1/connections/{id}/unitslists the account's units with a suggested listing for each. The unit_id is the Vrbo listing number, which doesn't change, and meta.address is the address as Vrbo has it. POST /v1/connections/{id}/mappings maps them. Mapping the first unit starts the import. On a workspace with no listings yet the units are already mapped to new listings when sign-in finishes, and the import is running.
A host who leaves the hosted mapping before every unit is mapped can come back to it without signing in to Vrbo again. While units are left, the Vrbo connection on GET /v1/connect carries action.reason: "needs_mapping" (required is true when none are mapped yet) and a fixUrl. Send the host to the fixUrl: it opens Connect straight on that account's unit mapping. The Connections page in the dashboard shows the same link as Map units.
Ask every host for one more step: adding the account's notification address on Vrbo as a secondary email, with message and reservation notifications on. Vrbo's notification emails are how new bookings, inquiries and guest messages reach Repull within a minute; the scheduled check every few minutes is the backup. Hosted Connect asks for it on its mapping screen. With "mapping": "api" that screen is skipped, so ask in your own flow: the address comes back as notification_email on GET /v1/connections/vrbo:{externalAccountId}/units and as notifications.address on GET /v1/connect/vrbo-login, next to notifications.state, which says whether the emails are arriving. See Vrbo notification address.