route_not_found
404 not_found. No route under /api/ matches the method and path you sent.
| HTTP status | type | Surfaces |
|---|---|---|
| 404 | not_found | REST, GraphQL |
What it means
No route under /api/ matches the method and path you sent.
| When |
|---|
no such route under /api/ on the host you reached |
What to do
Check the path against the API reference.
The response
HTTP 404:
{
"error": {
"type": "not_found",
"code": "route_not_found",
"message": "No route GET /api/entry.",
"docs": "https://docs.capacms.com/errors/route_not_found"
},
"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 |
|---|---|---|
| 404 | 404 | GraphQL is switched off on this host, for a GET. A POST then answers 405 mutations_not_enabled in the REST envelope, as every write to an unknown /api/ path does |