Disaster Recovery API

200 with the standby.

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 the resource keeps no standby; error.context.resource_id names it.

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 standby, 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: for a group, a resource without a standby, a plan without the feature, or a caller who is not the project owner.

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.

When the caller is not the project owner.

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 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.

200 with 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 auto_failover is switched on without accepts_email_fee: true or without the Growth plan, when the caller is not the project owner, or when email_delivery is not self or platform.

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 CSV, one member per row.

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.

When the caller is not the project owner.

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 checklist.

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.

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, newest first by default.

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.

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 status is not open, resolved or all.

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 incident.

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, newest first by default.

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.

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 kind or status is not one of its values.

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 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 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 counters.

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.

Array of RecoveryAllowanceResource

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.

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 summary.

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.

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 handshake.

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.

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.

When the handshake is no longer pending; error.context.handshake_id names it.

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.

202 with resource_id and status: request_sent.

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.

When the resource is a perk rather than a place, the creator cannot be reached on the connector, the plan lacks the feature, or the caller is not the project owner; error.context.resource_id names it.

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.

200 with the recovery operation the swap ran under.

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.

For a resource without a standby, an allowance already spent for a degraded resource, or a caller who is not the project owner.

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.

202 with resource_id and status: request_sent.

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.

When the resource is a perk with nothing to replace, the creator cannot be reached on the connector, or the caller is not the project owner; error.context.resource_id names it.

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.

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.

When the caller is not the project owner.

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 operation, its undo state 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. On this endpoint: RESOURCE_NOT_FOUND: when resource_id is not a resource the token manages.

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: for a bot replacement, a channel recovery with no resource_id, a closed window, a swap already put back, or a recovery that is not the token owner's; error.context.operation_id names it.

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 operation_id and how many reminders were nudged.

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.