NOT_FOUND - Blujay API

HTTP status	Retryable
`404`	No

What happened

The resource or route does not exist in your workspace, or, on a participant removal, the handle is not in the group. Resources in other workspaces are reported as not found.

How to fix it

Check the ID and the path. IDs are scoped to the workspace that owns the credential.

Example response

An illustrative example. The message wording and the contents of details vary; branch on error.code.

{
  "status": "error",
  "error": {
    "code": "NOT_FOUND",
    "message": "Not found",
    "type": "not_found",
    "http_status": 404,
    "retryable": false,
    "doc_url": "https://docs.blujay.io/errors/not-found",
    "details": []
  },
  "trace_id": "trc_8f2a1c0e4b7d",
  "timestamp": "2026-10-14T17:30:48.000Z"
}

Still stuck?

Email support@blujay.io with the trace_id from the error response. See Errors for the response format.