Errors / unauthenticated
Not authenticated
No credential was presented, or the one presented is not valid.
What to do
Send Authorization: Bearer . If you are using a session token rather than an API key, it may simply have expired — refresh it. A key that worked yesterday and 401s today has usually been revoked; check the API keys screen.
What it looks like
{
"error": {
"type": "authentication",
"code": "unauthenticated",
"message": "…",
"doc_url": "https://docs.textmast.com/errors/unauthenticated",
"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.
Related
- Invalid credentials — That email and password combination was not accepted.
- Invalid refresh token — The refresh token was unknown, already used, or belongs to a family that has been revoked.