Skip to main content
One integration to read, write, and act on financial data across accounting, invoicing, POS, e-commerce, payment, PMS, and banking systems.

​
How Chift works

Chift sits between your software and your end-users’ financial tools.
Your software integrates once with Chift. Chift connects to the tool of each end-user, for example Exact Online, Lightspeed or Shopify.

Chift sits between your software and your end-users' financial tools.

Whichever way you use it, the same three objects show up. Learn them once here.

​
The three objects

Everything in Chift is built from three objects, and how they relate is the part worth getting straight up front:
Two consumers, each with connections that link to shared connectors

Consumers, connections, and connectors.

  • Connector: software Chift talks to (Odoo, Sage, Shopify, Lightspeed). Chift builds and maintains these. You choose which to activate. In your product, an integration you offer.
  • Consumer: one of your end-users, identified by a uuid (consumerid). In your product, a tenant or account in your database, usually one per end-user.
  • Connection: one consumer linked to one connector, holding that end-user’s credentials and configuration. “This end-user connected their Odoo.”
Chift’s API paths and fields use the word integration (GET /integrations, integrationid) for historical reasons. In the documentation we say connector. They mean the same thing.

​
Two ways to use Chift

Both start from the same connectors, consumers, and connections. What differs is who writes the integration logic and who triggers it.
Unified API and Syncs build paths

Unified API: you build and trigger the integration. Syncs: Chift builds and runs it.

Unified API

You build and trigger the integration.

Syncs

Chift builds and runs the integration.