Version
GET

Get the recovery allowances

/v1/recovery/allowances in the Disaster Recovery API.

curl https://api.subscriby.net/v1/recovery/allowances \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

One row per kind, plus the window they are counted in.

  • self_service_remaining is what the rolling window still allows on its own; grant_remaining is what support has released on top and not yet spent. remaining is their sum and allowed whether a recovery of that kind would start right now.
  • uses_grant is true when the next recovery would spend a support grant rather than the self-service allowance.
  • next_self_service_at is when the self-service allowance returns, null while it is available. last_used_at is when the kind was last recovered inside the window.

See Allowances and support review for the rule and what support audits before releasing a grant.

GET
/v1/recovery/allowances

The token must hold this ability, or the call is refused with 403.

Runs the same action from an agent, behind the same ability.

Authorization

bearerToken
AuthorizationBearer <token>

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

Responses

200OK

Array of RecoveryAllowanceResource

401Unauthorized

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

403Forbidden

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.

429Too many requests

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