Skip to content

4xx Client error

404 Not Found

The server can't find anything at this URL.

What 404 means

The resource doesn't exist, or the URL is wrong. Some APIs also return 404 for resources you're not allowed to see.

Common causes

  • A typo in the path, or a missing or extra slash.
  • The wrong API version (/v1 vs /v2) or base URL.
  • The resource was deleted, or the ID is wrong.

How to fix it

If you're calling an API

  • Copy the endpoint from the docs and compare it character by character.
  • Check the API version and base URL.
  • Confirm the ID exists (list the collection first).

If you run the server

  • Return a helpful JSON error body, not an HTML page, from API routes.

Should you retry?

No: the URL won't start working by itself.

Example response

HTTP
HTTP/1.1 404 Not Found
Content-Type: application/problem+json

{
  "type": "about:blank",
  "title": "Not Found",
  "status": 404,
  "detail": "The server can't find anything at this URL."
}

Defined in: RFC 9110 (HTTP Semantics). 404 is a client error: change the request before retrying.

Debugging an API call? Convert your request with the cURL converter, check the response with the JSON formatter, or see whether the API is down on its status page.

Often confused with

HTTP 404 FAQ

What does HTTP 404 mean?

404 Not Found: The server can't find anything at this URL. The resource doesn't exist, or the URL is wrong. Some APIs also return 404 for resources you're not allowed to see.

Is 404 a client or server error?

It's a client error (4xx): something about the request needs to change before it can succeed.

How do I fix a 404 error?

Copy the endpoint from the docs and compare it character by character. Check the API version and base URL. Confirm the ID exists (list the collection first).

Should I retry after a 404?

No: the URL won't start working by itself.

Other 4xx status codes

All HTTP status codes