Lokalise

scalekit109 toolsAPI KeyDeveloper ToolsFiles & Documents

Connect to Lokalise to manage software and content localization: projects, translation keys, translations, languages, comments, contributors, glossary...

Lokalise connector

Install the SDK
Section titled “Install the SDK”
- Node.js
- Python
Terminal window
1 npm install @scalekit-sdk/node
Terminal window
1 pip install scalekit
Full SDK reference: Node.js | Python
Set your credentials
Section titled “Set your credentials”

Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.
.env
```
SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
SCALEKIT_CLIENT_ID=<your-client-id>
SCALEKIT_CLIENT_SECRET=<your-client-secret>
```

1
import { ScalekitClient } from '@scalekit-sdk/node'
2
import 'dotenv/config'
3

4
const scalekit = new ScalekitClient(
5
  process.env.SCALEKIT_ENV_URL,
6
  process.env.SCALEKIT_CLIENT_ID,
7
  process.env.SCALEKIT_CLIENT_SECRET,
8
)
9
const actions = scalekit.actions
10

11
const connector = 'lokalise'
12
const identifier = 'user_123'
13

14
// Make your first call
15
const result = await actions.executeTool({
16
  connector,
17
  identifier,
18
  toolName: 'lokalise_list_payment_cards',
19
  toolInput: {},
20
})
21
console.log(result)

1
import os
2
from scalekit.client import ScalekitClient
3
from dotenv import load_dotenv
4
load_dotenv()
5

6
scalekit_client = ScalekitClient(
7
    env_url=os.getenv("SCALEKIT_ENV_URL"),
8
    client_id=os.getenv("SCALEKIT_CLIENT_ID"),
9
    client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
10
)
11
actions = scalekit_client.actions
12

13
connection_name = "lokalise"
14
identifier = "user_123"
15

16
# Make your first call
17
result = actions.execute_tool(
18
    tool_input={},
19
    tool_name="lokalise_list_payment_cards",
20
    connection_name=connection_name,
21
    identifier=identifier,
22
)
23
print(result)

What you can do

Connect this agent connector to let your agent:

File upload — Upload a file to a Lokalise project for import, sending its content as a base64-encoded string alongside its filename and language code
Update webhook, translation, team user — Update an existing webhook’s URL, branch scope, subscribed events, or language mappings on a Lokalise project
Snapshot restore — Restore a Lokalise snapshot into a new project, seeded with the snapshot’s saved keys, translations, and settings, inside the same team as the original project
Group remove projects from, remove members from, add projects to — Remove one or more projects from a user group in a Lokalise team, revoking the group’s members’ access to those projects
Secret regenerate webhook — Regenerate the signing secret for an existing webhook on a Lokalise project
List webhooks, translations, translation providers — List all webhooks configured on a Lokalise project

Tool list

Use the exact tool names from the Tool list below when you call execute_tool. If you’re not sure which name to use, list the tools available for the current user first.

lokalise_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.3 params

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.

NameTypeRequiredDescription

group_idintegerrequiredThe numeric ID of the group to add members to.

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

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

lokalise_add_projects_to_group#Add one or more projects to a user group in a Lokalise team, granting the group's members access to those projects. Returns the group's updated details, including its full current list of assigned projects. Use this after creating a group to grant it access to specific projects. Use lokalise_remove_projects_from_group to revoke access instead. Requires Admin rights in the team.3 params

Add one or more projects to a user group in a Lokalise team, granting the group's members access to those projects. Returns the group's updated details, including its full current list of assigned projects. Use this after creating a group to grant it access to specific projects. Use lokalise_remove_projects_from_group to revoke access instead. Requires Admin rights in the team.

NameTypeRequiredDescription

group_idintegerrequiredThe numeric ID of the group to add projects to.

projectsarrayrequiredList of project IDs to add to the group. Use the project ID string shown in each project's settings (e.g. 598901215bexxx43dcba74.xxx), not the project name.

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

lokalise_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.27 params

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.

NameTypeRequiredDescription

formatstringrequiredFile 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_idstringrequiredThe unique identifier of the Lokalise project to export files from. Example: 3002780358964f9bab5a92.87762498.

add_newline_eofbooleanoptionalWhether to add a trailing newline at the end of each exported file, if supported by the format.

all_platformsbooleanoptionalWhether to include keys from all platforms. If disabled, only keys associated with the platform implied by the export format are included.

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

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

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

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

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

export_empty_asstringoptionalHow to render translations that have no value.

export_sortstringoptionalSort order applied to exported keys.

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

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

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

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

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

include_commentsbooleanoptionalWhether to include key comments in the exported file, if supported by the format.

include_descriptionbooleanoptionalWhether to include key descriptions in the exported file, if supported by the format.

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

include_tagsarrayoptionalOnly export keys carrying at least one of these tags.

indentationstringoptionalOverride the default indentation used in supported file formats.

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

placeholder_formatstringoptionalOverride the default placeholder syntax used for the export format.

plural_formatstringoptionalOverride the default plural syntax used for the export format.

replace_breaksbooleanoptionalWhether to replace real line breaks in exported translations with the literal sequence \n.

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

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

lokalise_bulk_update_keys#Update one or more existing translation keys in a Lokalise project in a single request, including their names, tags, and translations. Returns the updated keys with their current field values plus a separate errors array for any per-key failures — the call reports success even if every key failed, so check the errors array rather than assuming all requested keys were updated. Use this to change details on keys that already exist. Use lokalise_create_keys instead to add brand-new keys.3 params

Update one or more existing translation keys in a Lokalise project in a single request, including their names, tags, and translations. Returns the updated keys with their current field values plus a separate errors array for any per-key failures — the call reports success even if every key failed, so check the errors array rather than assuming all requested keys were updated. Use this to change details on keys that already exist. Use lokalise_create_keys instead to add brand-new keys.

