List support conversations
/v1/support/conversations in the Support Inbox API.
curl "https://api.subscriby.net/v1/support/conversations?status=open" \ -H "Authorization: Bearer $SUBSCRIBY_TOKEN"The queue across every project the token can reach, newest activity first, 25 per page. project_id, status and assigned_to narrow it.
Requires ability
The token must hold this ability, or the call is refused with 403.
MCP tool
Runs the same action from an agent, behind the same ability.
Authorization
bearerToken A personal access token minted on the dashboard under Settings, then Tokens, sent as Authorization: Bearer sbt_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team.
In: header
Query Parameters
Narrow the queue to a single project.
uuidNarrow to one status: open, pending, snoozed or resolved. An unknown value is refused.
Narrow to the conversations assigned to one team member, by user id.
uuidThe page to return, 1-indexed.
1Rows per page, 1 to 100.
25An alias of per_page, kept for older integrations.
Responses
200OKapplication/json
The page.
401UnauthorizedAUTHENTICATION_REQUIREDapplication/json
The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).
403ForbiddenTOKEN_MISSING_ABILITYapplication/json
The token is valid but does not carry the ability this endpoint requires; error.context.required_ability names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers FORBIDDEN, TEAM_TIER_REQUIRED or CONNECTOR_TIER_REQUIRED with the same status, and says so in its own description.
On this endpoint: FORBIDDEN: when the token is confined to other projects.
422Validation failedVALIDATION_FAILEDapplication/json
When status is not one of the four statuses; error.context.allowed lists them.
429Too many requestsRATE_LIMITEDapplication/json
The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.
How is this guide?
Last updated on
Support Inbox API
The support inbox is where a member who writes to your project bot something it does not recognise ends up: one durable support conversation per (project, member, channel), the saved replies your team answers with, and the project's support settings that decide whether the inbox is open, how you hear about a new thread and how replies are signed.
Get a support conversation
/v1/support/conversations/{conversation} in the Support Inbox API.