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

# Fincome

Sending data to Fincome: Step-by-Step guide

DinMo supports the sending of data to Fincome to keep customer’s data up to date from your data warehouse.

## Supported Destination Services

DinMo supports the following destination service:

* [**Synchronize customers’s data**](/integrations/destination-platforms/fincome/synchronize-customers-data.md), to update customers’s attributes values in Fincome

Please refer to the dedicated documentation page for more information.

## Authentication to Fincome

To connect DinMo to Fincome, you first need to create an API key in your Fincome platform.

Go to Settings, then to Developers and Create a secret key.

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

**Information needed**

To create a Fincome destination in DinMo, you will need:

* **API\_KEY**


---

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