Overview

Public message creation does not accept an i18n field directly. Localization currently shows up in two places:

GET /templates and GET /templates/{identifier} can include stored locale variants when you pass withi18n=true.
POST /messages resolves template content from templateId, the destination country, and any stored locale variants already attached to that template.

`i18n` key format

Locale keys use lowercase country codes such as:

br
us
mx

Inspect stored locale variants

curl "https://api.rewritetoday.com/v1/templates/otp_login?withi18n=true" \
  -H "Authorization: Bearer rw_..."

Example response:

{
  "ok": true,
  "data": {
    "id": "748395130237498600",
    "name": "otp_login",
    "content": "Rewrite: your code is {{code}}",
    "i18n": {
      "br": "Rewrite: seu codigo e {{code}}"
    },
    "variables": [
      { "name": "code", "fallback": "000000" }
    ],
    "description": "Login OTP SMS",
    "tags": {
      "flow": "otp"
    },
    "createdAt": "2026-05-06T18:30:00.000Z"
  }
}

Notes

content remains the default fallback.
Public template create and update routes no longer document i18n writes.
Keep variable names identical across every stored locale variant.