Help
FAQ
Frequently asked questions about the Multilingual Dictionary.
1. Getting Started
How do I get an API key?
Visit the API Access page to submit an application. Select your desired tier (Free, Basic, or Pro), fill in your details, and we will review and contact you within 1–3 business days.
What does a typical API call look like?
curl -H "Authorization: Bearer $YOUR_API_KEY" \ "https://my-multilingual-dictionary.deoliste.workers.dev/api/translation?word=天气"
What is the response format?
Responses are returned as JSON. Each translation object contains a
word field and a translations map keyed by ISO 639-1 language codes (en, fr, de, es, etc.). Each language array holds up to 5 translation variants.2. Search Behavior
Can I search in any language?
Yes. The API supports search in any supported language — Chinese, English, French, German, Spanish, Portuguese, Italian, Russian, Arabic, Japanese, Korean, and more. You can search for a Chinese word to find translations in all languages, or search for an English word to find the corresponding Chinese entry.
What happens if no result is found?
The API returns HTTP 200 with an empty translations object:
{ word, translations: {} }. This means the word is not in the current dictionary. Consider submitting it via the contribution form on the homepage.Does cross-language search work?
Yes. If you search for a word that appears as a translation rather than a headword, the API will still find the matching entry. For example, searching “bonjour” will return the French word entry with all its translations. This works in any language — search English to find Chinese, search French to find Japanese, and so on.
What is the difference between exact match and translation match?
The API always checks for an exact word match first. If none is found, it searches all stored translations. The first matching result is returned. This two-step lookup ensures you get the most relevant result regardless of which language you search in.
3. Rate Limits & Billing
What are the rate limits?
| Tier | Per Minute | Monthly Cap |
|---|---|---|
| Free | 5 requests/min | 1,000 /month |
| Basic | 60 requests/min | 50,000 /month |
| Pro | 300 requests/min | 500,000 /month |
What happens if I exceed my rate limit?
The API returns HTTP 429 with a descriptive error message indicating which limit was exceeded (per-minute or monthly). Upgrade your tier if you need higher limits.
Do limits reset automatically?
Yes. Per-minute counters reset every 60 seconds. Monthly counters reset on the first day of each calendar month.
4. Data & Content
How many languages are supported?
The dictionary currently covers 11 languages: Chinese (zh), English (en), French (fr), German (de), Spanish (es), Portuguese (pt), Italian (it), Russian (ru), Arabic (ar), Japanese (ja), and Korean (ko).
How is the dictionary data sourced?
Translations are compiled from CC-CEDICT (Chinese–English) and Wiktionary (English–other languages), both released under Creative Commons licenses. All data is reviewed through our contribution and approval workflow before being published.
Can I contribute new translations?
Yes. Use the contribution form on the homepage to submit translations for any word. Submissions are reviewed by administrators before being added to the dictionary. Every verified contribution helps improve coverage for everyone.
What are the maximum translations per language?
Each language supports up to 5 translation variants per word. This provides variation without overwhelming API consumers with redundant options.
How often is the dictionary updated?
The dictionary is updated as contributions are approved. We do not have a fixed update schedule — new translations are published after passing the review process.
5. Reference Resources
Where can I learn more about API usage?
Visit the API Documentation for the complete reference, including parameter descriptions, error codes, code examples, and language code reference.
I found a bug or have a suggestion — where do I report it?
Contact us via the GitHub repository linked in the footer, or reach out through the contact link. We welcome feedback from developers and API users.
Still have questions?