Loading...
Loading...
Best for individual realtime requests
Synchronous single
Use synchronous single requests for individual requests, such as a realtime chat or customer support response.
Loading...
We use essential storage to operate Lexel Translate. With your permission, we also use analytics, advertising, and marketing technologies. Read our Cookie Policy.
Loading...
Translate Features
Lexel Translate provides a practical translation layer for apps, communities, marketplaces, support tools, and developer workflows. Try for free, then scale with our APIs.
Native request example
POST /api/v1/translateUse the native API for realtime product copy, support flows, and user-facing text that needs protected terms, placeholder safety, and visible request accounting.
Request example
{
"request_id": "req_translate_demo_001",
"src": "en-Latn",
"tgt": "fr-Latn",
"content_mode": "plain",
"preserve_placeholders": true,
"do_not_translate": ["{name}"],
"input": {
"items": [
{ "txt": "Open a support ticket for {name}." }
]
}
}Response example
{
"ok": true,
"request_id": "req_translate_demo_001",
"operation": "translate",
"source_language_tag": "en-Latn",
"source_language_name": "English",
"detection_confidence": 0.99,
"output": {
"kind": "single",
"single": {
"translation": "Ouvrez un ticket d'assistance pour {name}.",
"src": "en-Latn",
"tgt": "fr-Latn"
}
},
"usage": {
"input_characters": 33,
"output_characters": 42
},
"warnings": []
}Workflow Choice
Explore a variety of synchronous and asynchronous APIs to handle all your translation needs.
Best for individual realtime requests
Use synchronous single requests for individual requests, such as a realtime chat or customer support response.
Best for groups of realtime requests
Send multiple items in one request for comments, product labels, listings, or other small bulk actions that still need an immediate response.
Best for large queued workloads
Queue long-running workloads when request timeouts, provider limits, or callback-driven workflows make normal request-response handling difficult.
Best for uploaded files
Directly translate large files without the hassle of extracting content from structural elements.
Consistency
Automatically preserve terminology, placeholders, and structure across requests.
Pin approved terminology with stored glossaries and version-aware selections.
Protect names, variables, and technical strings.
Built-in handling of structured formats to avoid syntax errors.
Pin product names, domain language, and approved translations so repeated requests stay aligned with your terminology.
Protect names, SKUs, commands, variables, and technical terms that should survive translation exactly as written.
Keep placeholders, tokens, URLs, and template variables intact with proactive safeguards.
Translate HTML, Markdown, JSON, and CSV workflows through extraction-aware handling instead of treating product content like one flat text blob.
Operations
Easily track usage, inspect logic, and verify operational status through the dashboard and APIs.
Use user-defined request identifiers to trace individual requests through every processing stage.
Easily compare usage for specific requests and aggregate usage across API methods against remaining quota to avoid budget overages.
Handle queued workloads with polling, callbacks, and reusable webhook profiles for reliable downstream automation.
Configured translation routes can use secondary providers when their primary provider is unavailable.
Request lifecycle
Receive request
Validate the native envelope, language tags, and request-scoped controls.
Apply protections
Resolve glossary choices, protected terms, placeholder handling, and structured-content extraction.
Execute translation
Dispatch through the main path or queued workflow that matches the request shape and runtime limits.
Return visibility
Emit a stable response with request_id, translated output, warnings, and usage totals.
Migration
Start with compatibility paths while you validate behavior and then move to the native API for a cleaner API contract.
Use our compatibility routes for Google, DeepL, and Microsoft Translator to try Lexel Translate with almost no code change. Just update the URL and API key.
Migrate to the native Lexel Translate API when you want direct access to batch requests, asynchronous requests, glossaries, and structured-content behavior.
Start from TypeScript helpers, Python helpers, and the documented request-response contract instead of reverse-engineering behavior from ad hoc examples.
Test each API individually with no commitment. Migrate in steps that work best for your needs.
Coverage
Review supported tags and pair guidance before you commit migration or production rollout work.