NameTypeRequiredDescription

keysarrayrequiredArray of key objects to update. Each entry must include the key_id of an existing key, plus whichever fields to change: key_name, description, platforms, tags (with merge_tags to combine with existing tags instead of replacing them), filenames per platform, comments, screenshots (base64-encoded), and translations (each with a language_iso and its translation text or plural-form map, plus flags such as is_reviewed and custom_translation_status_ids). A key can also be updated to be is_plural, is_hidden, or is_archived, given a char_limit, or given custom_attributes as a JSON-encoded string. Example: [{"key_id": 331223, "key_name": "index.welcome", "tags": ["main"]}].

project_idstringrequiredUnique identifier of the Lokalise project the keys belong to. Example: '3002780358964f9bab5a92.87762498'.

use_automationsbooleanoptionalWhether to run the project's translation automations against the updated keys' translations.

lokalise_create_billing_details#Create billing details for a Lokalise team, providing the billing email, country, and postal code used for invoices and translation orders. Returns the saved billing details, including billing email, address fields, phone, VAT number, and country code. Use this to set up billing information for a team that doesn't have it yet. Use lokalise_get_billing_details to check whether billing details already exist first. If Country Code is set to US, State Code is also required.11 params

Create billing details for a Lokalise team, providing the billing email, country, and postal code used for invoices and translation orders. Returns the saved billing details, including billing email, address fields, phone, VAT number, and country code. Use this to set up billing information for a team that doesn't have it yet. Use lokalise_get_billing_details to check whether billing details already exist first. If Country Code is set to US, State Code is also required.

NameTypeRequiredDescription

billing_emailstringrequiredEmail address invoices and translation-order notifications are sent to.

country_codestringrequiredTwo-letter ISO 3166-1 alpha-2 country code for the billing address (e.g. US, LV, DE).

team_idintegerrequiredThe numeric ID of the Lokalise team to create billing details for.

zipstringrequiredPostal or ZIP code for the billing address, valid for the specified country.

address1stringoptionalFirst line of the billing street address.

address2stringoptionalSecond line of the billing street address, e.g. suite or unit number.

citystringoptionalCity for the billing address.

companystringoptionalCompany name to appear on invoices.

phonestringoptionalContact phone number associated with the billing details.

state_codestringoptionalUS state code for the billing address. Required only when Country Code is US.

vatnumberstringoptionalVAT registration number to appear on invoices, where applicable.

lokalise_create_contributors#Create one or more new contributors on a Lokalise project, granting them project access and per-language permissions. Returns the created contributor object(s) with user ID, admin/reviewer status, and assigned languages. Note (verified live): the returned admin_rights for a given role_id can include extra entries beyond Lokalise's publicly documented role template (e.g. branches_main_modify appearing even when not requested) — treat the response as authoritative rather than assuming it exactly matches the documented template. Use this to invite team members or grant translators/reviewers access. Use Import Contributors instead to copy existing contributors from another project.2 params

Create one or more new contributors on a Lokalise project, granting them project access and per-language permissions. Returns the created contributor object(s) with user ID, admin/reviewer status, and assigned languages. Note (verified live): the returned admin_rights for a given role_id can include extra entries beyond Lokalise's publicly documented role template (e.g. branches_main_modify appearing even when not requested) — treat the response as authoritative rather than assuming it exactly matches the documented template. Use this to invite team members or grant translators/reviewers access. Use Import Contributors instead to copy existing contributors from another project.

NameTypeRequiredDescription

contributorsarrayrequiredArray of contributor objects to add to the project. Each object needs an email address, and either sets is_admin to true (which grants access to every project language, overriding any languages provided) or lists the specific languages the contributor can access, each with a language code and whether they can edit it. You can optionally set a full name (used only when inviting a brand-new Lokalise user whose account does not exist yet), a role_id to apply one of Lokalise's built-in permission templates (Manager, Developer, Content creator, Reviewer, or Translator), or a custom list of admin rights (such as glossary, screenshots, or task access) instead of a role template. Example: [{"email": "translator@example.com", "fullname": "Jane Translator", "is_admin": false, "is_reviewer": true, "languages": [{"lang_iso": "en", "is_writable": false}, {"lang_iso": "ru", "is_writable": true}]}]

project_idstringrequiredThe unique identifier of the Lokalise project to add contributors to.

lokalise_create_custom_status#Create a new custom translation status in a Lokalise project. Returns the created status's ID, title, and hex color. Use this to add a new workflow stage (e.g. "Reviewed by staff") that translators and reviewers can apply to keys, beyond Lokalise's built-in statuses.3 params

Create a new custom translation status in a Lokalise project. Returns the created status's ID, title, and hex color. Use this to add a new workflow stage (e.g. "Reviewed by staff") that translators and reviewers can apply to keys, beyond Lokalise's built-in statuses.

NameTypeRequiredDescription

colorstringrequiredHex color code used to display this status in the Lokalise editor, e.g. #ff9f1a.

project_idstringrequiredThe unique identifier of the Lokalise project to create the custom translation status in.

titlestringrequiredTitle of the new custom translation status, shown to translators and reviewers.

lokalise_create_glossary_terms#Create one or more new glossary terms in a Lokalise project in a single call. Returns the created term objects (with their new IDs) along with a count of how many were created, plus any per-term errors. Use lokalise_update_glossary_terms afterward to modify a term, or lokalise_list_glossary_terms to review existing terms first and avoid duplicates.2 params

Create one or more new glossary terms in a Lokalise project in a single call. Returns the created term objects (with their new IDs) along with a count of how many were created, plus any per-term errors. Use lokalise_update_glossary_terms afterward to modify a term, or lokalise_list_glossary_terms to review existing terms first and avoid duplicates.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise project to create glossary terms in. Example: 3002780358964f9bab5a92.87762498.

