> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digitalseaservice.com/llms.txt
> Use this file to discover all available pages before exploring further.

# not_found

> HTTP 404 — the URL or resource doesn't exist.

```http theme={null}
HTTP/1.1 404 Not Found
Content-Type: application/problem+json
X-Request-Id: req_01HV9XK...

{
  "type": "https://docs.digitalseaservice.com/errors/not_found",
  "title": "Resource not found",
  "status": 404,
  "detail": "Authenticated user not found in DSS records.",
  "instance": "req_01HV9XK..."
}
```

## What it means

Either the URL path doesn't match any route we serve, or the resource
identified by the URL doesn't exist (or hasn't been created yet).

## Common causes

| Cause | Fix |
| - | - |
| Typo in the path (`/v1/me/seatime` vs `/v1/me/sea-time`) | Check the [API reference](/api-reference). |
| Missing API version prefix (`/me/sea-time` vs `/v1/me/sea-time`) | Always include `/v1`. Future versions ship under `/v2`. |
| User has no sea time record yet | `GET /v1/me/sea-time` and `/recent` return **200** with zero totals and an empty `months` array. Do not treat this as unreachable. |
| User has no vessel history yet | `GET /v1/me/vessels` returns **200** with an empty `vessels` array. |
| Sandbox test user doesn't exist | Sandbox is seeded with a small set of test users. Use one of those. |

## What to do

Distinguish these two cases:

* **Route doesn't exist** — programming error, fix the URL.
* **Resource doesn't exist** — render an empty state. Don't retry. A
  Connected member with no sea days yet gets `200` zeros on sea-time
  endpoints, then `webhook user.sea_time.updated` when the first day lands.

## Related

* [API reference](/api-reference)
* [Errors overview](/errors)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.