Every request is made with an API key that belongs to one manilo account. You decide what each key may do and how much it may spend.
Pass the key as a bearer token in the Authorization header. Always use HTTPS and never put the key into a URL.
curl https://app.manilo.ai/api/v1/jobs/ \
-H "Authorization: Bearer $MANILO_API_KEY"
Keys are created in the manilo app under API access. A key starts with mnl_live_ and is shown exactly once. manilo stores only a hash, so a lost key cannot be recovered: revoke it and create a new one.
A key only works for the scopes it was created with. A request outside its scopes is answered with 403.
| Scope | Allows |
|---|---|
files:write | Upload, inspect and delete IDML files, create upload links |
translations:write | Create quotes, start, cancel and delete translations |
jobs:read | List jobs, read their status, download results, create download links |
glossary:write | Read, add and delete glossary entries |
tm:read | Read translation memory statistics and entries |
billing:read | Read the account balance |
A reporting tool that only watches jobs needs jobs:read alone. A translation integration needs the first three.
A sandbox key starts with mnl_test_. It runs the complete flow, from upload and quote to job, download and webhook, but nothing is translated and nothing is charged. The result files are unchanged copies of your upload.
test_mode: true. The quote still shows the real price, so you can test how you display it.API keys are limited to the translation workflow. Regardless of scopes, a key cannot log in to the app, change account or security settings, top up the balance, read invoices or create further keys. Those actions require a personal login.
Each key can have a monthly limit in EUR. Running jobs count as reserved, so several jobs started at the same time cannot exceed it together. The counter resets at the start of each calendar month (UTC).
A quote reports the remaining limit as api_key_limit_remaining. If the limit or the account balance does not cover a quote, starting it returns 402 and nothing is charged.
A key may send 120 requests per minute. Beyond that the API answers 429 with a Retry-After header. Polling a job every few seconds stays far below this.
Errors are JSON objects with a detail field that describes the problem.
| Status | Meaning |
|---|---|
400 | Invalid request, for example an unsupported language or a file that is not valid IDML |
401 | Missing, unknown, expired or revoked API key |
402 | Account balance or the key's monthly limit is not sufficient |
403 | The key lacks the required scope |
404 | Unknown resource, or one that belongs to another account |
410 | The quote has expired. Request a new one |
413 | File larger than 100 MB |
422 | Request body does not match the schema |
429 | Rate limit exceeded |
Two kinds of URL work without an API key, because the URL itself is the permission: one-time upload links and signed download links. Both expire on their own (upload links after 30 minutes, download links after 24 hours). Share them only with the person they are meant for.
Applications that connect through the MCP server with a sign-in do not need a key from you. You approve them once on a manilo page, choose a monthly limit, and can disconnect them at any time under API access. They are bound by the same scopes, limits and rules as API keys.
Try the quickstart or look up an endpoint in the API reference.