# unsupported-version

<Badge variant="warning">400 Bad Request</Badge> <Badge variant="muted">unsupported-version</Badge>

| Field           | Value                                                |
|-----------------|------------------------------------------------------|
| **Type URI**    | `https://docs.kordiam.app/docs/errors/unsupported-version` |
| **HTTP Status** | `400 Bad Request`                                    |

## Description

The API version in the request is not supported or invalid, or the `API-Version` header's major
version does not match the version in the URL path.

## Response Example

```json
{
  "type": "https://docs.kordiam.app/docs/errors/unsupported-version",
  "title": "Unsupported API Version",
  "status": 400,
  "detail": "API version '3.0' is not supported.",
  "instance": "/api/v2/elements",
  "traceId": "abc-123-def",
  "requestedVersion": "3.0",
  "supportedVersions": ["2.0"]
}
```

## Common Causes

- Typo in the version segment of the URL (for example `/api/v3/...`)
- Requesting an `API-Version` value that is not supported
- Sending an `API-Version` header whose major version does not match the path major version
- Requesting a preview or restricted version that is not enabled for the current client

## How to Fix

Use a supported `/api/v{major}/...` path and, if you send `API-Version`, keep it within the same
major version and request only versions enabled for your client or environment.