WORKSPACE_HEADER_NOT_ALLOWED - Blujay API

HTTP status	Retryable
`400`	No

What happened

The request sent a Blujay-Workspace header, but the credential isn’t a reseller partner key, or the endpoint acts for the partner itself (/v1/partner/*).

How to fix it

Send Blujay-Workspace only with a partner key on customer endpoints. Remove it for /v1/partner/* and for every other credential.

Example response

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

{
  "status": "error",
  "error": {
    "code": "WORKSPACE_HEADER_NOT_ALLOWED",
    "message": "Blujay-Workspace header not allowed here",
    "type": "validation",
    "http_status": 400,
    "retryable": false,
    "doc_url": "https://docs.blujay.io/errors/workspace-header-not-allowed",
    "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.