api_version_invalid API Origin: Application & API OSI layer 7 · Application Last updated 12 Oct 2026

API Error: Invalid or unsupported API version

The API version you requested — in the URL, a header or the SDK config — doesn’t exist or has been retired.

Exact message you may see Invalid API versionUnsupported API versionThe requested API version is not supportedAPI version is no longer supported
Seen on: REST API

Meaning

Versioned APIs pick behaviour from a path prefix (/v1, /v2), a header (Stripe-Version, X-GitHub-Api-Version, api-version query on Azure) or a dated version string. Old versions are eventually sunset, and a typo or future date is rejected outright.

SDKs pin a version too, so upgrading the SDK can change the version you send.

Common causes

  • Typo or invalid date in the version header/parameter
  • Version retired (sunset) by the provider
  • Mixed: path version and header version disagree
  • Old SDK pinned to a removed version

⚡ Quick fix

  1. Use a currently supported version from the provider’s changelog
  2. Set the version in one place (SDK config or header)
  3. Upgrade the SDK if it targets a retired version

Detailed fix by platform

REST API

  1. bash
    curl https://api.github.com/repos/o/r -H 'X-GitHub-Api-Version: 2022-11-28'
    curl https://api.stripe.com/v1/charges -u "$KEY:" -H 'Stripe-Version: 2024-06-20'

How to diagnose

  1. Sent version — Which header/path/param is actually sent?
  2. Supported — Provider’s list of active versions
  3. SDK — Version pinned by the SDK

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

1000 — Cloudflare Error 1000: DNS points to prohibited IP (Cloudflare)10001046 — MySQL ERROR 1046 (3D000): No database selected (MySQL)10461049 — MySQL ERROR 1049 (42000): Unknown database 'x' (MySQL)10491153 — MySQL ERROR 1153 (08S01): Got a packet bigger than 'max_allowed_packet' bytes (MySQL)11533D000 — FATAL: database "x" does not exist (PostgreSQL)3D000400 — HTTP 400 Bad Request (HTTP)400410 — HTTP 410 Gone (HTTP)410413 — HTTP 413 Content Too Large (Request Entity Too Large) (HTTP)413api_versi…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.