Authentication

All Translation API endpoints (except /health) require an API key passed in the request header.

The X-API-Key header

X-API-Key: key_live_XXXXXXXXXXXXXXXXXXXX

The header name is case-insensitive. Both x-api-key and X-API-Key are accepted.

Managing keys

Keys are created and revoked in the portal:

1. Open your project in app.i18nme.com.
2. Go to the API Keys tab.
3. Click Generate key — give it a descriptive label (e.g. production-web).
4. Copy the key immediately. It is shown only once.

To revoke a key, click the Delete icon next to it. Revocation takes effect immediately — in-flight requests using the revoked key will receive 401.

Key scope

Each key is scoped to a single project. It cannot be used to access translations from other projects.

Security best practices

• Never commit keys to source control. Use environment variables or a secrets manager.
• Rotate keys regularly. Create a new key, deploy it, then revoke the old one.
• Use separate keys per environment (production-web, staging-web, etc.) so you can revoke one without affecting others.
• Server-side only for write operations. The Translation API is read-only — keys used in the browser expose only translation data.

Error responses

Status	Meaning
401 Unauthorized	Key missing, malformed, or revoked
403 Forbidden	Key is valid but does not belong to this project
429 Too Many Requests	Daily rate limit exceeded — see Rate limits