HTTP 400 errors are returned with a JSON that always contains a user-friendly and localized error message.

In addition many errors include an ID that describes the reason for the error. In your software code you may want to parse this ID to decide how to react best.

Login specific errors

During connection, you may encounter these IDs. In all these cases the login failed.

Error ID	Description
LOGIN_FAILED	Raised by the api/connect method, typically if the account ID, login or password are invalid. The message text informs the user that Account ID, Login or Password are invalid. Note: This code is also returned if the the Wordbee Translator platform uses SSO, This is not supported by the API.
LOGIN_DISABLED	Login failed because the user credentials are disabled in Wordbee Translator. Too many invalid login attempts, Wordbee platform itself is no longer valid, etc. The message text asks the user to connect online to see further information.
LOGIN_EXPIRED	Login failed because the user's password has expired and must be renewed online. The message text asks the user to connect online.
LOGIN_BADIP	Login failed because the caller IP address is not permitted. Access to the API may be restricted by IP address ranges. The message text asks the user to contact the platform administrator.
LOGIN_NOACCESS_DOMAIN	Login failed because the user is not given access to the functionality of the requested "domain". The user credentials are valid though.

Post Edit specific errors

Error ID

Description

PE_FILE_ONLINE_ONLY

This error id is used with API - IT - Post Edit Download

When you download a post edited file, you may get this error ID. This means that the download can only be done online, from Wordbee Translator. See API method above for full description.

Other errors

Error ID	Description
NOT_AUTHORISED	User is not authorised to access the functionality.
SESSION_EXPIRED	The API session has expired. This will be shown when you did not call any API method with your token for a longer period. Make sure to not persist and reuse tokens. The call sequence should always be: Connect to API and obtain token Do your API calls Disconnect to invalidate token
BAD_PARAMETERS	The API may raise this error if API parameter values are invalid. Developer information is included with the "info" property of the error JSON.
OTHER	Points to other problems. Developer information is included with the "info" property of the error JSON.

Browser not supported