# not-found

# `not-found`

**HTTP 404.** No endpoint matches the method and path you requested.

```json
{
  "type": "https://developers.supliful.com/errors/not-found",
  "title": "Resource not found",
  "status": 404,
  "detail": "No route matches GET /v1/order.",
  "instance": "/v1/order"
}
```

The `detail` names the method and path we received, which is usually enough to spot the problem by comparing it with what you meant to send.

## What it is not

This means *the route does not exist*, not *the thing you asked for does not exist*. It is a routing failure, so it is returned before any authentication or lookup happens — you will see it whether or not you sent a valid key.

## How to fix it

- **Check the version prefix.** Every endpoint is under `/v1`. A path without it will never match.
- **Check the method.** The same path can exist for one method and not another; `detail` shows the method we saw.
- **Check for a trailing slash or a doubled segment.** `//v1/me` and `/v1//me` are different paths from `/v1/me`.
- **Compare against the [API Reference](/api).** It is generated from the served routes, so anything listed there exists and anything absent does not.

If you are calling an endpoint you were told about but cannot find in the reference, it has not shipped yet. Ask us at [help@supliful.com](mailto:help@supliful.com) rather than building against it.

## Retry behaviour

Terminal. Retrying an unmatched path cannot start matching.