Resource Not Found

resource-not-found · 404

The 404 the API's OpenAPI document advertises for every resource, which no route sends today.

Every other missing resource answers a type of its own, such as project-not-found. All of them carry resourceType and resourceId.

Besides the members every error carries, this type adds resourceType and resourceId.

Common causes

  • The resource is missing, or not visible to the caller.

How to fix the call

  • Match type on the -not-found suffix rather than on this slug, so every missing resource is handled the same way.
  • Check the id in the path against resourceId, which names the resource that was looked up.
  • See every missing-resource type on the index.

Example response

json
{
  "type": "resource-not-found",
  "title": "Resource Not Found",
  "detail": "Resource with ID '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad403' was not found",
  "resourceType": "Resource",
  "resourceId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad403",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/environments/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad403/env/resolved",
  "method": "GET",
  "instance": "GET /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/environments/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad403/env/resolved",
  "status": 404,
  "docs": "https://ghaym.me/docs/errors/resource-not-found"
}