> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/batch.md).

# Batch

Sending data to Batch: Step-by-Step guide

DinMo supports both the sending of data to the two Batch product suites:

* **Batch Mobile Engagement Platform** (MEP)
* **Batch Customer Engagement Platform** (CEP)

## Supported Destination Services

DinMo supports the following destination services:

* **Batch MEP**
  * [Synchronize contacts](/integrations/destination-platforms/batch/synchronize-contacts-mep.md), to update attributes in the contact table
  * [Delete profiles](/integrations/destination-platforms/batch/delete-profiles-cep-and-mep.md), to remove a person from Batch (for example, for GDPR purposes)
* **Batch CEP**
  * [Export contact lists](/integrations/destination-platforms/batch/export-contact-lists-cep.md), to create audiences in the Batch dashboard
  * [Delete profiles](/integrations/destination-platforms/batch/delete-profiles-cep-and-mep.md), to remove a person from Batch (for example, for GDPR purposes)
  * [Synchronize profiles](/integrations/destination-platforms/batch/synchronize-profiles-cep.md), to update contact attributes in the CEP project
  * [Send events](/integrations/destination-platforms/batch/send-events-cep.md), to create and update event linked to a Batch profile
  * [Synchronize product attributes](/integrations/destination-platforms/batch/synchronize-catalog-attributes.md), to update product catalog

Please refer to the dedicated documentation page for more information.

## Authentication to Batch

Regardless of the selected destination service, DinMo will always connect to Batch using REST API keys.

You will find their values in the General tab of your Batch settings:

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2Fgit-blob-5c077532c06baaaaa42c0f7dca7484b27de9e03a%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

### Informations needed

* **For Batch MEP**: API key & REST API keys & Project API Key (only for GDPR purposes)
* **For Batch CEP**: REST API Key & Project API Key

Note that the keys will be different for Android and iOS apps. To target both apps, please create two separate Batch platforms.


---

# 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://docs.dinmo.io/integrations/destination-platforms/batch.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.