LanguageOps API

Your localization workflow, API first

Send whole source files, structure and all, through extraction, translation, terminology, QA, LQA, review, and reconstructed export. Keep your team in control while your systems do the repetitive work.

Request API access See the workflow
One API
Files, translation, QA and export
Async by design
Jobs, status and safe retries
Observable
Cost, tokens, failures and polling
Workflow

From source file to delivery

  1. Create and upload

    Create a project with source and target languages, then upload DOCX, IDML, JSON, spreadsheets, XLIFF and other supported files.

  2. Run the workflow

    Start translation, terminology-aware enhancement, automated QA and optional LQA as one asynchronous job.

  3. Review when needed

    Route exceptions into the browser editor while clean batches continue automatically.

  4. Export the original format

    Reconstruct the translated source format or export XLIFF, TMX and QA evidence for downstream systems.

Capabilities

An API for whole localisation jobs

  • File-aware processing

    Preserve structure, tags, placeholders and round-trip metadata across complex source formats.

  • Translation + quality

    Combine MT and language models with project terminology, QA profiles, LQA and approval workflows.

  • TM and termbase access

    Search, import and export translation memories; attach glossaries and enforce terminology in context.

  • Safe automation

    Use idempotency keys, explicit job IDs, rate limits, cancellation, structured errors and retry guidance.

  • Secure team keys

    Organization-scoped credentials are shown once and stored as one-way digests, with immediate revocation.

  • Unit economics built in

    Track batch size, tokens per word, calls per job, polling share, LQA cost, failure rate and availability.

Operations

Know whether the automation is worth it

  • Average batch size
  • Tokens processed per word
  • Calls per job
  • Requests per 1,000 words
  • Cost per LQA job
  • Retry and failure rates
  • Polling versus useful calls
  • Support time per API customer
  • Availability and response time

Build your first LanguageOps workflow

API access is available on paid plans. Start with a production pilot; a dedicated sandbox and public CLI distribution are on the roadmap.

Talk to us See plans