---
title: "List inboxes"
method: GET
path: "/v1/{account_id}/inboxes"
tags: ["Messaging"]
---

# List inboxes

`GET /v1/{account_id}/inboxes`

## Request

- Base URL: `https://api.curviate.com`
- URL: `https://api.curviate.com/v1/{account_id}/inboxes`
- Auth: HTTP bearer

Lists the account's personal inbox plus, when the company product is attached, one entry per company page and folder. Company inboxes are reply-only. company_id is null when the page can't be correlated to a managed page.

## Path parameters

- `account_id` string, required

## Query parameters

- `kind` 'personal' | 'company'
- `company_id` string

## Response `200`

The account's inboxes: its own personal inbox, plus, when the company product is attached, one entry per company page (e.g. id='COMPANY_83734124_PRIMARY'). When no company inbox exists, hint names the Company Pages reconnect requirement instead of returning silently empty. This is the discovery step of the reply-as-a-page flow: find a company inbox here, read its conversations with GET /v1/{account_id}/inboxes/{inbox_id}/chats, then reply with the existing POST /v1/{account_id}/chats/{chat_id}/messages using one of its chat ids.

- object
  - `object` 'inbox_list': Response type discriminator.
  - `items` object[]
    - `object` 'inbox': Response type discriminator.
    - `id` string: Inbox identifier. Pass it to the inbox-chats endpoint below to read its conversations.
    - `kind` 'personal' | 'company': Whether this is the account's own inbox or a company page's.
    - `folder` string: Folder within the inbox, e.g. 'primary', 'archived', 'spam'.
    - `name` string, nullable: Personal: the folder's display name. Company: the page's display name.
    - `company_id` string, nullable: Company inboxes only. The managed-company id this mailbox was correlated to, or null when it could not be correlated (never a fabricated id).
    - `mailbox_id` string, nullable: Company inboxes only. The substrate's internal mailbox id (distinct from company_id).
    - `reply_only` boolean: True for company inboxes: a company page can only reply to an existing conversation, it can never start one.
  - `hint` string: Present only when no company inbox exists. Names the reconnect requirement.
  - `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`: Invalid kind or company_id filter value.
- `401`: Missing or invalid API key.
- `404`: No such account for this tenant. 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.
- `429`: Rate limited.
- `500`: Internal error.
- `502`: A temporary error occurred. Please try again.
- `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)