termsarrayrequiredArray of glossary term objects to create. Each object requires term (the term text), description, caseSensitive, translatable, and forbidden (booleans), and may optionally include a translations array of {langId, translation, description} entries for per-language overrides, and a tags array of strings. Example: [{"term": "checkout", "description": "The action of completing a purchase.", "caseSensitive": true, "translatable": false, "forbidden": false, "tags": ["ecommerce"]}]

lokalise_create_key_comment#Add one or more comments to a translation key in a Lokalise project. Returns the created comment objects, each with its ID, text, author, and timestamps. Use this to leave notes or feedback for translators on a specific key.3 params

Add one or more comments to a translation key in a Lokalise project. Returns the created comment objects, each with its ID, text, author, and timestamps. Use this to leave notes or feedback for translators on a specific key.

NameTypeRequiredDescription

commentsarrayrequiredOne or more comments to add to the key. Each entry is an object with a single text field. Example: [{"comment": "Please double-check this translation."}, {"comment": "Looks good to me."}]

key_idintegerrequiredThe unique numeric identifier of the translation key to add comments to.

project_idstringrequiredThe unique identifier of the Lokalise project the key belongs to.

lokalise_create_keys#Create one or more translation keys, with their translations, in a Lokalise project in a single request. Returns the created keys with their assigned IDs and a separate errors array for any per-key failures (for example, a key name that already exists) — the call reports success even if every key failed, so check the errors array rather than assuming all requested keys were created. Use this to add new keys and seed their initial translations. Use lokalise_bulk_update_keys instead to modify keys that already exist. We recommend sending up to 500 keys per request.3 params

Create one or more translation keys, with their translations, in a Lokalise project in a single request. Returns the created keys with their assigned IDs and a separate errors array for any per-key failures (for example, a key name that already exists) — the call reports success even if every key failed, so check the errors array rather than assuming all requested keys were created. Use this to add new keys and seed their initial translations. Use lokalise_bulk_update_keys instead to modify keys that already exist. We recommend sending up to 500 keys per request.

NameTypeRequiredDescription

keysarrayrequiredArray of key objects to create. Each key needs a key_name and a platforms list (any of ios, android, web, other). Optional per-key fields let you set a description, per-platform filenames, tags, comments, screenshots (as base64-encoded image data), and translations (each with a language_iso and its translation text, plus flags such as is_reviewed). A key can also be marked is_plural, is_hidden, or is_archived, given a char_limit, or given custom_attributes as a JSON-encoded string. Example: [{"key_name": "index.welcome", "description": "Index app welcome", "platforms": ["web"], "translations": [{"language_iso": "en", "translation": "Welcome"}]}].

project_idstringrequiredUnique identifier of the Lokalise project to add keys to. Example: '3002780358964f9bab5a92.87762498'.

use_automationsbooleanoptionalWhether to run the project's translation automations against the new keys' translations.

lokalise_create_languages#Add one or more languages to a Lokalise project by their system language ISO codes, optionally overriding the language code, name, or plural forms. Returns the project ID, the newly created language objects (including each new language's assigned ID), and a separate errors array for any languages that failed to add (for example, an unrecognized ISO code) — a successful call can still contain per-language failures, so check the errors array rather than assuming every requested language was added. Use this to enable additional languages for translation. Use lokalise_list_system_languages to find valid ISO codes first.2 params

