Connectors API

Array of ConnectorListingResource

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.

When status names no lane; error.context.accepted lists the lanes.

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

200 with the card.

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. On this endpoint: RESOURCE_NOT_FOUND: when nothing is known by that key; error.context.connector echoes it.

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 ConnectorInstallationResource

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.

200 with the installation.

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. On this endpoint: RESOURCE_NOT_FOUND: with reason: unknown_connector when the key names no connector at all, so a client can tell a typo from a connector that is not set up here. CONNECTOR_NOT_INSTALLED: when the connector exists but the project does not run it.

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. On this endpoint: RESOURCE_NOT_FOUND: with reason: unknown_connector, or 404 CONNECTOR_NOT_INSTALLED when the project does not run the connector.

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.

200 with the preview.

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. On this endpoint: RESOURCE_NOT_FOUND: with reason: unknown_connector, or 404 CONNECTOR_NOT_INSTALLED when the project does not run the connector.

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

201 with the installation; 200 when it was already installed.

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. On this endpoint: CONNECTOR_TIER_REQUIRED: for a second distinct connector on the project when the **project owner's** plan lacks the multi_connector capability (Growth). The owner's plan is read, never the token holder's, because Teams lets a member run someone else's project.

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. On this endpoint: RESOURCE_NOT_FOUND: with reason: unknown_connector when the key names no connector.

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

When the key names no connector creators may install today: only a card whose installable is true qualifies; error.context.connector echoes the key.

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.

200 with the report.

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. On this endpoint: RESOURCE_NOT_FOUND: with reason: unknown_connector, or 404 CONNECTOR_NOT_INSTALLED when the project does not run the connector.

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.

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.

200 with the installation as recorded.

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. On this endpoint: RESOURCE_NOT_FOUND: with reason: unknown_connector, or 404 CONNECTOR_NOT_INSTALLED when the project does not run the connector.

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.

200 with the report.

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. On this endpoint: RESOURCE_NOT_FOUND: with reason: unknown_connector, or 404 CONNECTOR_NOT_INSTALLED when the project does not run the connector.

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.

200 with the report.

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. On this endpoint: RESOURCE_NOT_FOUND: with reason: unknown_connector, or 404 CONNECTOR_NOT_INSTALLED when the project has no installation of the connector.

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

While the installation is pending or disconnected.

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.

200 with the installation.

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. On this endpoint: RESOURCE_NOT_FOUND: with reason: unknown_connector, or 404 CONNECTOR_NOT_INSTALLED when the project does not run the connector.

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 both settings and capabilities are missing, a settings key the connector never declared is sent, a declared rule fails, or a capability is undeclared or cannot be switched off; error.fields names the key.

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.