Troubleshooting
Common Analytics Server error codes
The following error codes are returned by Rosette when accessing an endpoint.
Error Code | Meaning | Description | |||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
400 | Bad Request | There was something wrong with your request, or the language was not supported by the endpoint. | |||||||||||||||||||||||||||||||||||||||||||||||
403 | Forbidden | Access denied. This could be based on plan, limits, or profiles. [a] | |||||||||||||||||||||||||||||||||||||||||||||||
404 | Not Found | The specified URI could not be found | |||||||||||||||||||||||||||||||||||||||||||||||
405 | Method Not Allowed | You tried to access Analytics with an invalid method | |||||||||||||||||||||||||||||||||||||||||||||||
409 | Incompatible Client Version | Your binding was out of date. Please update to the latest version. | |||||||||||||||||||||||||||||||||||||||||||||||
413 | Too Much Data | Your payload was bigger than the size limit of 600KB, or 50K characters. | |||||||||||||||||||||||||||||||||||||||||||||||
429 | Too Many Requests | Slow down! Analytics can only process one call at a time. [a] | |||||||||||||||||||||||||||||||||||||||||||||||
500 | Internal Server Error | There is a problem with your server. | |||||||||||||||||||||||||||||||||||||||||||||||
[a] applies to cloud instances only | |||||||||||||||||||||||||||||||||||||||||||||||||
Troubleshooting 400 errors
There can be multiple causes of a 400 error. Listed here are some common issues customers have encountered.
400 Bad Request Format Error possible causes:
You are passing in text in a language that the endpoint doesn’t support. Try setting the
languageJSON request parameter to the three-letter code of the language of your text, and make sure the endpoint supports it by checking the documentation. You can also check theX-RosetteAPI-ProcessedLanguageheader in the response to see what language Rosette thinks your text is in.You’ve passed in an empty string or an invalid character.
You didn’t pass in required parameters, like a
targetLanguageto the /name-translation endpoint, or eithercontentorcontentUrito others.
400 NonWorkingURI Returned from Valid URL
Sometimes sophisticated sites block our URL text extractor, thinking it's a bot. The workaround is to copy the text from the webpage and pass it as text in the 'content' parameter.
"Language xxx not supported"
This error is raised If no language is specified in a call, and Analytics cannot detect the language. xxx is the language code returned when an endpoint cannot determine the language.