Skip to main content
General·HTTP 404·API

Route not found

route_not_found

No API route matches this path.

What this means​

The path has a typo, uses the wrong version prefix, or names an endpoint that doesn't exist.

How to fix it​

Check the path against the API reference.

Retry behavior​

Sending the same request again gets the same answer.

How it appears in the response​

ComputeSphere returns errors as RFC 7807 Problem Details. The type field is the docs URL for this page — switch on code in your client.

{
  "type":    "https://computesphere.com/docs/errors/route_not_found",
  "title":   "Route not found",
  "status":  404,
  "code":    "route_not_found",
  "detail":  "No API route matches this path.",
  "instance": "/v2/…",
  "request_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "trace_id":   null
}

The Content-Type header is application/problem+json. On field-level validation errors a non-empty errors[] array also appears, each entry carrying a docs_url to its error code's page.