--- title: "List a conversation's messages" method: GET path: "/v1/{account_id}/companies/{identifier}/chats/{chat_id}/messages" tags: ["Companies: Inbox"] --- # List a conversation's messages `GET /v1/{account_id}/companies/{identifier}/chats/{chat_id}/messages` ## Request - Base URL: `https://api.curviate.com` - URL: `https://api.curviate.com/v1/{account_id}/companies/{identifier}/chats/{chat_id}/messages` - Auth: HTTP bearer Returns a page of one conversation's messages, newest-first. Message text passes through and is never stored. An unknown conversation returns 404 (the empty page is not trusted at face value); a genuinely empty existing thread returns an empty list. The connected account must administer the page. ## Path parameters - `account_id` string, required - `identifier` string, required - `chat_id` string, required ## Query parameters - `limit` integer - `cursor` string - `expand` string ## Response `200` A page of a conversation's messages, newest-first. Message text is returned verbatim and is never stored. A genuinely empty (but existing) thread returns an empty list; an unknown conversation returns 404. Page until cursor is null. - object - `object` 'company_chat_message_list', required: Response type discriminator. - `items` object[], required: The thread's messages, newest-first. - `object` 'company_chat_message', required: Response type discriminator. - `id` string, required: The message id (2-... form). - `conversation_id` string, required: The parent conversation id (2-... form). - `sender` object, required - `id` string, required: Sender's member id. - `name` string, nullable, required: Sender display name (content pass-through, never stored). - `public_identifier` string, nullable: The vanity slug from the profile URL, for example jane-smith. Present only when the request asks for it with expand=public_identifier, and then always present, carrying the slug or null when the platform surfaces none for this person. - `sent_at` number, required: Epoch-ms delivery time; also the newest-first pagination anchor. - `text` string, nullable: Message body (content pass-through, never stored). - `cursor` string, nullable, required: Opaque cursor for the next page, or null at end-of-list. - `notices` object[]: Present only when expand=public_identifier was asked for and some people on this page went unresolved for a reason the payload cannot show: more of them needed a profile lookup than one request performs, the account is outside its activity window at this hour and enforces it, or the account's profile_views budget is at its configured ceiling and enforces that. Absent whenever there is nothing to report, so a response that resolved everyone carries no such key. Branch on each entry's code, never on its message. - `code` 'EXPANSION_LIMIT_REACHED' | 'EXPANSION_WITHHELD_ACTIVITY_WINDOW' | 'EXPANSION_WITHHELD_CEILING', required: EXPANSION_LIMIT_REACHED: more people on this page needed a profile lookup than one request performs, so the ones past the budget carry public_identifier null without ever having been looked up. Their null therefore does not mean the person has no public profile. Ask for a smaller page to resolve everyone. EXPANSION_WITHHELD_ACTIVITY_WINDOW: the profile lookups this page needed were refused because the account is outside its activity window at this hour and enforces it, so those people carry public_identifier null and their null does not mean they have no public profile either. Ask again inside the window, or widen the window on this account's safety policy. EXPANSION_WITHHELD_CEILING: the profile lookups this page needed were refused because the account's profile_views budget is at its configured ceiling and it enforces that, so those people carry public_identifier null and their null does not mean they have no public profile either. Raise the profile_views ceiling on this account's safety policy, or ask for a smaller page. - `message` string, required: One sentence explaining the condition and how to resolve it. - `field` string: The request field the notice is about, here expand. - `value` string: The expansion the notice is about, here public_identifier. - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite. - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture. - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail). - `hint` object, required - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy. - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text. - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each. - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload. ## Other responses - `400`: A non-numeric identifier, a malformed/empty chat_id, or a malformed cursor. - `401`: Missing or invalid API key. - `403`: The account does not administer this page (the admin gate), or lacks an active seat. - `404`: The account_id does not belong to this tenant, or the conversation does not exist. An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id. - `422`: The account is restricted and cannot be queried. - `429`: Rate limited: slow down and retry after the hinted delay. - `500`: Internal error. - `502`: A temporary upstream error occurred, or the upstream response could not be interpreted. Check `retry_likely_to_succeed`: a temporary error is worth retrying, a response that could not be interpreted is not, and carries `retry_hint: {"kind": "never"}`. - `503`: Service unavailable. - `504`: Gateway timeout. --- [API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)