Errors / no_account_context

No account context

HTTP 400invalid_requestno_account_context

The credential is valid but is not bound to an account.

What to do

Use a token minted for a specific account. The account is never a field in the request — it is carried by the credential, which is what stops one customer reading another’s data by changing an id.

What it looks like

{
  "error": {
    "type": "invalid_request",
    "code": "no_account_context",
    "message": "…",
    "doc_url": "https://docs.textmast.com/errors/no_account_context",
    "request_id": "req_01j8xk2p7n4qc3m9v0wz5bt6ay"
  }
}

Quote the request_id if you get in touch. It is on every response, including this one, and it turns a support email into a single log query rather than an archaeology exercise.