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 400.

​
Multiple connections on same consumer for same 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.

​
Creating connections with credentials

For some connectors you can pass credentials directly on the connection POST instead of sending your end-user through an activation link. This lets you create connections on your customers’ behalf. Requires integrationid and name, and is not available for OAuth2 connectors. Call Get list of integrations to see which credentials a connector expects.