lexiQA exposes its data via an Application Programming Interface (API), so developers can interact in a programmatic way with the lexiQA application.
The API calls are REST-compliant and make use of the most common HTTP methods
Below you can find a sample of these API calls. In order to have access to the entire API documentation, please contact us.
GET/supportedLocales
Returns an array with the supported locales for this lexiQA instance. Amongst these, a bilingual file with any combination of source/target locales can be used in lexiQA.
GET/tooltipwarnings
Get the descriptions for the error classes supported for the running version of the lexiQA server. \"s\" entries contain the warning message for the source text. \"t\" entries contain the warning message for the target text.
POST/project/v1/createWithData
Creates a new project with the data included in the request. Uses Basic Authentication. Please use your user and lexiqa_key as username/pass. This is a non-blocking call. After a 201 return code, one must check for the project completion status (see Project Status). The "data" field should contain an array of objects, with a required source text field (st) and a target text (tt). If there is no translation, the tt field should be an empty string. The ID of each segment should be unique for this project. The "spellcheck" field enables/disables spellcheck.
POST/project/v1/addSegments
Add segments included in the request. Uses Basic Authentication. Please use your user and lexiqa_key as username/pass. This is a non-blocking call. After a 201 return code, one must check for the project completion status (see Project Status). The "data" field should contain an array of objects, with a required source text field (st) and a target text (tt). If there is no translation, the tt field should be an empty string. The ID of each segment should be unique for this project. If a segment with a provided ID already exists in the project, the original source/target text will be kept.
POST/project/v1/addSegments
Add segments included in the request. Uses Basic Authentication. Please use your user and lexiqa_key as username/pass. This is a blocking call. The "data" field should contain an array of objects, with a required source text field (st) and a target text (tt). If there is no translation, the tt field should be an empty string. The ID of each segment should be unique for this project. If a segment with a provided ID already exists in the project, the original source/target text will be kept.
POST/project/v1/create
Creates a new project with the attached tmx/xliff file. Uses Basic Authentication. Please use your user and lexiqa_key as username/pass. This is a non-blocking call. After a 201 return code, one must check for the project completion status (see Project Status).
GET/project/v1/status?id={projectid}
Checks the project status, if QA has finished and the project is ready to use (get warnings/perform QA on changed segments, etc.). Requires Basic Authentication.
GET/project/v1/params?id={projectid}
Retrieves project settings. Requires Basic Authentication.
POST/project/v1/update
Updates a list of projects with the data included in the request. Uses Basic Authentication. Please use your user and lexiqa_key as username/pass. This is a blocking call. The "spellcheck" field enables/disables spellcheck.
POST/project/v1/statistics
Retrieves the statistics for one or more projects contained in the request. Requires Basic Authentication.
GET/project/v1/warnings?id={projectid}
Retrieves the segments with warnings (along with the warning data) for the id in the request. Requires Basic Authentication.
POST/glossary/v1/createWithFile
Creates a monolingual brandnames or blacklist glossary with an xls/xlsx/txt file. Creates a new termbase with an xls/xlsx/csv/tab-separated txt file.
POST/segment/v1/qa
Requires Basic Authentication.
POST/warnings/v1/ignore
Requires Basic Authentication.
POST/warnings/v1/undoIgnore
Requires Basic Authentication.
GET/warnings/v1/spellingSuggestions?word={word}&locale={locale}
Requires Basic Authentication.