Lokalise connector for AI agents

Tools your localization agent reaches for on Lokalise, scoped per user.

CALL ANY TOOL

109 tools for localization in Lokalise: keys, translations, languages, tasks, glossaries, files, screenshots, snapshots, contributors, and webhooks.

lokalise_add_members_to_group

Add members to group

Add one or more team members to a user group in a Lokalise team, granting them the group's permissions and project access. Returns the group's updated details, including its full current list of member user IDs. Use this after creating a group to populate it with contributors. Use lokalise_remove_members_from_group to take members out of the group instead. Requires Admin rights in the team.

Parameters

Name

Type

Required

Description

group_id

integer

Required

The numeric ID of the group to add members to.

team_id

integer

Required

The numeric ID of the Lokalise team the group belongs to.

users

array

Required

List of numeric user IDs to add to the group. Find a team member's user ID on the team members page in Lokalise.

lokalise_async_download_files

Async download files

Start an asynchronous export of a Lokalise project's translation files as a downloadable bundle, without waiting for it to finish. Returns a process_id you can poll with a process-status tool; once complete, that process exposes the bundle's download URL. Use this instead of the synchronous download tool for large projects, and pair it with a webhook_url or triggers to automate delivery.

Parameters

Name

Type

Required

Description

format

string

Required

File format to export, given as a file extension of a supported format (e.g. json, xml, strings), or ios_sdk / android_sdk for an OTA SDK bundle.

project_id

string

Required

The unique identifier of the Lokalise project to export files from. Example: 3002780358964f9bab5a92.87762498.

add_newline_eof

boolean

Optional

Whether to add a trailing newline at the end of each exported file, if supported by the format. Default: `false`.

all_platforms

boolean

Optional

Whether to include keys from all platforms. If disabled, only keys associated with the platform implied by the export format are included. Default: `false`.

bundle_structure

string

Optional

Bundle path/filename structure to use when original_filenames is false. Supports the placeholders %LANG_ISO%, %LANG_NAME%, %FORMAT%, and %PROJECT_NAME%.

custom_translation_status_ids

array

Optional

Only export translations attributed to these custom translation status IDs. Leave empty to include translations with any status.

directory_prefix

string

Optional

Directory prefix added inside the bundle when original_filenames is true. Supports the %LANG_ISO% placeholder.

disable_references

boolean

Optional

Whether to skip automatically resolving key-reference placeholders (e.g. [%key:hello_world%]) into their corresponding translations. Default: `false`.

exclude_tags

array

Optional

Exclude keys carrying at least one of these tags from the export.

export_empty_as

string

Optional

How to render translations that have no value. One of: `base`, `empty`, `null`, `skip`.

export_sort

string

Optional

Sort order applied to exported keys. One of: `first_added`, `last_added`, `last_updated`, `a_z`, `z_a`.

filter_data

array

Optional

Narrow the export to keys/translations matching these data filters.

filter_filenames

array

Optional

Only export keys attributed to these filenames. Leave empty to include keys from all files.

filter_langs

array

Optional

Languages to include in the export. Omit to export all project languages.

filter_repositories

array

Optional

Restrict triggered integration exports to these repositories, in organization/repository format. Leave empty to process all configured repositories for the triggered platforms.

filter_task_id

number

Optional

Only export keys attributed to this task. Available only for the offline_xliff format.

include_comments

boolean

Optional

Whether to include key comments in the exported file, if supported by the format. Default: `false`.

include_description

boolean

Optional

Whether to include key descriptions in the exported file, if supported by the format. Default: `false`.

include_pids

array

Optional

Additional project IDs whose keys should be included alongside this project's export.

include_tags

array

Optional

Only export keys carrying at least one of these tags.

indentation

string

Optional

Override the default indentation used in supported file formats. One of: `1sp`, `2sp`, `3sp`, `4sp`, `5sp`, `6sp`, `7sp`, `8sp`, `default`, `tab`.

original_filenames

boolean

Optional

Whether to export using each key's original filename/format. If false, all keys for a language are exported into a single file per language. Default: `false`.

placeholder_format

string

Optional

Override the default placeholder syntax used for the export format. One of: `icu`, `ios`, `net`, `printf`, `symfony`, `i18n`, `raw`.

plural_format

string

Optional

Override the default plural syntax used for the export format. One of: `array`, `generic`, `i18next`, `i18next_v4`, `icu`, `json_string`, `symfony`.

replace_breaks

boolean

Optional

Whether to replace real line breaks in exported translations with the literal sequence \n. Default: `false`.

triggers

array

Optional

Integration exports to trigger as part of this export (must already be configured in project settings).

webhook_url

string

Optional

URL to receive an HTTP POST with the generated bundle URL once the export finishes.

