Skip to main content
A sync needs one setup per end-user: the end-user connects their software and fills the mappings the flow needs. Chift offers three models for that setup. They differ in how much you build and in where your end-user completes it. Read this page before you write any code. The model you choose decides whether you integrate the Chift API at all.

​
The three models

Embedded

You create the consumer and the activation link from your backend.

Pre-OAuth2

You share one static URL protected by your own OAuth2 flow.

Marketplace

Chift hosts a marketplace where your end-users sign up themselves.

​
Compare the models

The three models run the same flows. They change who triggers the setup and where it happens, not what the sync does.

​
Which one to choose

  • Choose embedded when you want to decide where and when the setup appears in your product, and you accept writing the integration. This is the only model that lets you place the connector choice inside your own interface.
  • Choose pre-OAuth2 when your software already has an OAuth2 flow and you want a white-label experience without writing code.
  • Choose marketplace when you want no development at all, and your end-users can hold an account in Chift. This model also suits accountants, who manage several client organizations from one account.

​
Next

Once you have chosen, follow the page for your model. For the embedded model, continue with Activating a sync.