Skip to main content

How Multilanguage Works

Each formula can have one version of its content per language. These language versions are separate message-content records — each with its own structure and variants.
When Aampe sends a message, it selects the message-content that matches the user’s language. Each language version is personalized independently — Aampe learns label preferences per language.

Step 1 — List Available Languages

Response:

Step 2 — Create a Language (if it doesn’t exist)


Step 3 — Create the Formula

Create the formula as normal. The API automatically creates a message-content for the default language. You will add the German message-content separately.

Step 4 — Set the Default Language Content

Pre-generate component instance IDs. These identify the slots for the default language — each language uses its own component instance IDs.

Step 5 — Add a New Language Version

Create a new message-content for German by posting with formula_id and language_id:
Then set its structure and variants the same way as the default language — using new component instance IDs:

Reading Back All Language Versions


Key Points

  • The default language’s message-content is auto-created with the formula — do not create it manually
  • Each language version uses its own component instance IDs (the UUIDs you generate per slot)
  • Labels and component types are shared across languages — you do not need to recreate them
  • Each language version is personalized independently by Aampe