Lexeri API
REST API for termbases, terms, usage examples, topics, exports and term checks.
Lexeri Developer Portal
Your terminology – via API, CLI and MCP.
References, guides and examples for everyone who integrates Lexeri into their own applications, build pipelines, workflows and AI assistants.
POST/term_checks/liveRequest
curl -X POST https://api.lexeri.com/term_checks/live \ -H "Authorization: Bearer $LEXERI_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{"locale_code": "en", "text": "Check the cooling water tank regularly."}'200 OKResponse
not_recommendedcoolant reservoirpreferredResponse shortened – all fields are in the API reference.
Quickstart: your first request in three steps
Create an API token
As an admin in the termbase settings, API tab. A token is valid for one termbase; it requires an Enterprise license.
Termbase › Settings › API
Send the token in the header
Lexeri uses bearer authentication. All endpoints share the same base URL and respond with JSON.
Authorization: Bearer <API-TOKEN>https://api.lexeri.comCheck your first text
Send a text and its locale code. You get back the terms found with their status – and, for terms that are not recommended, the preferred term.
POST/term_checks/live
Areas
What do you want to integrate?
Five entry points, each with a reference, step-by-step guides and examples.
Resources for developers
Tools for your everyday development work – so wrong terms never make it into a release.
CLI tool
@lexeri/check-cli
Checks files in CI pipelines against your termbase and exits with code 1 on forbidden terms.
$ npx --yes @lexeri/check-cli --locale en docs/*.mdNode.js 20+ · token via
LEXERI_API_TOKEN
Automations with the n8n node
@lexeri/n8n-nodes-lexeri
Term checks, searches and exports as steps in your own workflows – triggered by Lexeri events or by your systems.
VS Code & Visual Studio extensions
Visual Studio Marketplace
Check UI texts, resource files and documentation while you code – without leaving the IDE.
MCP in GitHub Copilot
mcp.json · VS Code
Copilot Chat in agent mode searches terms, checks texts and creates term suggestions in Lexeri.
VS Code 1.99+ · MCP enabled in the GitHub organization
MCP server
Brings your termbase into any AI assistant that supports the Model Context Protocol.
Server URL
https://mcp.lexeri.com/mcpHTTPConfiguration in VS Code · mcp.json
{ "servers": { "lexeri": { "type": "http", "url": "https://mcp.lexeri.com/mcp" } }}Tools (selection)
- search_for_terms
- check_text_for_term_matches
- get_termbase_information
- create_a_term_request
- create_a_task
- list_all_topics
- list_supported_locales
n8n node & Blackbird.io
Terminology in automations and translation workflows – without building your own integration.
n8n Community Node
- In n8n: Settings › Community Nodes › Install
- Enter the package:
@lexeri/n8n-nodes-lexeri - Create “Lexeri API” credentials with your API token
Operations
- Check Terminology
- Search Terms
- Get Termbase Info
- Export Termbase
- Import Terms
- Extract Terms from Documents
- Create Term Request
- List Topics
- Add Terms to Topic
Lexeri Trigger – events
- Term created or changed
- Term entry changed
- Term request created or completed
- Task completed
- Term extraction, import or check completed
Blackbird.io
Lexeri as a building block in translation and content workflows on Blackbird.io.
- Check terminology
- Extract terms from documents
- Export terminology
Apps: check texts from your application
Hand documents or texts from your own software to the Lexeri apps for Windows and macOS and have them checked for correct terminology there.
Windows app
BetaYour application
Lexeri Windows app
macOS app
BetaAaSelected textCheck text with LexeriShow result
Questions about the API or integrations?
Write to us at service@lexeri.com or have a look at the help center.