List Conversations

Retrieve all guest conversations across every connected platform, most recently active first. Each conversation is linked to a reservation and includes the latest message preview.

When to use this endpoint

  • Build a unified inbox that aggregates messages from Airbnb, Booking.com, and direct channels
  • Monitor guest communication volume and response times
  • Feed conversation context into your AI agent for automated responses
  • Display unread message counts in your dashboard

Real-time updates

Combine this endpoint with webhooks subscribing to conversation.updatedevents to get notified instantly when new messages arrive — instead of polling.

List conversations

GET/v1/conversations
curl "https://api.repull.dev/v1/conversations?limit=20" \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

Query parameters

limitintegerDefault: 20

Maximum number of conversations per page. 1-100.

cursorstring

The previous response's pagination.nextCursor. Omit on the first call.

orderstringDefault: recent

recent (default): most recent activity first. created: newest conversation first, stable for the whole walk. Use created to sync every conversation exactly once. Keep the same value on every page.

updated_sincestring

ISO 8601 instant. Only conversations whose record changed at or after it, oldest change first (order does not apply). Use the last row's updatedAt as your next value.

platformstring

Only conversations on one channel: airbnb, booking, vrbo, plumguide, website or email.

statusstring

open or archived. archived currently always returns an empty page.

Order

By default the list is ordered by lastMessageAt, newest first: the conversations with the latest activity come back on the first page. That is the right order for an inbox or for "what changed lately".

Syncing every conversation? Use order=created

The default order is live. A conversation that gets a new message while you page moves to the front, behind your position, so that walk will not return it (your next walk, or an updated_since poll, will). To walk every conversation exactly once, pass order=created: newest conversation first, by when it started, and stable for the whole walk. A cursor always continues in the order its walk started in.

To stay up to date after a full sync, poll with updated_since: it returns only conversations whose record changed since your last poll, oldest change first.

Response format

Returns a paginated array of conversation objects with message previews.

{
  "data": [
    {
      "id": "100",
      "reservationId": "456",
      "propertyId": "123",
      "guestName": "Sarah Mitchell",
      "lastMessage": "Hi! What are the check-in instructions?",
      "lastMessageAt": "2026-05-28T14:30:00Z",
      "unreadCount": 1,
      "type": "reservation",
      "createdAt": "2026-05-15T09:00:00Z"
    },
    {
      "id": "101",
      "reservationId": "789",
      "propertyId": "124",
      "guestName": "Marco Rossi",
      "lastMessage": "Thank you for the early check-in!",
      "lastMessageAt": "2026-05-27T10:15:00Z",
      "unreadCount": 0,
      "type": "reservation",
      "createdAt": "2026-05-20T11:00:00Z"
    }
  ],
  "pagination": {
    "total": 42,
    "limit": 50,
    "offset": 0,
    "hasMore": false
  }
}

Response fields

idstring

Unique conversation identifier.

reservationIdstring

ID of the linked reservation.

propertyIdstring

ID of the property this conversation belongs to.

guestNamestring

Full name of the guest.

lastMessagestring

Preview of the most recent message in the thread.

lastMessageAtstring

ISO 8601 time of the conversation's newest activity: its newest message, or a later change to the conversation. For imported conversations it is the newest imported message's own time, not when you connected. The default order sorts on it.

unreadCountinteger

Number of unread messages from the guest.

typestring

Conversation type: reservation, inquiry, or general.

createdAtstring

ISO 8601 timestamp when the conversation was created.

updatedAtstring

ISO 8601 time the conversation record last changed. Use it as the updated_since watermark.

Pagination

Results are cursor-paginated. Pass the previous response's pagination.nextCursor back as cursor, and stop when pagination.hasMore is false. For a walk over every conversation, add order=created (see Order).

# Full sync: every conversation exactly once, stable while paging
curl "https://api.repull.dev/v1/conversations?order=created&limit=100" \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# Then keep up to date: only what changed since your last poll
curl "https://api.repull.dev/v1/conversations?updated_since=2026-11-12T16:00:00Z&limit=100" \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

Collecting conversations that need a reply, across every page:

// Fetch conversations with unread messages
import type { Conversation } from '@repull/sdk';

const unread: Conversation[] = [];
let cursor: string | undefined

do {
  const { data, pagination } = await repull.conversations.list({ limit: 50, cursor });

  for (const conv of data) {
    if ((conv.unreadCount ?? 0) > 0) unread.push(conv);
  }

  cursor = pagination.hasMore ? pagination.nextCursor ?? undefined : undefined;
} while (cursor);

console.log(`${unread.length} conversations need a reply`);

API Reference

See the complete Conversations API Reference for all endpoints including reading messages and sending replies.

AI