Authentication & Quota Management
To access the Taia Public API, you must include a valid API key in every request.
This guide explains how to authenticate, which plans support the API, and how usage is measured.
⚠️ API access is available only to Pro plan users and organizations.
Free and Basic plan users do not have access to API functionality.
🔐 Authentication
Each request must include the following header:
Authorization: Api-Key YOUR_API_KEY
You can find and manage your key in the web app under: Settings → API Access
🔑 API Key Scope
Your API key is tied to:
- A specific user account
- The organization/team context (if applicable)
- The active Pro subscription under which usage will be counted
Future versions may allow scoped or expiring keys.
📦 Subscription Requirements
| Plan | API Access | Translation Memory / Glossary | CAT Tool |
|---|---|---|---|
| Free | ❌ | ❌ | ❌ |
| Basic | ❌ | ❌ | ❌ |
| Pro | ✅ | ✅ | ✅ |
Only Pro plan users and organizations can:
- Use the API
- Access glossaries and translation memory
- Leverage the CAT Editor and task-based workflows
📈 Quota Enforcement
Usage is counted per organization (or user if no org exists).
Pro Plan Default:
- 100,000 words/month
- Applies to AI translation via API and app
- Quotas renew monthly (on billing cycle date)
Additional Notes:
- Words are counted after file conversion
- Professional services (human) are not yet available via API
- Overages are blocked unless upgraded
📉 Rate Limits
To ensure platform stability:
| Metric | Limit |
|---|---|
| Requests per minute | 30 |
| Concurrent jobs | 3 |
| Max file size | 100 MB |
| Max target langs | 10 per request |
Exceeding limits returns 429 Too Many Requests.
Use exponential backoff or retry headers to wait.
🛑 Common Errors
| Code | Error Message | Cause |
|---|---|---|
| 401 | Unauthorized | Missing or invalid API key |
| 403 | Forbidden | Plan does not include API access |
| 429 | Too Many Requests | Exceeded rate or concurrency limits |
| 402 | Quota Exceeded | Monthly word limit reached |
| 400 | Invalid parameters | Missing fields or unsupported language |
🧠 Tips
- Do not expose your API key in frontend code or public repos
- Rotate keys periodically if used in CI/CD or automation
- Combine quota-aware automation with polling and async status tracking
Need help with authentication, quotas, or scaling API usage? Contact us →