Get a single message
Hydrates one message for a caller holding only its id — the same row the thread page returns, including the resolved email HTML body. The conversation is part of the lookup, not a check after it: a message id from another thread is indistinguishable from one that does not exist.
Loading the API reference…
Send a message (or add an internal note) POST
Sends through the endpoint named by endpointId (required unless type=note). subjectPatientId identifies which represented patient a message concerns, must belong to that contact, and is required when the contact represents more than one patient (409 CONTACT_PARTY_SUBJECT_REQUIRED). Returns the queued row synchronously for optimistic UI; delivery progresses via WebSocket message.updated events. Notes are never sent to the patient. Sends respect per-channel opt-outs (403 OPTED_OUT), the WhatsApp 24h window (400 WHATSAPP_WINDOW_CLOSED — retry with a template), the Messenger/Instagram 24h and TikTok 48h reply windows (400 REPLY_WINDOW_CLOSED; a person replying from the Smileline app or mobile app may answer on Messenger/Instagram up to 7 days after the last inbound once Meta approved the Human Agent feature — API-key and OAuth sends never get that extension), and the 1 MiB patient-bearing metadata ceiling (413 MESSAGE_CONTENT_METADATA_TOO_LARGE).
Download an attachment GET
Streams the server-owned object privately (no-store) after the org check. Active and unknown formats are forced to a safe download. A single `Range: bytes=` request answers 206 with Content-Range (416 past the end), so audio and video can seek.