Skip to main content
Advanced topic. Read How it works for the basic model, and Create a connection 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:
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.

​
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.
Creating multiple consumers for the same end-user has no pricing impact — pricing is based on connections, not consumers.