Implementations
On this page, we describe the usual implementations done by our clients.
- Authentication workflow
- Easy way - you do the work
- Lazy way - we do it for you
Those are example of implementations that can of course vary between the use cases of our customers. We do not limit ourselves to those use cases.
Authentication workflow
- From your software, you can initiate the integration for one of your customer.
- The consumerId is the link between your customer and Chift. You keep this in your database to be able to make requests to our API when required by your business case.
- Based on your consumerId, you receive a link that you can share with your customer to initiate a connection.
- Your users are redirected to Chift’s authentication page where they can connect to the softwares of your choice.
- Once the initial connection is setup, you can activate a webhook to receive asynchronously an event or your user can be redirected to the URL of your choice.
- Now you are ready to request our unified APIs.
Unifed API model
Our customers usually choose this approach. The authentication of their customers is managed as specified above. After the authentication of their customers/consumers is done, they can connect to our unified APIs to leverage the power of being instantly connected to multiple softwares.
Sync model
For customers that do not have the time to do the implementation themselves, we can help you by using our integration platform to build your synchronization in Chift. This helps you to leverage the magic of integrations without having to worry about building and maintaining any integration.