Sign in to run requests with your own sandbox key. Sign in
403 Forbidden

live_mode_forbidden — Live mode forbidden

Message “Live mode requires production access.”

What causes it

  • The request asked for `execution_mode: "live"` (trigger, batch create) but the account has not been approved for production data.
  • The request used a docs key (the key these docs pages mint for you when you are signed in). Docs keys are sandbox-only: they never run live, even on an approved account. The message then reads "Docs keys are sandbox-only, so they never run live. Use a key from /api-keys for live mode."
  • A live-mode batch or execution is being resumed, retried, or re-evaluated by an account that no longer holds production access.
  • A live-mode review decision was attempted, either by an account without production access or after the original submitter lost it ("Live-mode review cannot resume because the original submitter no longer has production access.").

How to fix it

  1. Omit `execution_mode` or send `"test"`. Test mode runs every cascade at no charge, on mock data or on a registered test subject's authored reports.
  2. With a docs key, use a key from /api-keys (or the Cascades app) for live runs. Keep the docs key for test mode.
  3. Request production approval from your Cascades contact. Approval is manual; there is no self-serve switch. Once approved, your /api-keys key works for live mode. Docs keys never do.
  4. For a blocked review resume, have an approved user on the account record the decision.

Operations that return it

Example response

HTTP/1.1 403 Forbidden · Content-Type: application/json

403 Forbidden
{
  "error": {
    "code": "live_mode_forbidden",
    "message": "Live mode requires production access.",
    "details": [
      {
        "field": "execution_mode",
        "message": "live mode requires production access"
      }
    ],
    "request_id": "6f1c2a3e-8d4b-4c5e-9f0a-1b2c3d4e5f60",
    "doc_url": "https://cascades.crscreditapi.com/docs/api/errors/live_mode_forbidden"
  }
}