Front-end integrations using a Unified API

Many patterns described in this section run in the background, for example a data sync that runs every 5 minutes. This pattern however, describes integrations in a front-end (UI) of a SaaS platform.

Blendr.io supports front-end integrations by allowing you to build a Unified API. This means that you do a one-time effort to implement a Unified API in your front-end. Once this is done, you can use Blendr.io to extend your Unified API with more supported platforms, without the need to change the code of your front-end.

Implementing a Unified API

Blendr.io can be used to build a Unified API. This means that you make API calls from your platform in order to e.g. retrieve data from other cloud platforms on behalf of your customers. One customer might be using Salesforce and another might be using e.g. Hubspot.

In this case Blend templates are created using Bundles. A bundle is a combination of Blends. You could have for example a Bundle called Salesforce and a Bundle called Hubspot. The Salesforce Bundle handles the integration between your platform and Salesforce. The Hubspot Bundle handles the integration between your platform and Hubspot.

In each Bundle, you can have multiple Blends, e.g. a Blend that will do a contact sync between your platform and another CRM. In the same Bundle, you can also have smaller Blends that act as a Unified API.

For example you could have a Blend called list_contacts in each Bundle. Thanks to the Blendr.io SaaS API, you can call these Blends from your platform, as if they are a Unified API. Here's the endpoint to use:

Execute an integration (blend) in an account alt text