lokalise_bulk_update_keys

Bulk update keys

lokalise_create_billing_details

Create billing details

lokalise_create_key_comment

Create key comment

lokalise_create_payment_card

Create payment card

lokalise_create_snapshot

Create snapshot

lokalise_delete_all_contributors

Delete all contributors

lokalise_delete_custom_status

Delete custom status

lokalise_delete_key

Delete key

lokalise_delete_project

Delete project

lokalise_delete_task

Delete task

lokalise_get_billing_details

Get billing details

lokalise_get_current_contributor

Get current contributor

lokalise_get_key_segment

Get key segment

lokalise_get_process

Get process

lokalise_get_task_usage_metrics

Get task usage metrics

lokalise_get_translation

Get translation

lokalise_import_contributors

Import contributors

lokalise_list_comments

List comments

lokalise_list_files

List files

lokalise_list_keys

List keys

List the translation keys in a Lokalise project, with optional filters for tags, filenames, platforms, key names, and translation status. Returns each key's ID, name, platforms, tags, and (when requested) comments, screenshots, and translations. Use this to browse or filter a project's keys. Use lokalise_get_key instead when you already know a specific key's ID.

Parameters

Name

Type

Required

Description

project_id

string

Required

Unique identifier of the Lokalise project whose keys should be listed. Example: '3002780358964f9bab5a92.87762498'.

cursor

string

Optional

Cursor value to resume cursor-based pagination. Lokalise returns the nextCursor value in an HTTP response header, not in the response body, as of this writing, Scalekit's tool-execution runtime does not surface response headers back to the caller, so cursor-based pagination cannot currently be completed end-to-end through this tool. Prefer offset pagination (limit/page) instead; only set this if you have obtained a cursor value some other way.

disable_references

integer

Optional

Whether to disable key references in the response. Use 1 to disable, or 0 to keep them enabled. One of: `0`, `1`.

filter_archived

string

Optional

Whether to include, exclude, or return only archived keys. One of: `include`, `exclude`, `only`.

filter_filenames

string

Optional

One or more filenames to filter keys by, separated by commas.

filter_key_ids

string

Optional

One or more numeric key IDs to filter by, separated by commas.

filter_keys

string

Optional

One or more key names to filter by, separated by commas. When per-platform key names are enabled for the project, the filter matches against any platform's name.

filter_platforms

string

Optional

One or more platforms to filter keys by, separated by commas. Valid values are 'ios', 'android', 'web', and 'other'.

filter_qa_issues

string

Optional

One or more QA issue types to filter by, separated by commas. Valid values include 'spelling_and_grammar', 'placeholders', 'html', 'url_count', 'url', 'email_count', 'email', 'brackets', 'numbers', 'leading_whitespace', 'trailing_whitespace', 'double_space', 'special_placeholder', and 'unbalanced_brackets'.

filter_tags

string

Optional

One or more tags to filter keys by, separated by commas. Only keys carrying at least one of these tags are returned.

filter_translation_lang_ids

string

Optional

One or more numeric language IDs to filter translations by, separated by commas. Only translations for these language IDs are included in the response.

filter_untranslated

integer

Optional

Whether to return only keys that have no translation yet. Use 1 to filter to untranslated keys, or 0 to include all keys. One of: `0`, `1`.

include_comments

integer

Optional

Whether to include each key's comments in the response. Use 1 to include, or 0 to omit. One of: `0`, `1`.

include_screenshots

integer

Optional

Whether to include URLs to each key's attached screenshots. Use 1 to include, or 0 to omit. One of: `0`, `1`.

include_translations

integer

Optional

Whether to include each key's translations in the response. Use 1 to include, or 0 to omit. One of: `0`, `1`.

limit

integer

Optional

Maximum number of keys to return in a single page of results (maximum 500).

page

integer

Optional

Page number of results to return (1-based). Only applies when Pagination Type is 'offset'.

pagination

string

Optional

Pagination strategy to use. 'offset' (the default) supports page numbers. 'cursor' is optimized for large datasets but only supports paging forward via a returned cursor value. One of: `offset`, `cursor`. Default: `offset`.

lokalise_list_project_languages

List project languages

lokalise_list_system_languages

List system languages

lokalise_list_teams

List teams

lokalise_remove_members_from_group

Remove members from group

lokalise_update_custom_status

Update custom status

lokalise_update_language

Update language

lokalise_update_team_group

Update team group

Update an existing user group in a Lokalise team, replacing its name, permission-template role or admin rights, and which languages it can view or contribute to. Returns the updated group's ID, name, permissions, and team ID. Use this to change a group's settings after creation. Use lokalise_add_projects_to_group or lokalise_add_members_to_group to manage its project and member assignments instead. Requires Admin rights in the team, and always resends name, Is Reviewer, and Is Admin since this is a full replace of the group's settings, not a partial patch.

