lokalise-mcp/dist/domains/translations/translations.service.d.ts

The Lokalise MCP Server brings Lokalise's localization power to Claude and AI assistants—manage projects, keys, and translations by chat.

/**
 * Translations Service
 *
 * Service layer for interacting with Lokalise Translations API.
 * Handles all API communication and data transformation.
 */
import type { CursorPaginatedResult, Translation } from "@lokalise/node-api";
import type { BulkUpdateTranslationsSummary, BulkUpdateTranslationsToolArgsType, GetTranslationToolArgsType, ListTranslationsToolArgsType, UpdateTranslationToolArgsType } from "./translations.types.js";
/**
 * Translations service for Lokalise API operations
 */
export declare const translationsService: {
    /**
     * List translations for a project
     * Note: Translations use cursor pagination, not standard pagination
     */
    list(args: ListTranslationsToolArgsType): Promise<CursorPaginatedResult<Translation>>;
    /**
     * Get a specific translation
     */
    get(args: GetTranslationToolArgsType): Promise<Translation>;
    /**
     * Update a translation
     */
    update(args: UpdateTranslationToolArgsType): Promise<Translation>;
    /**
     * Bulk update multiple translations with rate limiting and retry logic
     */
    bulkUpdate(args: BulkUpdateTranslationsToolArgsType): Promise<BulkUpdateTranslationsSummary>;
};
/**
 * Implementation Notes:
 *
 * 1. Translations use CURSOR PAGINATION, not standard page/limit pagination
 * 2. Filter by language ID requires numeric ID, not ISO code
 * 3. Review and verification statuses are important for translation workflow
 * 4. Translation content can be string or object (for plural forms)
 * 5. Custom translation statuses allow for custom workflow states
 */