> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chift.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing multiple connections

Advanced topic. Read [How it works](/guides/how-it-works) for the basic model, and [Create a connection](/guides/unified-api/how-to-connect) for the standard flow.

## The rule

A consumer can have several connections, but **only one connection per connector**. Odoo and Sage side by side is fine; two Odoo connections for the same consumer is not. The second `POST` returns an HTTP error `400`.

## Multiple connectors serving the same Unified API

Two different connectors can serve the same Unified API. A consumer connected to both Odoo *and* Sage has two connections behind the Accounting API, and a plain request is ambiguous: Chift cannot tell which one you mean.

In that case, pick the connection explicitly with one of these headers:

| Header                  | Value                                                                                                                             |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| `X-Chift-Integrationid` | The connector's `integrationid`, from [Get list of integrations](/api-reference/endpoints/integrations/get-list-of-integrations). |
| `X-Chift-Connectionid`  | The uuid of the specific connection, from [Get connections](/api-reference/endpoints/connections/get-connections).                |

<Note>
  You only need these when one consumer has several connections serving the **same** Unified API. Otherwise Chift resolves the connection for you and no header is required.
</Note>

## Multiple consumers for the same end-user

Sometimes your end-user needs access to the same connector more than once — for example, an accounting firm managing several folders in the same accounting system, where the connector doesn't support multi-folder or multi-entity natively.

The solution is to create **one consumer per connection**. Each consumer independently connects to the same connector, and you call the Unified API once per consumer.

<Info>
  Creating multiple consumers for the same end-user has no pricing impact — pricing is based on connections, not consumers.
</Info>

## Related

* [Create a connection](/guides/unified-api/how-to-connect)
* [Connection lifecycle](/guides/core-concepts/monitor-connections#connection-lifecycle)