Fehlercodes
Ursachen und Lösungen für Authentifizierungs-, Kontingent- und Parameterfehler.
| Status | Meaning | Body |
|---|---|---|
| 401 | No token sent | {"message":"Missing API key in request"} |
| 401 | Invalid token | {"message":"Invalid API key in request"} |
| 403 | Token disabled | {"message":"API key is disabled"} |
| 403 | Token expired | {"message":"API key has expired"} |
| 403 | Plan does not include WebSocket | {code, error, message} |
| 404 | Path not supported | — |
| 405 | Not a GET request | {code, error, message} |
| 429 | Per-minute or daily limit exceeded | {code, error, message}; see the Retry-After header |
| 502 / 503 | Upstream temporarily unavailable | {code, error, message}; retry shortly |
The 401 bodies are identical to the iTick API. 4xx responses from the upstream, such as parameter errors, are forwarded unchanged in the iTick format.
When you receive 429, wait the number of seconds given by the Retry-After header before retrying instead of resending immediately.