Get Reservations
Pull reservations from Airbnb, Booking.com, and every other connected platform in a single API call.
When to use this endpoint
- Sync reservations from all platforms into your own database
- Build a unified calendar or inbox across Airbnb, Booking.com, and direct bookings
- Power a revenue dashboard with real-time booking data
- Feed reservation data into your AI agent for guest communication
Need real-time updates?
List reservations
/v1/reservationscurl "https://api.repull.dev/v1/reservations?status=CONFIRMED&limit=10" \ -H "Authorization: Bearer sk_live_YOUR_KEY"
Query parameters
limitintegerDefault: 50Maximum number of results to return.
offsetintegerDefault: 0Number of results to skip for pagination.
statusstringFilter by reservation status.
PENDING CONFIRMED CANCELLED POST_STAYproperty_idstringFilter reservations for a specific property.
sourcestringFilter by booking platform.
AIRBNB BOOKING_COM DIRECTcheck_in_afterdateOnly reservations with check-in after this date. Format: YYYY-MM-DD.
check_in_beforedateOnly reservations with check-in before this date. Format: YYYY-MM-DD.
check_out_afterdateOnly reservations with check-out after this date. Format: YYYY-MM-DD.
check_out_beforedateOnly reservations with check-out before this date. Format: YYYY-MM-DD.
updated_sincedatetimeOnly reservations modified after this ISO 8601 timestamp. Useful for incremental sync.
camelCase aliases (checkInAfter, checkInBefore, checkOutAfter, checkOutBefore) are accepted but deprecated — prefer the snake_case names above.
Response format
Returns a paginated array of reservation objects.
{
"data": [
{
"id": "456",
"propertyId": "123",
"roomTypeId": "RT-001",
"status": "CONFIRMED",
"source": "AIRBNB",
"confirmationCode": "HM12345",
"checkIn": "2026-06-01",
"checkOut": "2026-06-05",
"checkInTime": "16:00",
"checkOutTime": "10:00",
"guestNotes": "Approximate time of arrival: between 15:00 and 16:00",
"conversationId": "164743",
"externalThreadId": "2680544213",
"inquiryId": "25173",
"primaryGuest": {
"firstName": "Sarah",
"lastName": "Mitchell",
"email": "sarah@example.com",
"phone": "+1-555-0123",
"language": "en"
},
"occupancy": {
"adults": 2,
"children": 1,
"infants": 0,
"pets": 0
},
"financials": {
"totalPrice": 1800,
"currency": "USD",
"paymentStatus": "paid",
"cancellationPolicy": "firm_14",
"breakdown": {
"basePrice": 1500,
"cleaningFee": 150,
"fees": [{ "type": "SERVICE_FEE", "amount": 100 }],
"taxes": [{ "type": "LODGING_TAX", "amount": 50, "rate": 0.09 }],
"discounts": []
}
},
"bookedAt": "2026-05-15T09:00:00Z"
}
],
"pagination": {
"total": 28,
"limit": 50,
"offset": 0,
"hasMore": false
}
}Response fields
Airbnb guest phones
phoneType: "airbnb_relay") or missing. See Airbnb guest phone numbers.idstringUnique reservation identifier.
propertyIdstringID of the property this reservation belongs to.
statusstringCurrent status: PENDING, CONFIRMED, CANCELLED, or POST_STAY.
sourcestringPlatform where the booking originated: AIRBNB, BOOKING_COM, DIRECT.
confirmationCodestringPlatform-specific confirmation code (e.g. HM12345 for Hostaway).
checkInstringCheck-in date (YYYY-MM-DD).
checkOutstringCheck-out date (YYYY-MM-DD).
checkInTimestringnullableLocal check-in time for this stay, HH:MM on a 24-hour clock in the property's own timezone — not UTC. The same field PATCH /v1/reservations/{id} writes, so you can confirm a change took. Where it comes from: the time the channel states for the property (Booking.com and Airbnb state their own); when the channel states none, the listing's own check-in time (set it with PUT /v1/listings/{id}/content, policies.checkInTimeStart); when the listing has none either, 15:00.
checkOutTimestringnullableLocal check-out time, same format. Pair with checkOut to schedule the turnover clean. Same order as checkInTime: the channel's time, then the listing's policies.checkOutTime, then 10:00.
guestNotesstringnullableWhat the guest wrote with the booking, as the channel sent it. Booking.com puts the estimated arrival time and special requests here. Free text, never parsed.
conversationIdstringnullableThe conversation with this guest — use it with GET /v1/conversations/{id} and /v1/conversations/{id}/messages. It is the same conversation from inquiry through pre-approval to the confirmed booking, and the same id the message webhooks carry.
externalThreadIdstringnullableThe channel's own id for that conversation (Airbnb thread id, Booking.com conversation id).
inquiryIdstringnullableThe inquiry this booking came from (GET /v1/inquiries), when the guest asked before booking.
primaryGuestobjectGuest who made the booking.
suggestedDoorCodestringAirbnb reservations only, when Airbnb sends it: the last 4 digits of the booker's verified phone (random when none). Use it for door codes instead of the guest's phone. See Airbnb guest phone numbers.
occupancyobjectNumber of guests by category.
financialsobjectComplete pricing breakdown.
bookedAtstringISO 8601 timestamp when the reservation was created.
pmsReservationIdstringnullableThe PMS's own id for this reservation (for example Guesty's reservation _id), so you can look it up in the PMS. null when the reservation did not come from a PMS.
accessCodesarraynullableDoor codes for the stay from the PMS's lock manager (today: Guesty Locks Manager). null when the reservation's codes are not read from a PMS; [] when they are and there is none yet, and for a cancelled stay. See Door codes below.
What Airbnb reservations do not carry
Door codes
When the host's PMS issues door codes, each reservation carries them in accessCodes, so your guest messaging or AI agent can hand every guest their code without a separate PMS key. Today that is Guesty Locks Manager. The same field is on GET /v1/reservations, GET /v1/reservations/{id} and the reservation webhooks.
"accessCodes": [
{
"code": "482913",
"type": "guest",
"status": "active",
"validFrom": "2026-11-01T20:00:00.000Z",
"validUntil": "2026-11-05T15:00:00.000Z",
"locks": [{ "id": "64f0c1aa2b3c4d5e6f708192", "name": "Front door", "provider": "schlage" }],
"source": "guesty",
"updatedAt": "2026-10-31T14:30:00.000Z"
},
{
"code": "730155",
"type": "backup",
"status": "active",
"validFrom": null,
"validUntil": null,
"locks": [{ "id": "64f0c1aa2b3c4d5e6f708192", "name": "Front door", "provider": "schlage" }],
"source": "guesty",
"updatedAt": "2026-10-31T14:30:00.000Z"
}
]- Codes are read for confirmed stays that check in within the next 14 days and have not checked out, and refreshed about every 30 minutes. Earlier and past stays keep the last codes read.
- Give the guest the
guestcode. Share abackupcode only if the guest code fails; Guesty may change a backup code read before check-in day. nullmeans codes are not read for this reservation (its PMS has no lock manager we read).[]means they are read and the PMS has none for this stay yet, which is also what an account without Locks Manager returns. A cancelled stay always returns[].- Codes are read-only: create or change them in the PMS.
Treat codes like passwords
Filtering examples
By platform
curl "https://api.repull.dev/v1/reservations?source=AIRBNB" \ -H "Authorization: Bearer sk_live_YOUR_KEY"
Upcoming check-ins
curl "https://api.repull.dev/v1/reservations?check_in_after=2026-06-01&check_in_before=2026-06-30&status=CONFIRMED" \ -H "Authorization: Bearer sk_live_YOUR_KEY"
Incremental sync (only changes since last poll)
curl "https://api.repull.dev/v1/reservations?updated_since=2026-06-01T00:00:00Z" \ -H "Authorization: Bearer sk_live_YOUR_KEY"
Pagination
Results are cursor-paginated. Pass the previous response's pagination.nextCursor back as cursor, and stop when pagination.hasMore is false.
// Page through all reservations
let cursor: string | undefined
do {
const { data, pagination } = await repull.reservations.list({ limit: 50, cursor });
for (const reservation of data) {
await processReservation(reservation);
}
cursor = pagination.hasMore ? pagination.nextCursor ?? undefined : undefined;
} while (cursor);API Reference
See the complete Reservations API Reference for all endpoints including create, update, and cancel.