Support Inbox API

The page.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

When status is not one of the four statuses; error.context.allowed lists them.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The thread.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The page.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The recorded message.

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The key was already used in the last 24 hours with a different request body.

The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields. On this endpoint: VALIDATION_FAILED: when body is missing or over 4,000 characters, or reply_to_message_id is not a message of this conversation.

The first request with this key is still running; retry in a few seconds and the original response is replayed.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

Array of SupportCannedReplyResource

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The snippet.

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The key was already used in the last 24 hours with a different request body.

The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields. On this endpoint: VALIDATION_FAILED: when title or body is missing or out of range, shortcut is malformed or already used on the project, or sort_order is outside 0 to 999.

The first request with this key is still running; retry in a few seconds and the original response is replayed.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The snippet.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The snippet, updated.

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The key was already used in the last 24 hours with a different request body.

The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields. On this endpoint: VALIDATION_FAILED: when a field is out of range or the shortcut is already used on the project.

The first request with this key is still running; retry in a few seconds and the original response is replayed.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

No content

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The key was already used in the last 24 hours with a different request body.

The first request with this key is still running; retry in a few seconds and the original response is replayed.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The settings.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The settings, updated.

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The key was already used in the last 24 hours with a different request body.

The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields. On this endpoint: VALIDATION_FAILED: when relay_mode is not owner_dm, forum_group or none, agent_name exceeds 60 characters, or auto_reply exceeds 1,000 characters.

The first request with this key is still running; retry in a few seconds and the original response is replayed.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The thread, resolved.

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The key was already used in the last 24 hours with a different request body.

The first request with this key is still running; retry in a few seconds and the original response is replayed.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The thread, reassigned.

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The key was already used in the last 24 hours with a different request body.

The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields. On this endpoint: VALIDATION_FAILED: when the key is omitted, is not a UUID, or names no user.

The first request with this key is still running; retry in a few seconds and the original response is replayed.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The thread, open again.

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The key was already used in the last 24 hours with a different request body.

The first request with this key is still running; retry in a few seconds and the original response is replayed.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The thread, blocked.

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The key was already used in the last 24 hours with a different request body.

The first request with this key is still running; retry in a few seconds and the original response is replayed.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

The thread, unblocked.

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

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.

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

The key was already used in the last 24 hours with a different request body.

The first request with this key is still running; retry in a few seconds and the original response is replayed.

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.