SignEnvoy docs
Sign in Start in the sandbox

Error reference Account suspended, the API is read-only

Error reference

Account suspended, the API is read-only

Writes are refused while the workspace is suspended, for billing or for review.

Problem type /problems/tenant-suspended
HTTP status 403
Emitted by REST API (/v1)
Title values
Subscription suspended. The API is read-only
This account is suspended pending review. The API is read-only
Trigger
REST API (/v1): suspended tenant, write refused (B-3)

What happened

The workspace is suspended, and the request was not a read (GET, HEAD, or OPTIONS). The response is HTTP 403.

What it means

Reads continue so you can fetch envelopes and download sealed copies; sends and other writes are refused. Signing pages for already sent envelopes keep working, so anyone who already holds a signing link can still sign. A suspension on your account is not their problem.

There are two causes, and the response’s title tells you which one applies.

  • “Subscription suspended”: billing. A payment failed and was not fixed within 7 days. Envelopes already out can still be signed until day 37, when the workspace returns to the free sandbox and anything still out for signature is cancelled, with its signers told. (Cancelling a subscription does not suspend anything: it runs to the end of the month and then returns to the sandbox.)
  • “This account is suspended pending review”: the account was suspended pending a review of how it is being used, under the acceptable use policy. Paying an invoice does not lift this one.

What to do next

For a billing suspension, update the payment method from Settings, Billing before day 37. Once the invoice is paid, writes resume with the same keys. After day 37 the workspace is in the sandbox: live keys are revoked, and going live again asks for the unpaid balance first. Once live again, create new live keys on the API keys page; webhook signing secrets are rotated for you.

For a suspension pending review, reply to the notice you received or contact support. The two are tracked separately on purpose: a review is not resolved by a payment, and a payment is not resolved by an appeal.

Problem body

Every error the API returns is an RFC 9457 problem document with media type application/problem+json. The type member is the stable identifier to switch on; docs_url is this page. 

{
  "type": "/problems/tenant-suspended",
  "title": "This account is suspended pending review. The API is read-only",
  "status": 403,
  "instance": "/v1/...",
  "docs_url": "https://staging.signenvoy-docs-b4g.pages.dev/errors/tenant-suspended"
}