Parameters

Name

Type

Required

Description

group_id

integer

Required

The numeric ID of the group to update.

is_admin

boolean

Required

Whether members of this group have Admin access to assigned projects. Lokalise's own documentation states this should override the languages fields below, but in practice the API still rejects the request without them (verified live), always supply non-empty Reference and Contributable Languages regardless of this value. Also note (verified live): when role_id is set (or certain admin_rights combinations are used), the response's permissions.is_admin/is_reviewer can come back true even though this field was sent as false, the API appears to derive the effective admin/reviewer status from the resulting permission set rather than echoing back exactly what was submitted. Treat this field as a write-only input, not a value you can read back unchanged from the response.

is_reviewer

boolean

Required

Whether members of this group have reviewer access to assigned projects (legacy permission flag, superseded by role_id/admin_rights on newer Lokalise plans but still required by this endpoint).

languages_contributable

array

Required

Language IDs the group can translate into. Always required by the live API, must be a non-empty array even when Is Admin is true (Lokalise's documentation says Is Admin overrides this, but the API rejects an empty or omitted value regardless; verified live).

languages_reference

array

Required

Language IDs the group can view but not translate into (read-only reference languages). Always required by the live API, must be a non-empty array even when Is Admin is true (Lokalise's documentation says Is Admin overrides this, but the API rejects an empty or omitted value regardless; verified live).

name

string

Required

New name for the group, shown in the Lokalise team members list.

team_id

integer

Required

The numeric ID of the Lokalise team the group belongs to.

admin_rights

array

Optional

Explicit list of permission strings to grant this group when no role_id template is used. Documented values include activity, contributors, branches_create, branches_main_modify, branches_merge, custom_status_modify, download, glossary, glossary_edit, glossary_delete, keys, manage_languages, review, screenshots, settings, statistics, tasks, and upload. Note (verified live): 'glossary' is accepted by this endpoint's schema but silently dropped from the response, the group's stored admin_rights end up empty when only 'glossary' is requested, so treat glossary-related permissions as unsupported for groups even though they are documented as valid values here.

role_id

integer

Optional

Numeric ID of a permission template to copy this group's permissions from. When set, it takes precedence over the Admin Rights field. Valid values: 1=Manager (manage project settings, contributors and tasks), 2=Developer (create keys, upload and download content), 3=Content creator (create, translate and edit keys, manage screenshots), 4=Reviewer (translate keys, control key statuses), 5=Translator (translate keys). One of: `1`, `2`, `3`, `4`, `5`.

lokalise_upload_file

Upload file

Upload a file to a Lokalise project for import, sending its content as a base64-encoded string alongside its filename and language code. Returns a queued process object with a process ID and status, or the completed process details if the import finishes immediately. Use this to bulk-import or update translations from a file instead of creating or editing keys one at a time.

Parameters

Name

Type

Required

Description

data

string

Required

Base64-encoded content of the file to import. Must be one of Lokalise's supported file types (e.g. JSON, XLIFF, .strings, .properties). Encode the raw file bytes as base64 before calling this tool.

filename

string

Required

Filename to assign to the uploaded file. May optionally include a relative path (e.g. admin/main.json); the path becomes part of the file's unique identity.

lang_iso

string

Required

Language code (ISO) of the translations contained in the uploaded file, matching a language already added to the project.

project_id

string

Required

The unique identifier of the Lokalise project to upload the file into. Example: 3002780358964f9bab5a92.87762498.

apply_tm

boolean

Optional

Whether to automatically apply 100% translation-memory matches to untranslated content. Takes priority over use_automations when both are enabled. Default: `false`.

cleanup_mode

boolean

Optional

Whether to delete every key (and its translations in all languages) that is not present in the uploaded file. Consider taking a project snapshot before enabling this. Default: `false`.

convert_placeholders

boolean

Optional

Whether to automatically convert placeholders in the file to Lokalise's universal placeholder syntax. Defaults to true; set to false to preserve the original placeholder syntax as-is. Default: `true`.

custom_translation_status_ids

array

Optional

Custom translation status IDs to attach to translations created or updated by this import.

custom_translation_status_inserted_keys

boolean

Optional

Whether to apply the given custom translation statuses to newly inserted keys. Default: `false`.

custom_translation_status_skipped_keys

boolean

Optional

Whether to apply the given custom translation statuses to skipped keys. Default: `false`.

custom_translation_status_updated_keys

boolean

Optional

Whether to apply the given custom translation statuses to updated keys. Default: `false`.

detect_icu_plurals

boolean

Optional

Whether to automatically detect and parse ICU-formatted plurals found in the translations being imported. Default: `false`.

distinguish_by_file

boolean

Optional

Whether to allow keys with the same name to coexist as separate keys when they are assigned to different filenames. Default: `false`.

filter_task_id

number

Optional

Apply the import results as part of an existing task. Only available for the offline_xliff file format.

format

string

Optional

File format override, expressed as a supported file extension (e.g. json, strings, xml). Normally inferred from the filename.

hidden_from_contributors

boolean

Optional

Whether to mark newly created keys as hidden from contributors. Default: `false`.

keys_to_values

boolean

Optional

Whether to automatically replace each key's translation value with the key name itself. Default: `false`.

replace_metadata

boolean

Optional

Structured JSON only. Whether to replace key metadata (tags, notes, character limit) with the values from the uploaded file. Manually-added tags are preserved; only tags previously set by a file upload are replaced. Default: `false`.

replace_modified

boolean

Optional

Whether to overwrite translations that have been modified since they were last exported, using the values from the uploaded file. Default: `false`.

skip_detect_lang_iso

boolean

Optional

Whether to skip automatic language detection based on the filename. Default: `false`.

slashn_to_linebreak

boolean

Optional

Whether to replace literal \n sequences in the imported content with real line breaks. Default: `false`.

tag_inserted_keys

boolean

Optional

Whether to add the given tags to newly inserted keys. Default: `false`.

tag_parsed_keys

boolean

Optional

Whether to add tags parsed from the uploaded file itself (e.g. structured-JSON per-key tags) to the corresponding keys. Default: `false`.

tag_skipped_keys

boolean

Optional

Whether to add the given tags to keys that were skipped during import. Default: `false`.

tag_updated_keys

boolean

Optional

Whether to add the given tags to keys that already existed and were updated. Default: `false`.

tags

array

Optional

Tags to apply to keys created or updated by this import.

title

string

Optional

Human-readable title for the uploaded file shown in the UI instead of the filename. Maximum 256 characters. Relevant for Marketing and Support (M&S) project types only.

use_automations

boolean

Optional

Whether to run the project's configured automations for this upload. Default: `false`.

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Lokalise tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["lokalise"], toolNames: [
    "lokalise_list_keys",
    "lokalise_list_translations",
    "lokalise_create_task"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "List unreviewed French translations in the Web App project" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["lokalise"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "List unreviewed French translations in the Web App project" }],
  tools,
});

