Skip to main content
Chift exposes one Unified API per category of financial software. Each one normalizes the data model across every connector in that category, so you integrate once and work with the same objects whatever software your end-users run. With the Unified API, your engineering team drives everything: you call Chift’s endpoints directly and read or write your end-users’ financial data whenever your product needs to. Chift keeps the credentials working. New to the terms connector, consumer, and connection? See How Chift works first.
Unified APIs overview

One Unified API per category of financial software.

​
Who does what

  • You create the consumer, create the connection, and hand the resulting activation link to your end-user. Afterwards you make the Unified API calls.
  • Your end-user opens that link and authorizes access to their software. Depending on the connector, they sign in via OAuth2, enter API credentials, or install the local agent. Some connectors then ask follow-up questions, such as which accounting folder or which POS location to use.
  • Chift stores and refreshes the credentials, and exposes the data through one Unified API shape regardless of which connector is behind it.
Jane connects her Pennylane: your app, Chift, Pennylane, then back to your app

Jane connects her Pennylane from your app.

​
What you store

Just the consumerid. Keep it on your end-user record: it is the key you pass to every Unified API call to say whose data you want. You do not need to store connection IDs for normal use. Chift resolves the right connection from the consumer and the API you are calling.
A Unified API call through Chift

A Unified API call through Chift.