Meet the new Scripe, live on October 7.Register

API v1 · 4xx

version_unsupported

HTTPWhen
400The Scripe-Api-Version header carries an unknown value. Omitting the header is fine — it defaults to the current version.

We accept at least the two most recent date-stamped versions at any time. Sunset of older versions is announced via the Scripe-Deprecation response header at least 90 days before the sunset date — see conventions.md §versioning.

The accepted versions are listed in the message; this code carries no details object, so parse the message rather than reading error.details:

json
{
  "error": {
    "code": "version_unsupported",
    "message": "Unknown 'Scripe-Api-Version' value '2020-01-01'. Supported versions: 2026-08-01, 2026-08-10.",
    "request_id": "req_…",
    "docs_url": "https://docs.scripe.io/api/v1/errors#version_unsupported"
  }
}

To recover:

  1. Pin a supported version in your client config.
  2. If you're upgrading, smoke-test in staging against the new version header before you cut over production.
  3. If you got here because we sunset a version, find the deprecation notice in the Scripe-Deprecation header captured before the cutover, or contact support — we always email integrators ahead of any sunset.