# Langbly

> Translation tools for developers and translators. Context-aware translation API (drop-in compatible with the Google Translate v2 spec) and a Translation Hub for document translation.

Langbly is an independent translation API designed as a drop-in replacement for the Google Translate v2 API. Switch by changing one endpoint URL, no code changes required. Supports 100+ languages with context-aware translation that understands full sentences instead of word-by-word output.

## Key Facts

- API compatible with Google Translate v2 (same endpoint format, same response schema)
- Context-aware translation that handles full sentences and document context
- $5 per 1M additional input characters versus Google Cloud Translation Basic's published $20 rate (75% lower)
- The first 500,000 input characters each month are included; payment details are required to activate API access
- Pay-as-you-go above the included 500K input characters with threshold billing
- 100+ languages supported
- HTML preservation (translates text, keeps markup intact)
- Formality control (formal, informal, neutral)
- Language detection endpoint
- SDKs for Python (PyPI: langbly) and JavaScript/TypeScript (npm: langbly)
- Document translation for 15 file formats (DOCX, PPTX, XLSX, PDF, SRT, HTML, etc.)
- Public integrations: Crowdin Store, n8n, Strapi, WordPress (Loco Translate and TranslatePress), and Drupal TMGMT
- GitHub Action: v1.2.0 is publicly available in GitHub Marketplace
- Manual or pre-marketplace integrations: Make and Zapier
- Independent company based in the Netherlands, not affiliated with Google

## Links

- [Homepage](https://langbly.com)
- [API Documentation](https://langbly.com/docs/)
- [Pricing](https://langbly.com/pricing/)
- [Translation API cost calculator](https://langbly.com/tools/translation-api-cost-calculator/)
- [MCP server for AI assistants](https://langbly.com/integrations/mcp/)
- [MCP setup and tool documentation](https://langbly.com/docs/mcp/)
- [Quick Start guide](https://langbly.com/docs/quickstart/)
- [Authentication](https://langbly.com/docs/authentication/)
- [Translate v2 endpoint reference](https://langbly.com/docs/translate-v2/)
- [Languages endpoint reference](https://langbly.com/docs/languages/)
- [Language quality tiers](https://langbly.com/docs/quality/)
- [Migration guide from Google Translate](https://langbly.com/docs/guide-migrate-google-translate-api/)
- [DeepL API vs Langbly](https://langbly.com/compare/deepl-api-vs-langbly/)
- [Document translation overview](https://langbly.com/docs/document-translation/)
- [Translation Hub overview](https://langbly.com/translation-hub/)
- [Google Translation Hub alternative & migration guide (shutdown September 20, 2026)](https://langbly.com/blog/google-translation-hub-alternative/)
- [Google Translation Hub migration checklist (download)](https://langbly.com/downloads/google-translation-hub-migration-checklist.md)
- [Glossaries](https://langbly.com/docs/glossary/)
- [Translation Memory](https://langbly.com/docs/translation-memory/)
- [Custom instruction sets](https://langbly.com/docs/instruction-sets/)
- [Python SDK on PyPI](https://pypi.org/project/langbly/)
- [JavaScript SDK on npm](https://www.npmjs.com/package/langbly)
- [GitHub organization](https://github.com/Langbly)
- [FAQ](https://langbly.com/faq/)
- [Status page](https://langbly.com/status/)
- [Security overview](https://langbly.com/security/)
- [Privacy policy](https://langbly.com/privacy/)
- [Terms of service](https://langbly.com/terms/)
- [Data processing agreement](https://langbly.com/dpa/)
- [EU data residency](https://langbly.com/eu-data-residency/)
- [Contact](https://langbly.com/contact/)
- [Compare: Best Translation API 2026](https://langbly.com/compare/best-translation-api/)
- [Compare: Google Translate API alternatives](https://langbly.com/compare/google-translate-api-alternatives/)
- [Compare: DeepL API alternatives](https://langbly.com/compare/deepl-api-alternatives/)
- [Compare: Google Translate vs DeepL](https://langbly.com/compare/google-translate-api-vs-deepl-api/)
- [Cheapest translation APIs in 2026](https://langbly.com/blog/cheapest-translation-api/)
- [Switch from Google Translate](https://langbly.com/switch-from-google-translate/)

## API Quick Start

Base URL: `https://api.langbly.com`

### Translate Text

```
POST /v2/translate
Headers: Authorization: Bearer YOUR_API_KEY
Body: { "q": "Hello world", "source": "en", "target": "nl", "format": "text" }
Response: { "data": { "translations": [{ "translatedText": "Hallo wereld" }] } }
```

### Detect Language

```
POST /v2/detect
Headers: Authorization: Bearer YOUR_API_KEY
Body: { "q": "Bonjour le monde" }
Response: { "data": { "detections": [[{ "language": "fr", "confidence": 0.98 }]] } }
```

### Supported Languages

```
GET /v2/languages?target=en
```

## Pricing

| Plan | Cost | Included | Overage |
|------|------|----------|---------|
| Included usage | $0 | 500,000 characters per month | Payment details required for activation |
| Pay-as-you-go | $0 base | 500,000 characters per month | $5 per 1M characters |

No base fee, no annual lock-in. Threshold billing means you are only charged when your accumulated balance reaches $5.

## Data Handling and Residency

`eu.langbly.com` provides EU data residency. Translation processing uses Google Cloud regions in EU member states, while the temporary Redis cache is in Frankfurt. The Netherlands is the configured default, not the only EU region.

Source text is not written to application databases or logs. Eligible translated responses may be cached in Redis for up to one hour; idempotent responses may be retained for up to 24 hours. Document-translation results are available for up to 24 hours. Customer content is not used for model training.

## Machine-readable data

Structured summaries for programmatic use:

- Service overview: https://langbly.com/ai/service.json
- Common questions: https://langbly.com/ai/faq.json
- One-line summary: https://langbly.com/ai/summary.json
- OpenAPI specification: https://langbly.com/openapi.json

## Contact

Email: [hello@langbly.com](mailto:hello@langbly.com)