GET
Get conversation by id

Overview

Returns a single conversation document. The caller is authorised iff their userId appears in participantIds; otherwise the endpoint returns 403 FORBIDDEN rather than 404 NOT_FOUND, so an attacker cannot probe for valid conversation ids by status code. Used by:
  • The conversation screen when opening from a deep link.
  • After a chat:open socket event, to fetch the latest lastMessage / unreadCount snapshot.
  • Re-fetching the conversation when reconciling stale local state.

Authentication

Bearer <accessToken> required. requireOnboarded middleware applied.

Path parameters

Query parameters

None.

Request body

None.

Response — 200 OK

Example response

The peer (firstName + avatar) and property (the peer’s listing) fields are enriched server-side — the conversation screen’s header renders the peer’s name, avatar, and the matched property without a follow-up call. See the Conversation object for the full reference.

Error responses

Example error — 403

Side effects

None — pure read.

See also

curl