> 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/emarsys.md).

# Emarsys

Sending data to Emarsys: Step-by-Step Guide

## Supported Destination Services

DinMo supports the following destination services:

* [Export contact lists](/integrations/destination-platforms/emarsys/export-contact-lists.md)
* [Synchronize contacts data](/integrations/destination-platforms/emarsys/synchronize-contacts-data.md)
* [Synchronize custom table's data (RDS)](/integrations/destination-platforms/emarsys/synchronize-custom-tables-data-rds.md)

Please refer to the dedicated documentation page for more information.

## Authentication to Emarsys

Regardless of the selected destination service, DinMo will always connect to Emarsys with an API user.

**Setup:** You will need your username, typically in the format of "account\_name00X" (X representing a digit), and the API secret. For an API secret, you need to create a new API user for DinMo under *Admin > Security Settings*.

**API Endpoint Configuration:** During the API key creation, you will need to enable the necessary endpoints. DinMo requires the following collection of endpoints: **contacts**, **fields**, and **contact lists**.

Please refer to the [Emarsys documentation](https://dev.emarsys.com/docs/core-api-reference/b3c3a1eba8515-authentication#creating-api-users) to learn more about permissions and API users.

{% hint style="warning" %}
Note that only account owners (and not admins) can create API users in Emarsys.
{% endhint %}


---

# 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/emarsys.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.