GET
List my conversations (inbox)

Overview

Returns every conversation the caller is a participant of, sorted by lastMessageAt descending (newest activity first), with _id descending as the tie-breaker so the order is stable across pages. This is the inbox feed. A conversation with lastMessage: null (handshake created but no message yet) sorts at the bottom — the secondary _id sort keeps it at a deterministic position. The mobile client typically renders these as “Say hi — you matched with X” placeholders. Conversations are returned as full documents (same shape as Get conversation) so the inbox can render last-message previews, unread badges, and timestamps without a follow-up call per row.

Authentication

Bearer <accessToken> required. requireOnboarded middleware applied — half-onboarded users hit 403 ONBOARDING_INCOMPLETE.

Path parameters

None.

Query parameters

The Phase 4 implementation does not yet accept a cursor — the entire inbox is returned in one page up to limit rows. Adding ?cursor= will be additive in Phase 5 and will not break callers that ignore it.

Request body

None.

Response — 200 OK

Each element matches the Conversation object shape.

Example response

Each conversation embeds an enriched peer (firstName + avatar) and property (the peer’s listing — cover photo + address) so the inbox renders a name, avatar, and property thumbnail per row without a follow-up call. See the Conversation object for the full field reference. peer / property may be null if the underlying user / listing has been deleted.

Error responses

Side effects

None — pure read.

See also

curl