Add one or more languages to a Lokalise project by their system language ISO codes, optionally overriding the language code, name, or plural forms. Returns the project ID, the newly created language objects (including each new language's assigned ID), and a separate errors array for any languages that failed to add (for example, an unrecognized ISO code) — a successful call can still contain per-language failures, so check the errors array rather than assuming every requested language was added. Use this to enable additional languages for translation. Use lokalise_list_system_languages to find valid ISO codes first.

NameTypeRequiredDescription

languagesarrayrequiredArray of language objects to add. Each object must include lang_iso, the ISO code of one of Lokalise's system languages (see lokalise_list_system_languages). You may optionally add custom_iso to override the stored language/locale code, custom_name to override the display name, and custom_plural_forms (an array of plural form names) to override the supported plural forms.

project_idstringrequiredThe unique identifier of the Lokalise project to add languages to. Find it with lokalise_list_projects.

lokalise_create_order#Place a translation order for a set of keys in a Lokalise project, sending them to a translation provider such as Gengo, Babble-on, or a professional translator tier. Returns the created order's ID, status, pricing, and language details, or a price estimate when Dry Run is enabled instead of placing a live order. Use this to kick off paid translation from a source language into one or more target languages for specific keys. Requires admin privileges in the target project, and (for credit-card payment) a card ID from the list payment cards tool.14 params

Place a translation order for a set of keys in a Lokalise project, sending them to a translation provider such as Gengo, Babble-on, or a professional translator tier. Returns the created order's ID, status, pricing, and language details, or a price estimate when Dry Run is enabled instead of placing a live order. Use this to kick off paid translation from a source language into one or more target languages for specific keys. Requires admin privileges in the target project, and (for credit-card payment) a card ID from the list payment cards tool.

NameTypeRequiredDescription

briefingstringrequiredInstructions for the translator describing tone, context, or anything else they should know about the content being translated.

keysarrayrequiredList of key identifiers from the project to include in this translation order.

project_idstringrequiredThe unique identifier of the Lokalise project containing the keys to translate.

provider_slugstringrequiredSlug of the translation provider to use for this order, e.g. 'gengo' for Gengo or 'babble-on' for professional human translation.

source_language_isostringrequiredISO language code of the source content being translated.

target_language_isosarrayrequiredList of ISO language codes to translate the content into. Provide one or more target languages.

team_idintegerrequiredThe unique numeric identifier of the Lokalise team placing the order.

translation_tierintegerrequiredNumeric tier of translation quality/speed to order. Available tiers depend on the chosen provider (for example, Gengo offers tiers such as 1=Standard, 2=Pro, 3=Ultra).

branchstringoptionalName of the project branch to place the order against, for projects with branching enabled. Omit to use the project's default branch.

card_idintegeroptionalIdentifier of the saved payment card to charge. Required when Payment Method is 'credit_card' (the default); look up card IDs with the list payment cards tool.

dry_runbooleanoptionalIf true, returns a price estimate for this order without actually placing it or charging any payment method. Defaults to false.

is_saved_to_translation_memorybooleanoptionalWhether completed translations from this order are saved to the project's translation memory. Can only be set to false for the 'google' and 'deepl' providers; other providers always save to translation memory. Defaults to true.

payment_methodstringoptionalHow the order will be paid for: 'credit_card' to charge a saved card, or 'team_credit' to use the team's prepaid credit balance. Defaults to 'credit_card'.

translation_stylestringoptionalTone of the translation. Only applies to the 'gengo' provider, which supports 'formal', 'informal', 'business', or 'friendly'. Defaults to 'friendly'.

lokalise_create_payment_card#Add a new payment card to your Lokalise account by sending the card number, CVC, expiration month, and expiration year directly to Lokalise's /payment_cards endpoint over TLS. Returns the created card's id, last4 digits, brand, and creation timestamp; Lokalise (not Scalekit) stores the full card number and CVC after this call. Use this only when a real billing card must be added to the account — the card number and CVC are transmitted unmasked in the request body, so avoid passing real production card numbers through this tool casually (e.g., in testing or demos); use a well-known test card number instead when just trying the tool out. Requires an API token scoped with write_payment_cards.4 params

Add a new payment card to your Lokalise account by sending the card number, CVC, expiration month, and expiration year directly to Lokalise's /payment_cards endpoint over TLS. Returns the created card's id, last4 digits, brand, and creation timestamp; Lokalise (not Scalekit) stores the full card number and CVC after this call. Use this only when a real billing card must be added to the account — the card number and CVC are transmitted unmasked in the request body, so avoid passing real production card numbers through this tool casually (e.g., in testing or demos); use a well-known test card number instead when just trying the tool out. Requires an API token scoped with write_payment_cards.

NameTypeRequiredDescription

cvcstringrequired3-digit card verification code (CVC/CVV) printed on the back of the card. This value is sent as raw, unmasked text directly to Lokalise's /payment_cards endpoint over TLS; Lokalise (not Scalekit) stores it after this call. Avoid using a real card's CVC just to try this tool out — use a test value such as 123 unless you specifically intend to add a real billing card. Example: "123".

exp_monthintegerrequiredCard expiration month as a number from 1 (January) to 12 (December). Example: 5 for May.

exp_yearintegerrequiredCard expiration year as a 4-digit number (e.g. 2030). Must be a future year for the card to be valid.

numberstringrequiredFull payment card number, digits only, with no spaces or dashes. This value is sent as raw, unmasked text directly to Lokalise's /payment_cards endpoint over TLS; Lokalise (not Scalekit) stores the card afterward. Avoid using a real production card number just to try this tool out — use a well-known test number such as 4242424242424242 unless you specifically intend to add a real billing card. Example: "4242424242424242".

lokalise_create_project#Create a new Lokalise project, optionally seeding it with one or more languages and a base language. Returns the created project's ID, name, description, team, base language, and default settings. Use this to start a new localization project before adding keys and translations. Use lokalise_update_project to change an existing project's name or description instead.8 params

Create a new Lokalise project, optionally seeding it with one or more languages and a base language. Returns the created project's ID, name, description, team, base language, and default settings. Use this to start a new localization project before adding keys and translations. Use lokalise_update_project to change an existing project's name or description instead.

NameTypeRequiredDescription

namestringrequiredName of the new project. Required. Example: 'TheApp Project'.

base_lang_isostringoptionalLanguage/locale code to use as the project's base language. Must be one of the codes supplied in Languages (or its custom_iso override, if set). Example: 'en-us'.

content_integrationstringoptionalContent integration identifier to use for this project. Only used, and required, when Project Type is 'content_integration'; must be one of the integrations already available to your team.

descriptionstringoptionalOptional free-text description of the project, such as its purpose or a link to related documentation.

is_segmentation_enabledbooleanoptionalWhether to enable the Segmentation feature for this project.

languagesarrayoptionalLanguages to add to the project when it is created. Each entry needs a lang_iso (a valid language code in Lokalise's system) and may optionally set custom_iso to override the code/locale shown for that language. Example: [{"lang_iso": "en", "custom_iso": "en-us"}, {"lang_iso": "en_GB", "custom_iso": "en-gb"}].

project_typestringoptionalType of project to create, which determines available features. 'localization_files' (Web and mobile, supports branching and individual key management), 'paged_documents' (ad hoc document projects, file-based management), 'content_integration' (marketing projects with limited key parameters, file-based management), 'marketing' (automatically translated marketing projects), or 'marketing_integrations' (automatically translated marketing projects with integrations).

team_idstringoptionalID of the team to create the project in, as either a numeric team ID or a team UUID. Leave blank to create the project in the current API token owner's default team.

lokalise_create_screenshots#Upload one or more screenshots to a Lokalise project as base64-encoded JPG or PNG images. Requires the Manage screenshots admin right. Returns the created screenshot objects, including their IDs, hosted image URLs, and any translation keys they were attached to. Use this to add visual context for translators; link a screenshot to specific keys, or enable OCR to have Lokalise auto-detect matching keys from text found in the image.2 params

Upload one or more screenshots to a Lokalise project as base64-encoded JPG or PNG images. Requires the Manage screenshots admin right. Returns the created screenshot objects, including their IDs, hosted image URLs, and any translation keys they were attached to. Use this to add visual context for translators; link a screenshot to specific keys, or enable OCR to have Lokalise auto-detect matching keys from text found in the image.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise project to upload screenshots into.

screenshotsarrayrequiredOne or more screenshot objects to create. Each object requires a base64-encoded image in data (prefixed with its data URI, e.g. data:image/png;base64,...), and may optionally include a title, description, whether to run OCR key-detection, a list of key IDs to attach it to, and tags. Example: [{"data": "data:image/png;base64,iVBORw0KGgo...", "title": "Onboarding step 2", "ocr": false, "key_ids": [1132290, 1132292], "tags": ["onboarding"]}]

lokalise_create_service_jwt#Create a short-lived service JWT for a Lokalise project, for use with over-the-air (OTA) updates and mobile SDKs. Returns the signed JWT string that the SDK or OTA client uses to authenticate. Use this only for software (localization_files) projects; Documents and Marketing project types are not supported.2 params

Create a short-lived service JWT for a Lokalise project, for use with over-the-air (OTA) updates and mobile SDKs. Returns the signed JWT string that the SDK or OTA client uses to authenticate. Use this only for software (localization_files) projects; Documents and Marketing project types are not supported.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise software (localization_files) project to create the token for.

servicestringrequiredThe service the token is being created for. Currently only 'ota' (over-the-air updates / mobile SDKs) is supported.

lokalise_create_snapshot#Create a snapshot of a Lokalise project, capturing its current keys, translations, and settings at a point in time. Returns the project ID and the new snapshot's ID, title, and creation timestamp. Use this before a risky bulk edit so you can roll back with lokalise_restore_snapshot if something goes wrong.2 params

Create a snapshot of a Lokalise project, capturing its current keys, translations, and settings at a point in time. Returns the project ID and the new snapshot's ID, title, and creation timestamp. Use this before a risky bulk edit so you can roll back with lokalise_restore_snapshot if something goes wrong.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise project to snapshot. Find it on the project's settings page or from lokalise_list_projects.

titlestringoptionalOptional title for the snapshot, used to identify it later in the project's snapshot list. If omitted, Lokalise assigns a default title.

lokalise_create_task#Create a new translation, review, or AI-automated task in a Lokalise project, assigning specific keys and languages to translators, reviewers, or an AI engine. Returns the created task's ID, title, status, assigned languages with their translators, and (for AI task types) any requested languages that were skipped and why. Use this to kick off translation or review work on a set of keys; use lokalise_update_task to change an existing task's settings instead.20 params

Create a new translation, review, or AI-automated task in a Lokalise project, assigning specific keys and languages to translators, reviewers, or an AI engine. Returns the created task's ID, title, status, assigned languages with their translators, and (for AI task types) any requested languages that were skipped and why. Use this to kick off translation or review work on a set of keys; use lokalise_update_task to change an existing task's settings instead.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise project to create the task in.

titlestringrequiredTitle of the task, shown to assigned translators and reviewers.

apply_ai_tm100_matchesbooleanoptionalWhether to apply 100% Translation Memory matches instead of AI-translating those segments. Only applies when task_type is automatic_translation.

auto_close_itemsbooleanoptionalWhether translation task items should be automatically marked complete when edited. Must be true or omitted for the automatic_translation and lqa_by_ai task types.

auto_close_languagesbooleanoptionalWhether each language in the task should close automatically once its last item is completed. Must be true or omitted for the automatic_translation and lqa_by_ai task types.

auto_close_taskbooleanoptionalWhether the whole task should close automatically once every language is complete. Must be true or omitted for the automatic_translation and lqa_by_ai task types.

closing_tagsarrayoptionalTags to add to affected keys once the task closes.

custom_translation_status_idsarrayoptionalIDs of custom translation statuses to apply to task items once each item is completed.

descriptionstringoptionalBrief description of the task. For automatic_translation and lqa_by_ai task types, this text is also used as instructions for the AI.

do_lock_translationsbooleanoptionalIf true, locks translations for project members not assigned to this task.

due_datestringoptionalDue date and time for the task, in "Y-m-d H:i:s" format (project's timezone).

include_ai_scorebooleanoptionalWhether to run AI scoring (LQA) on the task's translations once automatic translation finishes. Only applies when task_type is automatic_translation and requires the AI scoring feature on your plan.

keysarrayoptionalList of translation key identifiers to include in the task. Required if parent_task_id is not set (a review task with a parent task inherits its keys instead).

languagesarrayoptionalLanguages included in the task, and who should work on each. Each entry needs a language_iso code, and can optionally list user IDs (users) and/or user-group IDs (groups) to assign to that language. For task_type translation and review, this field is effectively required with at least one entry, and that entry must list a non-empty users or groups (verified live: the API rejects translation/review tasks with 'One of users and groups parameters must contain values' if both are empty/omitted) — the schema marks this optional only because it's genuinely optional for automatic_translation/lqa_by_ai. Both users and groups must be omitted for the automatic_translation and lqa_by_ai task types. Unsupported languages for those AI task types are ignored and returned in the response's skipped_languages instead of failing the request. Example: [{"language_iso": "fi", "users": ["421"]}, {"language_iso": "ru", "groups": ["191"]}].

mark_verifiedbooleanoptionalWhether to mark AI-generated translations as verified. Only applies when task_type is automatic_translation.

parent_task_idintegeroptionalID of a parent task. Only applicable when task_type is review — this review task opens once its parent task closes.

save_ai_translation_to_tmbooleanoptionalWhether to save AI-generated translations to Translation Memory. Only applies when task_type is automatic_translation.

source_language_isostringoptionalSource language code translators will translate from. Falls back to the project's base language if not provided.

task_typestringoptionalType of task to create: translation (default) for human translators, automatic_translation to have Lokalise AI translate automatically, lqa_by_ai to have AI score existing translations, or review for a review pass over already-translated keys.

translate_all_segmentsbooleanoptionalWhether to re-translate all segments, including ones that already have a translation or TM match, instead of only empty ones. Only applies to automatic_translation tasks in projects with segmentation enabled, and can only be set at creation time.

lokalise_create_team_group#Create a new user group in a Lokalise team, setting its name and either a permission-template role or explicit admin rights, plus which languages it can view or contribute to. Returns the created group's ID, name, permissions, and team ID. Use this to set up a group before granting it project access or adding members with lokalise_add_projects_to_group and lokalise_add_members_to_group. Use lokalise_update_team_group to change an existing group's settings instead. Requires Admin rights in the team.8 params

Create a new user group in a Lokalise team, setting its name and either a permission-template role or explicit admin rights, plus which languages it can view or contribute to. Returns the created group's ID, name, permissions, and team ID. Use this to set up a group before granting it project access or adding members with lokalise_add_projects_to_group and lokalise_add_members_to_group. Use lokalise_update_team_group to change an existing group's settings instead. Requires Admin rights in the team.

NameTypeRequiredDescription

is_adminbooleanrequiredWhether 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_reviewerbooleanrequiredWhether 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_contributablearrayrequiredLanguage 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_referencearrayrequiredLanguage 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).

namestringrequiredName of the new group, shown in the Lokalise team members list.

team_idintegerrequiredThe numeric ID of the Lokalise team to create the group in.

admin_rightsarrayoptionalExplicit 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_idintegeroptionalNumeric 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).

lokalise_create_webhook#Create a new webhook on a Lokalise project to receive notifications for specific events. Returns the created webhook's ID, URL, secret, subscribed events, and any per-event language mappings. Use this to set up a new webhook endpoint; use lokalise_update_webhook to change an existing webhook's settings instead of creating a duplicate.5 params

Create a new webhook on a Lokalise project to receive notifications for specific events. Returns the created webhook's ID, URL, secret, subscribed events, and any per-event language mappings. Use this to set up a new webhook endpoint; use lokalise_update_webhook to change an existing webhook's settings instead of creating a duplicate.

NameTypeRequiredDescription

eventsarrayrequiredList of event names to subscribe this webhook to, for example project.translation.updated or project.key.added. Must contain at least one valid event name from the supported list. Note: Lokalise automatically adds a plural alias alongside some singular event names once a webhook is created (e.g. subscribing to project.key.added also shows project.keys.added on read-back) — both forms are accepted here so a list read from lokalise_get_webhook can always be resent as-is.

project_idstringrequiredUnique identifier of the Lokalise project to create the webhook in.

urlstringrequiredHTTPS endpoint that will receive the webhook's POST payloads. Lokalise validates this URL synchronously at creation time by making a live request to it and requires a 200 response, so it must already be reachable and responding correctly (a placeholder or non-responsive URL will fail creation).

branchstringoptionalLimit the webhook to a specific project branch. Omit this to apply the webhook to all branches.

event_lang_maparrayoptionalRestricts specific events to only fire for certain languages. Each entry pairs one event name with a list of language ISO codes; only project.translation.updated and project.translation.proofread support this mapping. Omit this to have those events fire for all languages in the project.

lokalise_delete_all_contributors#Start an asynchronous job that deletes every contributor from a Lokalise project. Returns a job ID for the deletion job, not the deletion result itself. Use this to reset project access before re-inviting or re-importing contributors; poll Get Contributor Bulk Deletion Job with the returned job ID to check progress and completion. This action cannot be undone, and only one bulk deletion can run per project at a time. Known upstream issue (confirmed live, 2026-09-04): Lokalise's API currently rejects every call to this exact, documented endpoint with `400 Invalid type of contributor_id parameter` — as if it were routing the request to their singular DELETE /contributors/{contributor_id} endpoint instead, treating the literal path segment 'import' as a contributor_id. Verified by proxying the request directly (bypassing this tool's own request construction) with the identical path/method/body Lokalise's own OpenAPI spec documents. This looks like a bug or route-priority issue on Lokalise's side, not a defect in this tool's request shape — nothing in the request can currently work around it.1 param

Start an asynchronous job that deletes every contributor from a Lokalise project. Returns a job ID for the deletion job, not the deletion result itself. Use this to reset project access before re-inviting or re-importing contributors; poll Get Contributor Bulk Deletion Job with the returned job ID to check progress and completion. This action cannot be undone, and only one bulk deletion can run per project at a time. Known upstream issue (confirmed live, 2026-09-04): Lokalise's API currently rejects every call to this exact, documented endpoint with `400 Invalid type of contributor_id parameter` — as if it were routing the request to their singular DELETE /contributors/{contributor_id} endpoint instead, treating the literal path segment 'import' as a contributor_id. Verified by proxying the request directly (bypassing this tool's own request construction) with the identical path/method/body Lokalise's own OpenAPI spec documents. This looks like a bug or route-priority issue on Lokalise's side, not a defect in this tool's request shape — nothing in the request can currently work around it.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise project to delete all contributors from.

