Common Rosette Server error codes
The following error codes are returned by Rosette when accessing an endpoint.
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 language
JSON 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 the X-RosetteAPI-ProcessedLanguage
header 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 targetLanguage
to the /name-translation endpoint, or either content
or contentUri
to 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 Rosette cannot detect the language. xxx
is the language code returned when an endpoint cannot determine the language.