Live mode needs a subscription

This workspace is in the sandbox, where test keys work in full and live keys do not.

Problem type	`/problems/live-mode-unavailable`
HTTP status	402
Emitted by	REST API (/v1)
Title values	`Live mode is not available` `This workspace is in the sandbox. Test keys work in full; live sending needs a subscription`
Trigger	REST API (/v1): a live key on a sandbox workspace (D92, ES-20). Retires `envelope-allowance-exhausted`: since D91 there is no allowance, so no send is refused for volume

What happened

A live envelope was asked of a workspace that cannot send live right now. It is in the sandbox: it never went live, or its subscription ended or lapsed. The response is HTTP 402, and nothing was created or sent. The same workspace’s test keys keep working normally.

What it means

Every workspace starts in the sandbox: test keys are free and unlimited, for as long as you want them. Sandbox envelopes are watermarked and are not legally binding, which is why a live key is a separate decision rather than a switch. Nothing about the sandbox expires, and no data is lost by staying in it.

Live sending is billed per envelope with a monthly minimum. GET /v1/me reports status, the rate and the minimum, and what the current month has cost so far.

What to do next

Go live from Billing in the dashboard. A workspace that was live before keeps its old live API keys revoked when it goes live again: create new live keys on the API keys page. Its webhook signing secrets are rotated for it, and each new secret is shown once on the webhooks page. If there is an unpaid balance, Billing asks for it first. Your test keys are unaffected. If you meant to stay in the sandbox, use a test key: reads, sealing, webhooks, and the whole API behave the same.

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.