> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-developer-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-developer-guide/api-documentation/recipes/sending-multilingual-push.md).

# Sending a Multilingual Push

Send one push request that carries the title, text, and click action for several languages.

This recipe shows how to send a single bulk push that carries the title, text, and click action for more than one language. You describe the message once in the request, and the languages object holds the translations.

## When to Use

This recipe fits campaigns for apps with users in several languages, where you want to keep every translation in one request instead of sending one request per language.

## Prerequisites

* REST API key of the application
* The title and text of the message in each language
* The click action, such as a deeplink, for each language when it differs

## Step 1: Define the Message

Start with the `message` object. It holds the base title, text, platforms, and click action of the push.

```json
"message": {
  "title": "New Update Available",
  "text": "Explore exciting features in the latest update!",
  "platforms": ["IOS", "ANDROID"],
  "click": {
    "deeplink": "https://www.example.com"
  }
}
```

## Step 2: Add the Languages

Add a `languages` object next to `message`. Each key is a language name, and each value carries the `title`, `text`, and `click` of that language.

```bash
curl https://restapi.netmera.com/rest/3.0/sendBulkNotification \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'X-netmera-api-key: <API_KEY>' \
  --data '{
  "message": {
    "title": "New Update Available",
    "text": "Explore exciting features in the latest update!",
    "platforms": ["IOS", "ANDROID"],
    "click": {
      "deeplink": "https://www.example.com"
    }
  },
  "languages": {
    "English": {
      "title": "New Features",
      "text": "Discover what is new in this update.",
      "click": { "deeplink": "https://www.example.com" }
    },
    "Turkish": {
      "title": "Yeni Özellikler",
      "text": "Bu güncellemede neler yeni öğrenin.",
      "click": { "deeplink": "https://www.example.com" }
    }
  },
  "target": {
    "sendToAll": true
  }
}'
```

**Expected result:** HTTP 200 with a `notificationKey`.

## Step 3: Read the Delivery Statistics

Pass the `notificationKey` to `getPushStats` as shown in [Sending a Push Campaign to a Tagged Audience](/netmera-developer-guide/api-documentation/recipes/sending-push-to-tagged-audience.md).

## Verification Checklist

* Each entry in `languages` has the `title`, `text`, and `click` of that language
* The language names are written the same way in every request
* `target` is set; to reach all users, use `"sendToAll": true`
* `platforms` lists every platform that should receive the message

## Related Pages

For the full request format, see the Multilanguage section of the [Notifications](/netmera-developer-guide/api-documentation/rest-api/notifications.md) page in the REST API documentation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://user.netmera.com/netmera-developer-guide/api-documentation/recipes/sending-multilingual-push.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.