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

# Selligent

Sending data to Selligent: Step-by-Step Guide

## Supported Destination Services

DinMo supports the following destination services:

* [Export contact lists](/integrations/destination-platforms/selligent/export-contact-lists.md)
* [Synchronize record attributes](/integrations/destination-platforms/selligent/synchronize-record-attributes.md)

Please refer to the dedicated documentation page for more information.

## Authentification to Selligent

To connect to Selligent, go to the Destinations overview page in DinMo and click the **Add destination** button. Select Selligent and click on continue. You can then authenticate DinMo to Selligent via a Service Account.

To create this service accout, go to your Selligent dashboard and click the settings gear in the bottom left corner.

Navigate to **Access Management > Service Accounts** and click **New**. Make sure to configure the following endpoints:<br>

* **For both destination services:**
  * GET `/organizations/{organization}/lists/{api_name}`
  * GET `/organizations/{organization}/lists`
* **To Synchronize Record Attributes**
  * POST `/organizations/{organization}/lists/{api_name}/data/load`
  * POST `/organizations/{organization}/lists/{api_name}/data`
  * GET `/organizations/{organization}/lists/{api_name}/fields`
  * GET `/organizations/{organization}/lists/{api_name}/relations`
  * POST `/organizations/{organization}/lists/{api_name}/fields`
* **To Export contact lists**
  * GET `/organizations/{organization}/lists/{api_name}/segments`
  * DELETE `/organizations/{organization}/lists/{api_name}/segments/{segment_api_name}/data/clear`
  * POST `/organizations/{organization}/lists/{api_name}/segments/static`
  * POST `/organizations/{organization}/lists/{api_name}/segments/{segment_api_name}/data/load`
  * DELETE `/organizations/{organization}/lists/{api_name}/segments/{segment_api_name}/data`

The `GET /relations` and `POST /data` endpoints are required to synchronize attributes from lists linked through outgoing one-to-one relations. The service account must also be allowed to read fields from the parent list and every related list used in the activation.

Then in DinMo:

1. Enter the Selligent hostname used to access your control panel, which is usually `{organization}.slgnt.eu`
2. Enter the API and Secret keys from the Service Account you created


---

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