lokalise_delete_comment#Delete a comment from a translation key in a Lokalise project. You can only delete comments you added yourself. Returns the project ID and a boolean confirming the comment was deleted. Use this to remove an outdated or incorrect comment; this action cannot be undone.3 params

Delete a comment from a translation key in a Lokalise project. You can only delete comments you added yourself. Returns the project ID and a boolean confirming the comment was deleted. Use this to remove an outdated or incorrect comment; this action cannot be undone.

NameTypeRequiredDescription

comment_idintegerrequiredThe unique numeric identifier of the comment to delete.

key_idintegerrequiredThe unique numeric identifier of the translation key the comment belongs to.

project_idstringrequiredThe unique identifier of the Lokalise project the key belongs to.

lokalise_delete_contributor#Remove a contributor from a Lokalise project, permanently revoking their access. Returns confirmation that the contributor was deleted, along with the project ID. Use this to remove a contributor entirely. Use lokalise_update_contributor to change their permissions instead of removing them. Requires the contributor ID; look it up with lokalise_get_contributor if you don't already have it.2 params

Remove a contributor from a Lokalise project, permanently revoking their access. Returns confirmation that the contributor was deleted, along with the project ID. Use this to remove a contributor entirely. Use lokalise_update_contributor to change their permissions instead of removing them. Requires the contributor ID; look it up with lokalise_get_contributor if you don't already have it.

