List the merged conversation inbox
The tenant’s merged conversation inbox — support channels (the primary employer↔creator conversation type) and DM conversations, merged by last-message recency. The agent-facing equivalent of the web’s merged “Home” inbox. Each item’s type dictates the follow-up messages read: support_channel → GET /support-channels/{id}/messages, dm → GET /conversations/{id}/messages. Snapshot of the most recent items (limit ≤ 50, no cursor; hasMore is always false) — paginate deeper via /support-channels and /conversations. One-way system broadcasts the tenant itself sent (e.g. brand-verification congrats DMs) are hidden while unanswered — they reappear if the counterparty replies, and stay visible via /conversations. A tenant with no connected messaging account degrades to a DM-only inbox; an upstream support-channel FAILURE also degrades to DM-only but is flagged via warnings: ["support_channels_unavailable"].
Authorizations
OAuth 2.1 authorization code + PKCE (S256). Tokens are tenant-bound (company_id) and scoped. Discover endpoints via /.well-known/oauth-authorization-server.
Query Parameters
Max items to return.
1 <= x <= 50Response
The merged inbox (most recent first).
Soft-degradation signals. 'support_channels_unavailable': the live support-channel fetch failed upstream and the list is DM-only/incomplete (distinct from a tenant with no connected messaging account, which is not a failure and carries no warning).