How can we help?
Search our knowledge base or browse common questions below.
No. Langbly is an independent company. We offer a Google Translate v2-compatible API, which means you can switch from Google Translate by changing a single endpoint URL. No code changes required.
We support over 100 languages, including all major European, Asian, and Middle Eastern languages. Check our documentation for the full list, or send a test request to see if your language pair is supported.
Langbly uses context-aware translation that understands full sentences, not just individual words. For most language pairs, quality is comparable to or better than traditional machine translation services. We recommend testing with your own content to judge the results yourself.
Billing is based on the number of input characters you send (the "q" parameter). Everyone gets 500K characters per month for free. Above that, usage costs $5 per 1M characters. You only get charged when your accumulated balance reaches $5. If your balance stays under $5, it carries over to the next month.
Without a payment method, your API stops at 500K characters per month. With a payment method, usage above 500K is billed at $5 per 1M characters. There are no hard limits. You only get charged when your balance reaches $5.
Manage API billing and payment details from the billing page in your dashboard. The first 500K input characters each month remain included; contact support if you cannot access the current billing portal.
Yes. Enterprise plans come with custom volumes, dedicated support, and SLA guarantees. Contact us through the contact form and we will put together a proposal.
Each request can contain up to 50 text strings. Character limits depend on your plan: 10,000 (free/trial), 25,000 (PAYG), or 50,000 (paid plans). Server processing timeout is 15 seconds; we recommend setting your client timeout to 45 seconds. Every response includes timing headers (x-processing-time-ms, x-timeout-ms) for full visibility. See our Timeout & Retry Guide in the docs for retry strategies and code examples.
Yes. You can send multiple text strings in a single request using the "q" parameter as an array. This is more efficient than making separate requests and counts as a single API call.
Yes. Official SDKs for Python (PyPI) and JavaScript/TypeScript (npm) are available. Both include auto-retry, typed errors, and Retry-After support. You can also use the REST API directly from any language.
Yes. All traffic is encrypted with TLS 1.3. Source text is not written to application databases or logs. To speed up repeated requests, eligible translated responses may be cached in Redis for up to one hour; idempotent responses may be retained for up to 24 hours. Customer content is never used to train models.
No. Your translation content is never used to train, fine-tune, or improve any model. This is a permanent commitment.
You can create, rotate, and revoke API keys from your dashboard at any time. Each key is verified on every request. You can have multiple active keys per account.
Yes. eu.langbly.com provides EU data residency for translation processing and temporary storage. Google Cloud processing uses regions in EU member states and the temporary Redis cache is in Frankfurt.