Capainvalid_version
400 invalid_request. Capa-Version names a date Capa does not serve.
| HTTP status | type | Surfaces |
|---|---|---|
| 400 | invalid_request | REST, GraphQL |
What it means
Capa-Version names a date Capa does not serve.
| When | What the hint tells you |
|---|---|
Capa-Version is not a supported date | the versions that exist |
What to do
Use one of the dates in the hint.
The response
HTTP 400:
{
"error": {
"type": "invalid_request",
"code": "invalid_version",
"message": "Capa-Version 2026-13-99 is not a supported version.",
"param": "Capa-Version",
"hint": "Supported versions: 2026-10-01.",
"docs": "https://docs.capacms.com/errors/invalid_version"
},
"meta": {
"version": "2026-10-01",
"contract": 1,
"requestId": "req_0f3c…"
}
}On GraphQL
/api/graphql answers the same code inside errors[].extensions. The status depends on the Accept header you send (status codes):
application/json | graphql-response+json | When |
|---|---|---|
| 400 | 400 | Capa-Version names no version |