Errors / internal_error
Internal error
Something broke at our end. It was not your request.
What to do
Retry — with the same Idempotency-Key if you were sending, so a request we actually processed before failing cannot become a second message. If it keeps happening, send us the request_id: it is in this response, and it is the difference between a one-query answer and a guess. The exception itself is never in the message, because those leak table names and file paths.
What it looks like
{
"error": {
"type": "api_error",
"code": "internal_error",
"message": "…",
"doc_url": "https://docs.textmast.com/errors/internal_error",
"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
- Not found — No such route, or no such resource on this account.