Getting started

This guide walks you through creating a namespace, adding a translation key, generating translations with AI, and fetching them from your application via the public API.

Prerequisites

A Norcube account (sign up).
An organization (one is created automatically on sign-up – see Platform → Organizations).

Create a namespace

A namespace is your translation workspace. Most teams create one per app or per client.

Open the dashboard and switch to LangSync from the product switcher.
Go to Namespaces → New namespace.
Fill in:
- Name – a short alphanumeric slug (e.g. marketing-site). Used in API paths.
- Context – free-text description of what's in this namespace. The AI reads it when translating.
- Default language – the language your source strings are written in (e.g. en-US).
Click Create.

Add a target language

Open the namespace and go to Languages.
Click Add language, pick one (e.g. de-DE), and save.

Repeat for each language you want to ship in.

Add your first term

Go to Terms inside the namespace.
Click New term.
Enter:
- Mark – the translation key (e.g. welcome.title).
- Default value – the source string (e.g. Welcome to our app).
- Toggle Translate automatically on.
Click Save.

The AI fills in the German translation in the background. Refresh the page to see it.

Create an API key

Go to API keys → New key.
Give it a name (e.g. production) and click Create.
Copy the key now – you won't be shown the full value again.

Fetch translations from your app

curl -H "Authorization: Apikey YOUR_API_KEY" \
  "<your-langsync-host>/api/v1/namespaces/marketing-site/terms/translations?langId=DE-LANGUAGE-ID"

Returns a JSON map of { "<term-mark>": "<translation>" } ready for your i18n library.

Next steps

Bulk-import terms from CSV

Onboard an existing translation file in one upload.

Use a glossary

Keep brand names and product terms consistent across every AI call.

Sync from CI

Push terms from a Git repo on every release with the LangSync CLI.