Skip to main content
Pre-OAuth2 is an add-on to the embedded model. Your backend creates the connection to your own software for your end-user. Your end-user then connects only their own software during the setup.

Why use it

In an embedded sync, your software is the fixed side. Without pre-OAuth2, your end-user also authenticates your software on the setup page, although they are already signed in to your product. With pre-OAuth2, you provide the credentials of the end-user for your own software directly. No OAuth2 flow runs: you own the authentication of your software, and your end-user is already connected.
The Unified API also has a pre-OAuth2 feature. It uses the same call in another context: there, you run the OAuth2 flow of a third-party software yourself. In a sync, the credentials are those of your own software.

How it works

Pre-OAuth2 adds one call before the normal embedded flow.
1

Create the consumer

Create the consumer of your end-user, as in the embedded flow. See Activating a sync.
2

Create the connection to your own software

Create a connection for this consumer with the integrationid of your software, a name, and the credentials of the end-user.
API reference: Add new connection ↗
3

Continue with the embedded flow

Create the activation link and send your end-user to it. Your software is already connected, so your end-user connects only their own software and completes the mappings.
Chift sets up pre-OAuth2 with you. Contact us to enable it for your account.