Langbly API Documentation
Langbly provides a Google Translate v2 compatible endpoint you can call from your app to translate text (or HTML) into a target language.
Base URLs
| Endpoint | Base URL | Best for |
|---|---|---|
| Global | https://api.langbly.com | Worldwide access |
| EU data residency | https://eu.langbly.com | Processing and temporary storage in the EU |
Both endpoints use the same API format. See EU Data Residency for details.
Main endpoint
POST /language/translate/v2
Start with Quickstart to get an API key and run your first request.
Frequently asked questions​
Is Langbly a drop-in replacement for Google Translate?​
Yes, if you already use the Google Translate v2 API, you can switch by changing two things: the base URL (to api.langbly.com or eu.langbly.com) and the API key. The request and response format are identical, so you do not need to rewrite any parsing logic.
Do I need to detect the language before translating?​
No. If you omit the source field from your request, the API automatically detects the source language as part of the same translation call. No separate detect step is required.
Can I translate HTML or entire documents?​
Yes. Set format to "html" in your request to translate HTML content while preserving markup. For whole documents (DOCX, PPTX, XLSX, PDF, and more), use the dedicated document translation endpoint instead of sending individual strings.
Which base URL should I use?​
Use api.langbly.com for global traffic. Use eu.langbly.com if you require data residency within the European Union. Both endpoints accept the same POST /language/translate/v2 format.