NameTypeRequiredDescription

contributor_idintegerrequiredThe unique numeric identifier of the contributor to delete.

project_idstringrequiredThe unique identifier of the Lokalise project the contributor belongs to.

lokalise_delete_custom_status#Delete a custom translation status from a Lokalise project. Returns confirmation that the status was deleted, along with the project ID. Use this to permanently remove a status you no longer need. Use lokalise_update_custom_status to rename or recolor a status instead of deleting it. Requires the status ID; look it up with lokalise_list_custom_statuses if you don't already have it.2 params

Delete a custom translation status from a Lokalise project. Returns confirmation that the status was deleted, along with the project ID. Use this to permanently remove a status you no longer need. Use lokalise_update_custom_status to rename or recolor a status instead of deleting it. Requires the status ID; look it up with lokalise_list_custom_statuses if you don't already have it.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise project the custom translation status belongs to.

status_idintegerrequiredThe unique numeric identifier of the custom translation status to delete.

lokalise_delete_file#Permanently delete a file and all of its associated keys from a Lokalise project. Returns the project ID and a file_deleted confirmation flag. Use lokalise_list_files first to find the file_id. Only supported for Documents and Marketing/Support project types, not Software (localization_files) projects.2 params

Permanently delete a file and all of its associated keys from a Lokalise project. Returns the project ID and a file_deleted confirmation flag. Use lokalise_list_files first to find the file_id. Only supported for Documents and Marketing/Support project types, not Software (localization_files) projects.

