Content & Documents · Integration
Lokalise
Add Lokalise to your product for your customers, and give your AI agents governed access to it.
Lokalise's API at api.lokalise.com/api2 authenticates with an X-Api-Token header rather than a bearer token, and everything hangs off a project ID that is a long hex string with a colon and branch suffix when branching is enabled. The objects are projects, keys, translations, languages, contributors, screenshots and tasks, and a key is unique per platform, so the same string on iOS, Android and web can be one key with per-platform filenames or three separate keys depending on how the project was set up. File upload and download are asynchronous: you queue a job and poll the process ID, and treating the upload response as a completed import is a common mistake. Translations carry a state such as unverified or reviewed, and bulk updates through the keys endpoint are capped per request, so large catalogues need chunking. Rate limits are enforced per token across the whole team. fastn stores each customer's Lokalise token and project scope separately and keeps the connection maintained as tokens rotate.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Lokalise project so strings from your product sync into their workflow
Push new or changed source strings from your app and pull back completed translations per language
Show translation completeness per language inside your own release checklist
Attach screenshots to keys so translators see where a string appears in your interface
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent create keys and upload source strings but require approval before deleting any key
Have an agent report which languages are blocking a release, with each project read audited per tenant
Let an agent mark translations as reviewed only for the projects a tenant has granted
Example prompt
Which languages in our Lokalise project still have untranslated keys for the next release?
Set up Lokalise in 4 steps
- 01Enable the Lokalise connector from your fastn dashboard.
- 02Have each customer authorise their own Lokalise account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Lokalise integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Lokalise integration without building it. Your customers connect their own Lokalise account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Lokalise update is not your on-call problem.
- One integration serves your product and your agents. The same governed Lokalise connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Notion
Box
DocusignOften used alongside
Tools the same teams tend to run next to Lokalise, across other categories.
Shopify
Stripe
Jira
AsanaLokalise integration FAQ
How do I add a Lokalise integration to my product?
Enable the Lokalise connector in your fastn dashboard, then let each customer authenticate their own Lokalise account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Lokalise client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Lokalise account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Lokalise account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Lokalise integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent create keys and upload source strings but require approval before deleting any key
Who maintains the Lokalise integration?
fastn does. When Lokalise changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the Lokalise integration run under?
Each customer's own Lokalise grant. Where Lokalise holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Lokalise automatically?
Where Lokalise supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Lokalise integration?
A common starting point: let a customer connect their own Lokalise project so strings from your product sync into their workflow. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Lokalise integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Lokalise does not change your per-connector cost. You can start free with 3 connected accounts.
Add Lokalise to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.