404 Not Found

What does 404 Not Found mean?

The server cannot find the requested resource. It belongs to the 4xx Client Error class, which means the request contains bad syntax or cannot be fulfilled. Something about the request needs to change.

When do APIs return 404?

A typo in the path, a missing API version prefix, a resource that was deleted, or an ID that belongs to a different account.

How to fix a 404 Not Found

Check the path character by character, including the version segment such as /v1/ and whether the API expects a trailing slash. Confirm the resource ID exists and is visible to your credentials — some APIs deliberately return 404 instead of 403 for resources you cannot see, to avoid leaking their existence.

Reproduce a 404 response

The fastest way to understand a status code is to trigger one and read the full response. Open the API tester and send a request to https://httpbin.org/status/404 — you will see the 404 status along with every response header the server sent. Comparing those headers against a working request is often what reveals the cause.

When you are debugging a real endpoint, check the response headers as carefully as the body, and confirm you are using the right HTTP method for the operation.

Related 4xx status codes