NameTypeRequiredDescription

file_idnumberrequiredThe unique identifier of the file to delete, as returned by the List Files tool.

project_idstringrequiredThe unique identifier of the Lokalise project that owns the file. Example: 3002780358964f9bab5a92.87762498.

lokalise_delete_glossary_terms#Permanently delete one or more glossary terms from a Lokalise project by ID. Returns counts and IDs of the terms that were deleted, plus any that failed to delete with an error message. Use lokalise_list_glossary_terms first to find the term IDs you want to remove.2 params

Permanently delete one or more glossary terms from a Lokalise project by ID. Returns counts and IDs of the terms that were deleted, plus any that failed to delete with an error message. Use lokalise_list_glossary_terms first to find the term IDs you want to remove.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise project to delete glossary terms from. Example: 3002780358964f9bab5a92.87762498.

term_idsstringrequiredNumeric IDs of the glossary terms to delete, as a comma-separated list (no spaces required). Example: 1234,5678.

lokalise_delete_key#Delete a single translation key, and all of its translations, from a Lokalise project. Returns the project ID, whether the key was removed, and the number of keys still locked in the project. Use this to remove one key. Use lokalise_delete_keys to remove multiple keys in a single bulk call. Requires a key_id — find one with lokalise_list_keys or lokalise_get_key first.2 params

Delete a single translation key, and all of its translations, from a Lokalise project. Returns the project ID, whether the key was removed, and the number of keys still locked in the project. Use this to remove one key. Use lokalise_delete_keys to remove multiple keys in a single bulk call. Requires a key_id — find one with lokalise_list_keys or lokalise_get_key first.

NameTypeRequiredDescription

key_idintegerrequiredThe numeric ID of the key to delete.

project_idstringrequiredThe unique identifier of the Lokalise project containing the key. Find it with lokalise_list_projects.

lokalise_delete_keys#Permanently delete one or more translation keys, and their translations, from a Lokalise project. Returns a confirmation flag and a count of any keys that were locked and could not be removed. Use this to remove keys you no longer need. Use lokalise_empty_project instead to remove every key in a project at once. This action cannot be undone.2 params

Permanently delete one or more translation keys, and their translations, from a Lokalise project. Returns a confirmation flag and a count of any keys that were locked and could not be removed. Use this to remove keys you no longer need. Use lokalise_empty_project instead to remove every key in a project at once. This action cannot be undone.

NameTypeRequiredDescription

keysarrayrequiredList of numeric key IDs to permanently delete from the project. Example: [12345, 12346].

project_idstringrequiredUnique identifier of the Lokalise project the keys belong to. Example: '3002780358964f9bab5a92.87762498'.

lokalise_delete_language#Delete a language from a Lokalise project, permanently removing it and all of its translations. Returns the project ID and a boolean confirming the language was deleted. Use this to remove a language no longer needed for translation; this action cannot be undone. Requires the language's numeric ID, which you can find with a project languages listing tool.2 params

Delete a language from a Lokalise project, permanently removing it and all of its translations. Returns the project ID and a boolean confirming the language was deleted. Use this to remove a language no longer needed for translation; this action cannot be undone. Requires the language's numeric ID, which you can find with a project languages listing tool.

NameTypeRequiredDescription

lang_idintegerrequiredThe unique numeric identifier of the language to delete, as assigned by Lokalise (not the ISO code). Find it via a project languages listing tool.

project_idstringrequiredThe unique identifier of the Lokalise project the language belongs to.

lokalise_delete_payment_card#Permanently delete a saved payment card from your Lokalise account by its card ID. Returns the deleted card's ID and a confirmation flag. Use this to remove a card you no longer want available for translation orders. This cannot be undone; use the list payment cards tool first to confirm the card ID.1 param

Permanently delete a saved payment card from your Lokalise account by its card ID. Returns the deleted card's ID and a confirmation flag. Use this to remove a card you no longer want available for translation orders. This cannot be undone; use the list payment cards tool first to confirm the card ID.

