Resource Not Found

not-found · 404

No route matched the request, so the endpoint itself doesn't exist on the API.

A missing resource on a route that does exist answers a type of its own, such as project-not-found, so the two cases differ without reading prose.

This type adds no members to the ones every error carries.

Common causes

  • The path is misspelled, or is missing the /v1 prefix.
  • The method is wrong for a path that does exist, such as a POST to a collection that only serves GET.
  • The endpoint was assumed rather than looked up. The HTTP API has no public reference, so an endpoint that seems obvious may not exist.

How to fix the call

  • Compare path with the one you meant to call, prefix included.
  • Don't probe for endpoints by trying variations. Drive Ghaym through the ghaym CLI instead.

Example response

json
{
  "type": "not-found",
  "title": "Resource Not Found",
  "status": 404,
  "detail": "The requested endpoint '/v1/projcts' does not exist. Please check the API documentation for available endpoints.",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projcts",
  "method": "GET",
  "instance": "GET /v1/projcts",
  "docs": "https://ghaym.me/docs/errors/not-found"
}