Update translation in a campaign

Use this endpoint to update multiple translations for a campaign.

If you want to update translations after a campaign has been launched, you’ll need to save your message as a draft first.

Prerequisites

To use this endpoint, you’ll need an API key with the campaigns.translations.update permission.

Rate limit

This endpoint has a rate limit of 250,000 requests per minute.

Path parameters

There are no path parameters for this endpoint.

Request parameters

Note all translation IDs are considered universal unique identifiers (UUIDs), which can be found in Multi-Language Support settings or in the GET request response.

Example request

1
2
3
4
5
6
7
8
9
10
Content-Type: application/json
Authorization: Bearer YOUR-REST-API-KEY
{
    "campaign_id": "e24404b3-3626-4de0-bdec-06935f3aa0ab", // CAMPAIGNS ONLY
    "message_variation_id": "f14404b3-3626-4de0-bdec-06935f3aa0ad",
    "locale_id": "h94404b3-3626-4de0-bdec-06935f3aa0ad",
    "translation_map": {
       "id_3": "Ein Absatz ohne Formatierung"
    }
}

Response

There are four status code responses for this endpoint: 200, 400, 404, and 429.

Example success response

1
2
3
{
	"message": "success"
}

Example error response

The status code 400 could return the following response body. Refer to Troubleshooting for more information about errors you may encounter.

1
2
3
4
5
6
7
{
	"errors": [
		{
			"message": "The provided locale code does not exist."
		}
	]
}

Troubleshooting

The following table lists possible returned errors and their associated troubleshooting steps.