New v2.0 Released

Google Translate v2 Compatible API

Use the same v2 endpoint shape, with caching, idempotency, HTML support, and usage-based billing on input characters.

No credit card required
500K free characters (30 days)
api.langbly.com/language/translate/v2
Request ExampleExample
POST /language/translate/v2~15s timeout
curl -X POST "https://api.langbly.com/language/translate/v2" \
-H "X-API-Key: tr_live_..." \
-d '{ "q": "Hello world.", "target": "es" }'
// Response
{
  "data": {
    "translations": [
      { "translatedText": "Hola mundo." }
    ]
  }
}
Cache TTL
7d
Request Budget
20s

Built for modern engineering teams

Everything you need to localize your app without the complexity.

Privacy-First Data Handling

No request-body storage in our database. API keys verified via Unkey. Traffic encrypted in transit (TLS).

HTML Tag Support

Translate text nodes while keeping HTML tags intact using the format=html parameter.

Auto-Language Detection

Automatic source language detection when the source parameter is omitted.

Formality Control

Fine-tune output with the optional formality parameter (formal/informal/neutral).

Reliability

Resilient by Design.

Retries + circuit breaker handle upstream issues gracefully. Redis caching reduces cost and stabilizes repeated requests. Optional fallback routing is available when configured.

  • Retries + Circuit Breaker

    Retries (up to 2 by default) and circuit breaking patterns reduce error spikes.

  • Redis Caching

    Frequently requested translations are served from cache with a 7-day TTL.

  • Idempotency-Key

    Safe client retries without accidental double-charging or duplicate work.

Reliability Signals
illustration
Uptime
N/A
P95 Latency
N/A
Cache Hit
N/A
Redis cache
Serves hot translations
Retries
Smooths transient failures
Circuit breaker
Prevents cascading failures
Circuit breaker OK
Idempotency-safe
GDPR Compliant99.9% SLAZero Data RetentionEU Data Residency

Built for trust and compliance

EU-hosted infrastructure, GDPR-compliant by design, and powered by renewable energy.

EU Data Residency

Dedicated EU endpoint in Finland. All translation processing, storage, and caching stays within the European Union.

Learn more →

GDPR-Compliant

No request body storage. Minimal data retention. API keys verified through secure token infrastructure. All traffic encrypted with TLS.

Learn more →

Green Infrastructure

Our data centers in the Netherlands and Finland run on 83-98% carbon-free energy with industry-leading efficiency.

Learn more →

Ready to scale your translations?

Join developers building global applications with Langbly API.

From the Blog

Insights on translation technology and building multilingual products.

·7 min read

Custom Instructions for Translation APIs: Tell the Model Exactly How to Translate

Most translation APIs give you zero control over the output. You send text, you get a translation, and you hope it fits your context. Langbly now lets you pass custom instructions with every request. Here is how it works and why it changes the way you handle translations.

·11 min read

React i18n with a Translation API: Automating Translations in React Apps

How to connect a translation API to your React i18n workflow. Covers react-i18next setup, automated string extraction, API integration for generating translations, and a CI/CD pipeline that keeps translations in sync.

·9 min read

LibreTranslate vs Google Translate vs Langbly: Self-Hosted vs API Translation

A practical comparison of LibreTranslate (self-hosted, open-source) against Google Translate and Langbly. Covers real translation quality, hosting costs, language support, and when self-hosting makes sense.

“

Works with our existing Google v2 client in minutes.

Alex Chen
Alex Chen
CTO at GrowthFlow