DocsNothing is translated4 min read
Nothing is translated
In order of how often it is the answer. Each one is checkable in under a minute.
| symptom | cause | fix |
|---|---|---|
| First paint is English, then it changes | Working as designed | nothing — or preload() at startup |
| Every string stays English forever | 401: the key is wrong, revoked, or from another environment | the console prints the first 15 characters of what it was given |
| 403 origin_not_allowed in the browser | Your origin is not in the project list | add http://localhost:5173 etc. in the dashboard |
| Works on the server, fails in the browser | The key is test, or the origin list is empty and the browser sends none | issue a live key for the client, a test key for CI |
| Same word, wrong meaning on one screen | Called with no context while another screen used a context | pass screen:<name> consistently |
| 402 after a good week | The monthly character meter is spent | usage is in the body; upgrade or wait for the reset |
| One string never translates | Longer than 500 characters, or only control/bidi characters | split long copy upstream; the SDK truncates and warns |
| 503 now and then | The model is down | expected: the string is filed in the Inbox anyway |
| "Translated with Siyak" you did not want | Free plan attribution | it disappears on an approved plan, and never attaches to an approved string |
Ask a person
Support → New ticket. Include the month, the project name and, for a browser, the Origin you are calling from — the first two are what any answer needs, and the third resolves half of all 403 reports without a reply.
# What the SDK prints is enough for a ticket; it never logs a full key. [siyak] invalid_api_key (HTTP 401) — key: sk_live_9f2c1a… (first 15 characters only)