Vrbo Transactions
Every bank deposit Vrbo made to the host, with the bookings it paid, and the payouts Vrbo has scheduled — on the same path and in the same shape as the Airbnb transactions ledger. Each line has a stable id and a signed amount, and a deposit's lines add up to what reached the bank, so you can reconcile Vrbo payouts automatically. POST on the same path refreshes it from Vrbo.
/v1/channels/vrbo/transactionsParameters
account_idstringOnly this Vrbo account (accountId from GET /v1/channels/vrbo/connection).
start_datestringFrom this deposit date (YYYY-MM-DD).
end_datestringUp to this deposit date (YYYY-MM-DD).
statusstringCOMPLETED (deposited) or UPCOMING (scheduled, not paid yet).
payout_idstringOne deposit (its reference number) and every line in it.
confirmation_codestringEvery line for one booking.
typestringPayout, Reservation or Adjustment.
limitintegerLines per page, up to 500 (default 100).
cursorstringThe pagination.nextCursor of the previous page.
Reconciling deposits
The response reads like Vrbo's financial report: newest deposit first, each Payout row followed by the bookings it paid.
- A deposit's lines add up to its
payout.paidOutAmountexactly. A negative line (type: Adjustment) is money Vrbo took back from that deposit, for example after a refund. - Ids are stable: a Payout row's
transactionIdis Vrbo's deposit reference number; a line's is<reference>:<confirmationCode>:<n>. Upsert ontransactionId. status: UPCOMINGlines are payouts Vrbo has scheduled, with Vrbo'supcomingStatus(Scheduled, orBlockedwhile Vrbo holds it) and the estimated payoutdate. Once paid, the line appears under its deposit.- Lines on listings that are inactive in Repull are included and flagged
onInactiveListing, so every deposit reconciles.reservationIdlinks a line to the booking in Repull when it is in the workspace. - Vrbo's report has no fee split per booking, no taxes and no stay dates (
unavailableFields); the reservation has those.
Freshness and refresh
The ledger is read from the Vrbo account — the last 12 months of deposits and the payouts scheduled for the next 6 — and kept, so a read answers at once.
- A ledger more than a day old, or never read, answers from Repull's copy and is refreshed in the background:
dataFreshness.reasonisrefreshingornever_synced. POST /v1/channels/vrbo/transactionsrefreshes it now — every connected account, or one with?account_id=. Optional body:start_date/end_datefor the deposits to read. About 15 seconds per account; an account that fails carrieserrorand the others still refresh.
Example
# Refresh from Vrbo, then read one deposit with its bookings curl -X POST https://api.repull.dev/v1/channels/vrbo/transactions \ -H "Authorization: Bearer sk_live_YOUR_KEY" curl "https://api.repull.dev/v1/channels/vrbo/transactions?payout_id=7f3c2a10-5b4e-4d8a-9c21-0e6f8a1b2c3d" \ -H "Authorization: Bearer sk_live_YOUR_KEY"
Response
{
"data": [
{
"transactionId": "7f3c2a10-5b4e-4d8a-9c21-0e6f8a1b2c3d",
"accountId": "vrbo:7001234",
"type": "Payout",
"isPayout": true,
"status": "COMPLETED",
"date": "2026-11-16",
"currency": "CAD",
"amount": 434.88,
"payout": { "payoutId": "7f3c2a10-5b4e-4d8a-9c21-0e6f8a1b2c3d", "payoutDate": "2026-11-16", "lineIndex": null, "paidOutAmount": 434.88, "bankDestination": "EXAMPLE BANK 1234" }
},
{
"transactionId": "7f3c2a10-5b4e-4d8a-9c21-0e6f8a1b2c3d:HA-4TQ7WM:1",
"type": "Reservation",
"isPayout": false,
"status": "COMPLETED",
"date": "2026-11-16",
"currency": "CAD",
"amount": 249.81,
"payout": { "payoutId": "7f3c2a10-5b4e-4d8a-9c21-0e6f8a1b2c3d", "payoutDate": "2026-11-16", "lineIndex": 1, "paidOutAmount": null, "bankDestination": "EXAMPLE BANK 1234" },
"confirmationCode": "HA-4TQ7WM",
"reservationId": 235939,
"listingId": 6199,
"vrboListingNumber": "1234567",
"onInactiveListing": false,
"unavailableFields": ["gross_amount", "fees", "taxes", "nights", "reservation_start_date", "description"]
}
],
"pagination": { "nextCursor": "eyJvIjoxMDB9", "hasMore": true, "total": 986 },
"dataFreshness": { "lastSyncedAt": "2026-11-21T22:04:50.662Z", "stale": false, "reason": "ok" }
}