Troubleshooting API error codes
This article lists the most common error codes that you may encounter when you use the Language I/O API.
Note: 4xx codes typically indicate user errors. 5xx codes typically indicate server-side errors.
Some error codes may come with a message that explains why the error occurred. For example, if you requested an operation in a language that is not configured in your account, a "400 - Bad Request" could show an additional message that explains this, and how to solve it or contact support. You can find a list of API error messages you may encounter below.
List of common error codes
Error Codes | Troubleshooting |
400 - Bad Request | The server cannot process the request due to an apparent client error. Review your request and contact your Customer Success Manager if the problem persists. |
401 - Unauthorized | Authentication failed. Check your x-api-key header and try again, or reset your API key. If the problem persists, contact your Customer Success Manager. |
500 - Internal Server Error | An unexpected condition was encountered and the request could not be fulfilled. Wait a few minutes and try again. If the problem persists, contact your Customer Success Manager. |
501 - Server Not configured | This server error is likely caused by user error (for example, using GET when the server expects POST ). Review your request to make sure that you are using the correct HTTP method. |
528 - Unsupported Locale | The locale value that you entered in your request is not supported by Language I/O. Try again with another value. Remember that language codes must be formatted as such: xx-xx (for example, the correct language code for French is "fr-fr", not "fr"). |
537 - Unexpected Error | An unexpected condition was encountered and the request could not be fulfilled. Wait a few minutes and try again. If the problem persists, contact your Customer Success Manager. |
List of API error messages you may encounter
Message | Error Code | How can I resolve it? |
Translation request limit reached. Trial users can only translate up to %d words. | 409 | If you have reached your trial limit but want to continue using the API, contact a Language I/O Customer Success Manager. They will help you find a plan suitable for your use case. |
We were unable to detect the language of the message. | 501 | The detectLocale operation failed. Try again and if the problem persists, contact Support. |
The translation request was missing the source content. | 502 | Make sure that sourceContent is specified in your request and try again. |
We were unable to write the translation record to the database. | 503 | There was an issue during the translation. Try again and if the problem persists, contact Support. |
We were unable to complete the translation with the provided target language(s). | 506 | There was an issue during the translation. Try again and if the problem persists, contact Support. |
No vendors support the language pair for the given translation type %s, source locale %s, and target locales %s. | 508 | The language pair that your requested is not supported. Try again with different locales. |
Your account has been disabled. Please contact your Language I/O representative. If you think this is a mistake, please contact support@languageio.com | 509 | If you have reached the end of your trial period but want to continue using the API, contact a Language I/O Customer Success Manager. They will help you find a plan suitable for your use case. |
Your account is not configured to support %s translation or translation from %s to target language(s) %s. If you think this is a mistake, please contact support@languageio.com | 515 | Contact Support to configure the required languages to your account. |
The source language '%s' is the same as the target language '%s'. | 517 | Make sure that the source and target values in your request are different languages and try again. |
The %s API rate limit has been exceeded. Please try again in %s seconds. If this continues to happen, please contact support@languageio.com | 520 | API Rate Limits reset after a certain period of time. Wait ten minutes and try again. If the problem persists, contact Support. |
It doesn't look like your account is setup for the locale value specified in your request. If you want us to add support for these languages, please contact support@languageio.com | 528 | Contact Support to configure the required locales to your account. |
Oops. It doesn't look like a target language was provided, so we don't know how you want this translated. Please provide a target language to your request and try again. | 529 | Make sure that a target locale is specified in your request and try again. |
The contentTypeName '%s' is not supported. Please set a valid contentTypeName and try your request again. | 530 | Make sure that the contentTypeName value is "api" and try again. |
We couldn't find an rnRepsonseProject with id '%s'. Please check this is correct and try again. If you believe you shouldn't be getting this error, please contact support@languageio.com | 531 | Double check that the rnRepsonseProject id is correct and try again. |
No source locale was provided. We could not complete the translation. | 532 | Make sure that a source locale is specified in your request and try again. |
Your account isn't setup to support the locale '%s' requested. | 534 | Contact Support to configure the required locales to your account. |
Translation type '%s' not supported. Please try a different translation type. If you believe you shouldn't be getting this error | 535 | Make sure that the translationType value is "machine" and try again. |
An unexpected internal server error has occurred. | 537 | An unexpected condition was encountered and the request could not be fulfilled. Wait a few minutes and try again. If the problem persists, contact your Customer Success Manager. |
No Project found with the provided id | 538 | Double check that the rnRepsonseProject id is correct and try again. |
No Project found with the provided project id and customer id | 539 | Double check that the rnRepsonseProject id is correct and try again. |
Comments
0 comments
Article is closed for comments.