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?

Use webhooks to get notified instantly when reservations are created, updated, or cancelled — instead of polling this endpoint.

List reservations

GET/v1/reservations
curl "https://api.repull.dev/v1/reservations?status=CONFIRMED&limit=10" \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

Query parameters

limitintegerDefault: 50

Maximum number of results to return.

offsetintegerDefault: 0

Number of results to skip for pagination.

statusstring

Filter by reservation status.

PENDING CONFIRMED CANCELLED POST_STAY
property_idstring

Filter reservations for a specific property.

sourcestring

Filter by booking platform.

AIRBNB BOOKING_COM DIRECT
check_in_afterdate

Only reservations with check-in after this date. Format: YYYY-MM-DD.

check_in_beforedate

Only reservations with check-in before this date. Format: YYYY-MM-DD.

check_out_afterdate

Only reservations with check-out after this date. Format: YYYY-MM-DD.

check_out_beforedate

Only reservations with check-out before this date. Format: YYYY-MM-DD.

updated_sincedatetime

Only 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

Airbnb no longer shares guests' real phone numbers. A phone on an Airbnb stay may be a temporary relay number (phoneType: "airbnb_relay") or missing. See Airbnb guest phone numbers.
idstring

Unique reservation identifier.

propertyIdstring

ID of the property this reservation belongs to.

statusstring

Current status: PENDING, CONFIRMED, CANCELLED, or POST_STAY.

sourcestring

Platform where the booking originated: AIRBNB, BOOKING_COM, DIRECT.

confirmationCodestring

Platform-specific confirmation code (e.g. HM12345 for Hostaway).

checkInstring

Check-in date (YYYY-MM-DD).

checkOutstring

Check-out date (YYYY-MM-DD).

checkInTimestringnullable

Local 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.

checkOutTimestringnullable

Local 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.

guestNotesstringnullable

What 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.

conversationIdstringnullable

The 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.

externalThreadIdstringnullable

The channel's own id for that conversation (Airbnb thread id, Booking.com conversation id).

inquiryIdstringnullable

The inquiry this booking came from (GET /v1/inquiries), when the guest asked before booking.

primaryGuestobject

Guest who made the booking.

suggestedDoorCodestring

Airbnb 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.

occupancyobject

Number of guests by category.

financialsobject

Complete pricing breakdown.

bookedAtstring

ISO 8601 timestamp when the reservation was created.

pmsReservationIdstringnullable

The 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.

accessCodesarraynullable

Door 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

Airbnb does not release a guest's real email address, a payment method, a per-reservation payment reference, or free-text notes to any partner — so those are absent here and on webhooks, not withheld. Booking.com and direct bookings do carry a guest email. See what reservation events do not carry for the full table and where to look instead.

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 guest code. Share a backup code only if the guest code fails; Guesty may change a backup code read before check-in day.
  • null means 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

A door code opens a real home. Send it only to the guest of that stay, close to check-in, and don't log it.

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.

AI