NameTypeRequiredDescription

card_idintegerrequiredThe unique numeric identifier of the payment card to delete.

lokalise_delete_project#Permanently delete a Lokalise project, including all of its keys and translations. Returns the deleted project's ID and a confirmation flag. Use this only when the project itself should be removed entirely. Use lokalise_empty_project instead to clear a project's keys and translations while keeping the project. This action cannot be undone.1 param

Permanently delete a Lokalise project, including all of its keys and translations. Returns the deleted project's ID and a confirmation flag. Use this only when the project itself should be removed entirely. Use lokalise_empty_project instead to clear a project's keys and translations while keeping the project. This action cannot be undone.

NameTypeRequiredDescription

project_idstringrequiredUnique identifier of the Lokalise project to delete. Example: '3002780358964f9bab5a92.87762498'.

lokalise_delete_screenshot#Permanently delete a screenshot from a Lokalise project. Requires the Manage screenshots admin right. Returns a confirmation flag indicating the screenshot was deleted. Use this to remove a screenshot that is no longer needed; this action cannot be undone, so confirm the screenshot ID with lokalise_list_screenshots or lokalise_get_screenshot first.2 params

Permanently delete a screenshot from a Lokalise project. Requires the Manage screenshots admin right. Returns a confirmation flag indicating the screenshot was deleted. Use this to remove a screenshot that is no longer needed; this action cannot be undone, so confirm the screenshot ID with lokalise_list_screenshots or lokalise_get_screenshot first.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise project that owns the screenshot.

screenshot_idintegerrequiredThe unique numeric identifier of the screenshot to delete.

lokalise_delete_snapshot#Permanently delete a snapshot from a Lokalise project. Returns the project ID and a boolean confirming the snapshot was deleted. Use this to clean up snapshots you no longer need; deleted snapshots cannot be recovered or restored afterward, so make sure you won't need lokalise_restore_snapshot on it first.2 params

Permanently delete a snapshot from a Lokalise project. Returns the project ID and a boolean confirming the snapshot was deleted. Use this to clean up snapshots you no longer need; deleted snapshots cannot be recovered or restored afterward, so make sure you won't need lokalise_restore_snapshot on it first.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise project the snapshot belongs to.

snapshot_idintegerrequiredThe unique numeric identifier of the snapshot to permanently delete. This cannot be undone.

lokalise_delete_task#Permanently delete a task from a Lokalise project. Returns the project ID and a boolean confirming the task was deleted. Use this to remove tasks that are no longer needed; deleted tasks and their language/progress data cannot be recovered afterward.2 params

Permanently delete a task from a Lokalise project. Returns the project ID and a boolean confirming the task was deleted. Use this to remove tasks that are no longer needed; deleted tasks and their language/progress data cannot be recovered afterward.

NameTypeRequiredDescription

project_idstringrequiredThe unique identifier of the Lokalise project the task belongs to.

task_idintegerrequiredThe unique numeric identifier of the task to permanently delete. This cannot be undone.

lokalise_delete_team_group#Delete a user group from a Lokalise team, permanently removing the group and its project and member assignments. Returns confirmation that the group was deleted, along with the team ID. Use this to remove a group you no longer need. The projects and members themselves are not deleted, only the group's association with them. Requires Admin rights in the team. This action cannot be undone.2 params

Delete a user group from a Lokalise team, permanently removing the group and its project and member assignments. Returns confirmation that the group was deleted, along with the team ID. Use this to remove a group you no longer need. The projects and members themselves are not deleted, only the group's association with them. Requires Admin rights in the team. This action cannot be undone.

NameTypeRequiredDescription

group_idintegerrequiredThe numeric ID of the group to delete.

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

lokalise_delete_team_user#Remove a user from a Lokalise team, revoking their access to the team and its projects. Returns confirmation that the user was deleted. Use this to offboard a team member; this action cannot be undone. Use lokalise_list_team_users to find the user ID first. Requires Admin role in the team.2 params

Remove a user from a Lokalise team, revoking their access to the team and its projects. Returns confirmation that the user was deleted. Use this to offboard a team member; this action cannot be undone. Use lokalise_list_team_users to find the user ID first. Requires Admin role in the team.

NameTypeRequiredDescription

team_idintegerrequiredThe numeric ID of the Lokalise team to remove the user from. Find it via lokalise_list_teams.

user_idintegerrequiredThe numeric ID of the team user to delete. Find it via lokalise_list_team_users.

lokalise_delete_webhook#Permanently delete a webhook from a Lokalise project. Returns the project ID and a confirmation flag indicating the webhook was deleted. Use this to stop event notifications from being sent to a webhook endpoint; this action cannot be undone, so confirm the webhook_id with lokalise_list_webhooks first if unsure.2 params

Permanently delete a webhook from a Lokalise project. Returns the project ID and a confirmation flag indicating the webhook was deleted. Use this to stop event notifications from being sent to a webhook endpoint; this action cannot be undone, so confirm the webhook_id with lokalise_list_webhooks first if unsure.

NameTypeRequiredDescription

project_idstringrequiredUnique identifier of the Lokalise project the webhook belongs to.

webhook_idstringrequiredUnique identifier of the webhook to delete.

lokalise_download_files#Export a Lokalise project's translation files synchronously as a .zip bundle uploaded to Amazon S3. Returns the project ID and a bundle_url pointing to the generated .zip, available to download for about a month. Use lokalise_async_download_files instead for large projects (10,000+ key-language pairs), since this endpoint is limited to smaller ones.23 params

Export a Lokalise project's translation files synchronously as a .zip bundle uploaded to Amazon S3. Returns the project ID and a bundle_url pointing to the generated .zip, available to download for about a month. Use lokalise_async_download_files instead for large projects (10,000+ key-language pairs), since this endpoint is limited to smaller ones.