Project Not Found

project-not-found · 404

The API found no project by that identifier in the workspace the call ran in.

One that is in another workspace answers this same 404, never a 403, so it can't be told apart from one that doesn't exist. resourceId repeats the identifier the API looked up. The path takes the project's id or its slug, and resourceId is the one sent.

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

Common causes

  • The identifier is wrong: a typo, a cut-off id, or one copied from another workspace.
  • The project was deleted between the call that listed it and this one.
  • The call ran in another workspace than the one that holds it: a call runs in the workspace its X-Ghaym-Workspace header names, or a stream's ?workspace=<id> when the header is absent.

How to fix the call

  • Read resourceId and compare it with the value you meant to send.
  • List them again with ghaym cloud projects list and take the identifier from that answer, not from a cached or typed value.
  • If the identifier is right and recent, send X-Ghaym-Workspace with the workspace that holds it.
  • Don't retry unchanged: the same call answers the same 404 for as long as nothing changes.

Example response

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