Manage Lokalise secondary workflow: Download translations and integrate with app.
Use when downloading translation files, exporting translations,
or integrating Lokalise output into your application.
Trigger with phrases like "lokalise download", "lokalise pull translations",
"export lokalise", "get translations from lokalise".
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Manage Lokalise secondary workflow: Download translations and integrate with app.
Use when downloading translation files, exporting translations,
or integrating Lokalise output into your application.
Trigger with phrases like "lokalise download", "lokalise pull translations",
"export lokalise", "get translations from lokalise".
Designed for Claude Code, also compatible with Codex and OpenClaw
Lokalise Core Workflow B
Overview
Everything on the "Lokalise to app" side: download translated files, manage translations and review status, leverage translation memory, manage contributors and their language access, and handle format differences across JSON, XLIFF, and PO files.
Prerequisites
Lokalise API token exported as LOKALISE_API_TOKEN
Lokalise project ID exported as LOKALISE_PROJECT_ID
@lokalise/node-api installed for SDK examples
lokalise2 CLI installed for CLI examples
unzip available for extracting download bundles
Instructions
Download translated files. The download endpoint returns an S3 URL to a zip bundle — request the bundle, download the zip, then extract.
Manage translations — list, update, and mark as reviewed.
SDK — List translations for a language:
const frTranslations = await client.translations().list({
project_id: PROJECT_ID,
filter_lang_id: 673, // Language ID for French (find via languages endpoint)filter_is_reviewed: 0, // Only unreviewedlimit: 100,
});
for (const t of frTranslations.items) {
console.log(`[${t.key_id}] ${t.translation} (reviewed: ${t.is_reviewed})`);
}
SDK — Update a translation:
const updated = await client.translations().update(TRANSLATION_ID, {
project_id: PROJECT_ID,
translation: "Nouvelle traduction",
is_reviewed: false, // Mark as needing review after edit
});
SDK — Mark translations as reviewed (batch):
const unreviewed = await client.translations().list({
project_id: PROJECT_ID,
filter_lang_id: LANG_ID,
filter_is_reviewed: 0,
limit: 500,
});
for (const t of unreviewed.items) {
await client.translations().update(t.translation_id, {
project_id: PROJECT_ID,
is_reviewed: true,
});
}
console.log(`Marked ${unreviewed.items.length} translations as reviewed`);
SDK — List translations with cursor pagination (for large datasets):
SDK — Leverage TM during download (pre-translate empty keys):
// Pre-translate uses TM + MT before download// First, trigger pre-translation// Then download with filled translationsconst download = await client.files().download(PROJECT_ID, {
format: "json",
original_filenames: false,
bundle_structure: "%LANG_ISO%.json",
export_empty_as: "base", // Fallback to base language if TM has no match
});
Manage contributors — add translators and configure language access.
SDK — Add a translator with specific language access:
// Lokalise detects format from filename extension// Just make sure the filename matches the content formatawait client.files().upload(PROJECT_ID, {
data: base64Data,
filename: "messages.xliff", // Triggers XLIFF parserlang_iso: "en",
});
Output
Downloaded translation files extracted to project directory
Translations updated and review status managed
Contributors added with appropriate language permissions
Files exported in the correct format for your i18n framework