// Execute the tool call with the user's vaulted Lokalise API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["lokalise"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "List unreviewed French translations in the Web App project" }],
  tools,
});

// Tool call runs with the user's vaulted Lokalise API key
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["lokalise"] }, pageSize: 100,
});

const agent = new Agent({
  name: "localization_agent",
  model: "gemini-2.5-pro",
  instruction: "Lokalise tools scoped to this user",
  tools,
});

await agent.run("List unreviewed French translations in the Web App project");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Lokalise tool. Click to copy, paste into your agent, done.

Keys and translations

Copy the prompt

Copied

List keys tagged release-2.4 in the Web App project.

Copy the prompt

Copied

Show unreviewed French translations that have placeholder QA issues.

Copy the prompt

Copied

Update the German translation for the checkout_button key and mark it reviewed.

Tasks and contributors

Copy the prompt

Copied

Create a review task for the new Spanish keys in the Mobile project.

Copy the prompt

Copied

List open tasks in the Mobile project.

Copy the prompt

Copied

Add a contributor with translator access to Japanese only.

Files and releases

Copy the prompt

Copied

Export the Web App project's translation files for all languages.

Copy the prompt

Copied

Upload en.json to the Web App project for import.

Copy the prompt

Copied

Create a snapshot of the Mobile project before the release.

SEE HOW AUTH WORKS

Each user connects their own Lokalise API key once; Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Lokalise

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Lokalise

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Lokalise

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Lokalise

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other localization and developer connectors.

Engineering Teams

Auto release notes agent

Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.

Engineering Teams

DevOps assistant agent

Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Lokalise API key looks fine in a demo. In production every key edit looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Lokalise today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Lokalise as the user or through a shared key?

As the user. Each user connects their own Lokalise API key once, and Scalekit sends it with every call. Audit logs attribute every key edit and file export to that user, not a shared service account.

Where is the Lokalise API key stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Lokalise?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the list and get tools without the 18 destructive tools such as lokalise_delete_project. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Lokalise access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent delete Lokalise projects or keys?

Only if you expose those tools. lokalise_delete_project, lokalise_empty_project, and lokalise_delete_keys remove keys and translations permanently, so leave them out of listScopedTools for agents that should only read and edit. Lokalise admin rights still apply: snapshots and screenshots need the matching admin right on the user's account.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit