Hyperlocalise logo
Request a Demo
For developers

CLI and API

Localisation as code, from your terminal and CI

Extract messages, push source files, and pull translations with one CLI and a config file in your repo. Use the API when you need to build your own pipeline.

The shift

From manual exports to a pipeline you can version

Today

  • Someone exports files, uploads them, and downloads translations by hand.
  • Each repository has its own scripts, and they break when the TMS changes.
  • Translation status is invisible to the build.

With Hyperlocalise

  • One i18n.yml in the repo defines locales, files, and mappings.
  • The same CLI runs on a laptop and in CI, with a scoped API key.
  • Files and jobs are available over HTTP for anything custom.

How it works

From one config file to translations in every build

Set it up in minutes. The same commands run on your machine and in CI.

i18n.yml
locales:  source: en-US  targets: [de-DE, fr-FR, ja-JP]buckets:  app:    files:      - from: locales/{{source}}.json        to: locales/{{target}}.json

Watch

See the platform in action

A short walkthrough of projects, review, automations, and agents working across markets.

Works with

Works with your repo and toolchain

  • GitHub
  • Phrase
  • Crowdin
  • Lokalise
  • Smartling
  • OpenAI
  • Claude
  • Gemini

Key capabilities

Built for engineering teams

  • One config file

    Define locales, files, and mappings in i18n.yml, versioned with your code.

  • Message extraction

    Extract messages from source code into a catalog with one command.

  • Push and pull sync

    Move source files up and translations down from a laptop or CI.

  • Scoped API keys

    Give CI only the permissions it needs, and revoke keys from settings.

  • Files and jobs API

    Upload files, create jobs, check progress, and download results over HTTP.

  • Webhooks

    Get notified when jobs finish, so your pipeline can react.

Example workflow

How we localise our own app

Hyperlocalise's web app ships in ten languages using the same CLI. No one uploads a file by hand.

  1. On every merge

    Extract and push

    CI runs hl extract and hl sync push, so new messages reach the workspace within minutes.

  2. During the day

    Translate and review

    Linguists and agents translate in the workspace. Nobody touches a file.

  3. Every night

    Pull translations

    A scheduled job runs hl sync pull and opens a pull request with the updated locale files.

  4. Next morning

    Review and merge

    An engineer reviews the diff and merges. Every locale stays current with no manual steps.

Built for your role

One platform for everyone who takes you global

Localisation managers run the programme, growth teams open new markets, and developers ship the code. Find the workflow that matches your job.

A few things you might ask.

Localisation in your terminal, CI, and code.

Any more questions?

Contact us

Put localisation in your pipeline

Start free, create an API key, and run your first sync from your terminal in minutes.