Friday, December 29, 2023
HomeBusinessBridging the Hole Between SaaS Functions

Bridging the Hole Between SaaS Functions

A unified utility programming interface (API) is an API that serves as a layer of abstraction that may talk with a number of underlying APIs concurrently. 

In consequence, every object and endpoint within the unified API maps to a corresponding object and endpoint within the underlying API. This allows SaaS corporations to construct a single integration with the unified API and immediately ship integrations with every of the underlying APIs.

On this article, we are going to dive deep into unified APIs, how they work, their challenges and options, and the way they profit SaaS corporations.

What downside do unified APIs remedy?

SaaS consumers have come to anticipate seamless native integrations from the options they buy. Interoperability is not a pleasant to have however a requirement. Nevertheless, constructing these native integrations with their different instruments is a problem each SaaS firm faces immediately, because it requires important engineering assets to ship and preserve.

For each integration, engineers should construct safe authentication, comb via the third-party app’s API documentation, implement the enterprise logic required to ship the use case and construct an intuitive configuration expertise for the top consumer.

And this doesn’t account for all of the work concerned in sustaining and updating the combination as new function requests are added, when the third-party API releases breaking modifications, and the time builders spend serving to clients debug integration points.

Inside the context of SaaS integrations, unified APIs emerged lately as a technique to sort out the problem of understanding every third-party app’s API documentation.

At its core, this could save engineering groups from continuously studying or revisiting the nuances, shapes, and nomenclature for each particular person API, as soon as for each integration.

How do unified APIs work?

Let’s stroll via how a unified API works with a tangible instance.

Think about your clients are asking on your product to combine with their CRM – throughout your consumer base, some clients use Salesforce, others use HubSpot, and a few use Dynamics or Pipedrive.

A unified CRM API would summary the APIs of every of those CRMs by sustaining references to every of the underlying CRMs’ APIs.

unified APIs working example

Supply: Paragon

The instance right here reveals that every underlying CRM has an object that represents a “contact.”

HubSpot calls it a Contact, Salesforce gives each a Lead and a Contact object, and Pipedrive refers to contacts as Prospects. When a name is made to the “Contact” object inside the unified API,  the unified API will then reference the corresponding object within the specified service.

Now, object-level references are the primary layer, however inside these objects, there are additionally properties or fields which might be abstracted. Within the instance above, that would embody totally different nomenclature for title, ID, firm, and many others.

So, in case your crew is constructing a number of CRM integrations, theoretically, you may construct a single integration with a unified CRM API that allows you to ship all of the underlying CRM integrations concurrently.

Class-specific unified APIs

Not all APIs might be unified in a single API as a result of totally different SaaS purposes have distinctive information fashions, buildings, and options. 

Subsequently, distributors sometimes supply a number of unified APIs which might be particular to a sure SaaS vertical, comparable to CRM, accounting, or promoting, as these SaaS purposes may have comparatively related information buildings and share many widespread objects or properties.

When designing a unified API, the API supplier should rigorously select which underlying APIs to incorporate within the unified API, because the extra overlap the underlying APIs have, the broader the protection the unified API can present.

Nevertheless, if the unified API have been to incorporate purposes that aren’t as related to one another, it will be much less helpful because it would not be capable of floor all of the objects and properties that the underlying APIs share. As an example, a unified API that features a CRM and an accounting utility is probably not very helpful as a result of outdoors of a “buyer” object, there is probably not a lot overlap throughout the remainder of the purposes’ information fashions.

What are the advantages of unified APIs?

Unified APIs present a number of advantages to engineering groups that have to ship and preserve dozens of integrations.

API abstractions

As an alternative of studying and interacting with the person APIs of every service, your engineering crew solely must discover ways to interface with the unified API as soon as (per class). 

This not solely makes constructing these integrations simpler and quicker but in addition helps cut back the complexity of integrations. 

