Lokalise for AI agents
Agents read Lokalise at once. Changes and sends are held for a person's approval by default.
About Lokalise
Lokalise is a translation and localization management platform for managing multilingual content, projects, contributors, files, keys, translations, and localization workflows.
What an agent can do in Lokalise
Every Lokalise action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Lokalise without asking first. 6 actions.
- List Audit LogsList one page of team audit events in OCSF 1.3.0 format. This endpoint requires a personal API token belonging to a team admin and a Lokalise plan that includes Audit Logs; availability was verified o
- List BranchesList one page of branches for a Lokalise project. This capability requires a Software project with Branching enabled; it is unavailable for other project types or projects with Branching disabled.
- List KeysSearch and return one cursor page of keys from a Lokalise project or branch. Translation, comment, and screenshot expansion is opt-in to keep responses small. Branch access requires a branch-enabled S
- List Project LanguagesList one page of languages configured for a Lokalise project or, when branch_name is supplied, for a branch. Branch access requires a compatible Software project with Branching enabled.
- List ProjectsList projects available to the connected Lokalise API token, optionally filtered by team or exact project names. Include settings to discover whether a Software project has Branching enabled.
- List TranslationsSearch and return one cursor page of translations from a Lokalise project or branch by language, review state, task, or QA issue. Branch access requires a branch-enabled Software project.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 4 actions.
- Create KeysCreate 1 to 500 keys in a Lokalise project or branch. Requires a personal read/write API token and the project's Manage keys admin right. Branch targets also require a compatible Software project with
- Delete KeysPermanently delete one or more keys from a Lokalise project or branch. This operation is irreversible and requires a personal read/write API token with key-management permission. Branch targets additi
- Update KeysBatch update keys and their translations, including key metadata, translation content, review flags, and custom statuses, in one Lokalise project or branch. Requires a personal read/write API token an
- Update TranslationUpdate one translation's content and review or status flags in a Lokalise project or branch. Requires a personal read/write API token; a read-only token cannot perform this action. Branch targets addi
Changes wait in Needs you
Changes and sends in Lokalise are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
Lokalise questions
Can an agent change data in Lokalise on its own?
Not by default. Changes and sends in Lokalise are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Lokalise?
This connector lists 6 read actions. Reads run at once, without waiting for approval.
How does Lokalise connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.