Error handling
Response codes
LanguageWire Project API uses conventional HTTP response codes, as defined in the RFC 2616 and RFC 6585 to indicate the success or failure of an API request.
In general:
- Codes in the 2xx range indicate success.
- Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter missing, a upload failed, etc.).
- Codes in the 5xx range indicate an error coming from LanguageWire servers (these are rare).
Frequent error codes
These are some of the common error codes you might get while using our Project API, along with additional information about how to resolve them.
| HTTP Status Code | Parameter | Error | Solution |
|---|---|---|---|
| 404 | /account_invalid | The account ID provided as a value for the company-account is invalid. | Check that your requests are specifying a valid ID account. |
| 401 | /api_key_expired | The API key provided has expired, hence the system cannot recognise you. | Obtain new API keys from the Dashboard. |
| 400 | /language_code_invalid | The source or target language code is not correct. | Check and apply the Language recommendations to your tags. Then, submit the request again. |
| 404 | /parameter_unknown | The request contains one (or more) unknown parameters. | Remove these and try again. |
| 429 | /rate_limit_exceed | You send too many requests in a limited period (Rate limit has been applied). | Wait 15 minutes and retry. |
| 500 | /InternalServerError | There is a temporary error in our server. | Wait 15 minutes and retry.If persists, contact your assigned Project Manager. |
| 504 | /GatewayTimeout | The request cannot be completed as the operation is taking too long. | Refresh or wait 15 minutes and retry. |
Something missing? If you are experiencing any other error that is not listed in this page, share it with us so we can investigate and take further actions.