Translating Email Content

Use Localize to help translate your email content.

There are a couple of ways that you can use Localize to translate your email content.

Static Email Content

For email content that doesn't change very much, you can use Localize to manage the translations of the content, using the Text Import method. You can read all about it here.


Semi-automated Email Content

You can manage translations of email content using our REST API, optionally with human translations.

Use Case:

  1. Send the contents of the email in separate phrases to Localize using the Create phrase(s) endpoint.
  2. Use one of the various methods to get human translations for the phrases in the Localize dashboard.
  3. Human Translation Orders
  4. Invite translators to your Team
  5. Import/Export files for your translators to work in
  6. To get the translated version of the email contents, call the Get a Phrase endpoint for each phrase, sending in a hash of the source phrase.
  7. You can then replace the contents in the email with the human translated content.

"Real-time" Email Content

For emails that are created and delivered near-real-time, you can use our REST API to manage translations on-the-fly.
This method assumes you are using machine translations.

Use Case:

  1. Enable machine translations in your Project.
  2. Send the contents of the email in separate phrases to Localize using the Create phrase(s) endpoint.
  3. Be sure to add the label "auto-approve" - this will auto-approve the translation of the phrase, generating a machine translation for the phrase.
  4. To get the translated version of the email contents, call the Get a Phrase endpoint for each phrase, sending in a hash of the source phrase.
  5. You can then replace the contents in the email with the machine translated content.

Updated 9 days ago


Translating Email Content


Use Localize to help translate your email content.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.