Moreover, with regards to upkeep, the unified API vendor is liable for dealing with the communication with the underlying APIs, which suggests your crew does not want to fret about breaking modifications being made to one of many underlying APIs. In the end, the unified API vendor will likely be liable for updating their abstraction to make sure the combination continues to work.

Managed authentication

Unified API suppliers usually supply a managed authentication service that abstracts away the complexities of authentication with the underlying APIs, whether or not it’s through API keys or OAuth. 

If you combine with a number of APIs instantly, you need to handle the authentication course of for every one, together with managing consumer credentials and making certain safe token refresh insurance policies. 

On condition that there are lots of nuances in how every utility handles authentication, this is usually a cumbersome and error-prone activity, particularly should you’re working with numerous APIs.


By nature, the unified API makes proxy requests to its underlying APIs. As such, they may gather and analyze information in regards to the requests made to the third-party purposes. In consequence, when a request fails, the unified API supplier can log this occasion and supply particulars on the error message that was returned by the underlying API.

This logging performance might be helpful on your crew because it permits them to establish points that could be occurring with their integrations shortly. Moderately than going via the logs from a number of third-party APIs, they will depend on the unified API supplier to centralize the logging and error reporting.

With debugging errors, unified API suppliers can usually present extra detailed error messages than the underlying APIs themselves. It is because they will analyze the error response and supply extra context across the root explanation for the difficulty, which might drastically cut back the period of time spent on diagnosing errors and pace up incident response occasions.

Pre-built consumer interface

Most unified API suppliers present a pre-built interface on your clients to authenticate into an integration, saving you from constructing the configuration expertise your self.

This offloads your crew from designing the consumer expertise for every integration, which might compound by way of time financial savings when contemplating the handfuls of potential integrations you may construct on the unified API.

What are the challenges with utilizing unified APIs?

Whereas unified APIs present the advantages shared above, they’re crippled by some structural limitations that corporations are beginning to grow to be extra conscious of.

Use case limitations

On condition that unified APIs can solely summary the “shared” objects and endpoints amongst the underlying APIs, you may solely construct options which might be comparatively easy and generalizable throughout all of the integrations. That is by far the most important limitation of any unified API resolution.

Moreover, the extra purposes supported inside a unified API, the extra restricted it turns into.

abstract of unified API coverage

Supply: Paragon

Let’s stroll via some examples of those limitations.

Irreconcilable options

If it’s essential construct an integration function that entails performance or properties which might be particular to one of many integrations, that won’t be doable with a unified API.

For instance, let’s say that you just wish to combine with a number of buyer suggestions instruments through a “unified suggestions API.” If one instrument leverages a quantitative mannequin with suggestions scores between 1-10, whereas one other solely collects “unfavourable, impartial, optimistic” accompanied by “notes,” there is no such thing as a method {that a} unified API can help these use instances, as you can’t reconcile these right into a single reference.

Lacking fields

If the property it’s essential replace through the combination is simply accessible for a particular subset of the supported integrations, that property received’t be made accessible inside the unified API.

For instance, even when a number of of the underlying third-party purposes have ZIP code as a subject, so long as one doesn’t, ZIP code can’t be accessed as a property through the unified API.

Customized objects and fields

By nature, unified APIs present a set of pre-defined references to every underlying API. Nevertheless, should you introduce customized objects or fields into the combo, the unified API supplier can not anticipate what these objects or fields are. Subsequently, they can not help integrations that contain customized objects or fields.

This is usually a big blocker in case your clients require the integrations you present to help using customized objects inside the third-party purposes.

Fee limits

If you find yourself integrating with a number of APIs without delay through a unified API, you want to concentrate on the speed limits of every API and make sure that your integration logic does not exceed the bounds for anybody API. 

Because of this the logic you construct should adhere to the speed limits of the API with the bottom threshold for charge limits. Put merely, the API with the bottom charge restrict would be the limiting issue on your integration. In case you attempt to make too many requests to that API’s endpoints, your requests will begin to fail, even when the opposite APIs within the unified API can technically help that very same quantity.

