Caching

Langbly caches translations in Redis to reduce latency and upstream costs.

What’s cached

• The per-string result (translatedText, and detectedSourceLanguage when applicable)
• Cache key is based on: source (or auto), target, format, exact input-array boundaries, and output-affecting options such as formality, glossary, context, and custom instructions
• Plain requests without account-specific customization may use a hashed cross-account key; requests with glossaries, instructions, context, or account translation memory stay account-scoped

TTL (default)

• 1 hour for eligible translation results
• 24 hours for responses stored under an idempotency key

If you need caching disabled or a different TTL, contact support@langbly.com.