Workspace Header Required

workspace-header-required · 400

The call named no workspace, so nothing ran.

Every workspace-scoped call sends X-Ghaym-Workspace with the workspace's id; listing, creating and renaming workspaces need none. The API picks no workspace for a call that leaves it out.

Besides the members every error carries, this type adds header.

Common causes

  • The call was sent without X-Ghaym-Workspace, from a script or client that builds its own requests.

How to fix the call

  • List the caller's workspaces with ghaym cloud workspaces list and send one of those ids in X-Ghaym-Workspace.
  • An EventSource can't send headers: on the streams GET /v1/services/<service>/logs, GET /v1/deployments/<id>/logs, GET /v1/agent-sessions/<id>/stream, add ?workspace=<id> instead.
  • From the CLI, add --workspace <id>.

Example response

json
{
  "type": "workspace-header-required",
  "title": "Workspace Header Required",
  "detail": "Name the workspace this request runs in with the X-Ghaym-Workspace header.",
  "header": "X-Ghaym-Workspace",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects",
  "method": "GET",
  "instance": "GET /v1/projects",
  "status": 400,
  "docs": "https://ghaym.me/docs/errors/workspace-header-required"
}