To keep away from hitting charge restrict errors when making bulk requests to particular endpoints for these integrations, you have to use batching or throttling to regulate the speed of requests you ship to every API. 

So, whereas it’s nonetheless doable to work round decrease charge limits, you’ll end up constructing further complexity into your codebase so as to accommodate limitations from any one of many underlying integrations.


Unified APIs usually require that you just authorize entry to all scopes for a third-party service so as to use their API, versus permitting you to pick particular person scopes for every integration.

Because of this whenever you authenticate a consumer to make use of your integration, the consumer will likely be compelled to offer you entry to the entire information related to that third-party service, not simply the information required for the combination.

For instance, you’re constructing a CRM integration through a unified API, and the CRM has entry to gross sales, advertising and marketing, and buyer help information. When a consumer authenticates their account to make use of your integration, you’d be given entry to all three units of knowledge, even when all of your utility wants is the gross sales information.

This could elevate safety considerations on your clients. To mitigate these considerations, it is necessary to be clear along with your customers about what information you might be requesting entry to and to elucidate why you want that information clearly. 

Moreover, provided that the seller usually hosts unified APIs, you’re counting on the seller to make sure that they’ve sturdy safety measures in place to guard your customers’ information from unauthorized entry or breaches.

Opinionated information mannequin

How the seller reconciles totally different underlying APIs and reference endpoints is topic to their very own opinion. Whereas this isn’t an issue for many use instances, there will likely be occasions when they could current an abstraction that you just disagree with, or that doesn’t adhere to the anticipated habits.

Roadmap constraints

In comparison with embedded integration platforms, which offer one-on-one abstractions of each third-party API throughout many classes, unified API distributors are restricted to the classes for which they’ve constructed unified APIs. 

Whereas they will and can construct new unified APIs over time, should you ask for an integration with a class that isn’t at present supported, chances are high you’ll have to attend years for that integration to be made accessible. 

The one exception can be if the seller occurred to be constructing out a unified API for the class that the requested integration matches into. Nonetheless, given the breadth of the SaaS ecosystem and the potential classes they may help, this can not often be the case.

Workarounds: There are undoubtedly a variety of limitations that include unified APIs, which might make you suppose twice in regards to the true worth of unified APIs; the distributors that exist immediately are attempting to give you distinctive options to supply workarounds.


For instance, sure suppliers created the power to make “pass-through” requests to the underlying API. Nevertheless, immediately’s implementation remains to be very limiting and creates a subpar developer expertise.

When do you have to use a unified API

In terms of deciding whether or not a unified API is the suitable resolution on your crew, you may observe easy decision-making standards.


If the entire following are true, then it’s actually value evaluating.

  • Your integration roadmap is restricted to the classes supported by the unified API supplier.
  • Each integration use case you’ll ever have to construct might be generalized throughout each utility within the class.
  • You possibly can make investments devoted assets to constructing an infrastructure that may deal with the quantity of requests required to help your clients as you scale.
  • You don’t want your help crew to have visibility into how the combination behaves and the place it errored out, and you may have the engineering crew soar in to debug.

In case you can’t confidently say sure to the 4 factors above, you might not wish to be locked into utilizing a unified API.

As an alternative, an embedded integration platform could also be a greater resolution, as they allow you to construct a lot deeper integrations whereas offering extra complete tooling to assist streamline the combination growth course of.

The B2B SaaS integration problem

Deciding on an answer that will help you scale your SaaS product’s native integration roadmap shouldn’t be a straightforward one. You not solely have to make sure that it may well handle your use instances immediately but in addition all doable use instances your clients might request sooner or later.

Unified APIs is usually a nice resolution for delivery dozens of integrations with minimal effort, offered that the use instances your clients require are uniform throughout each integration inside a given class.

It’s a growing market with many new gamers and is actually an attention-grabbing strategy to fixing the B2B SaaS integration problem.

Be taught all about APIs, their advantages, challenges, and use instances within the complete information.



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments