Introduction Here at Kloudless, we often find that companies benefit from our Unified APIs’ ability to provide integration for many different services at once. By coding once and integrating with multiple APIs, developers can skip the tedious process of combing through documentation, testing, and having to manually update their code so it plays well with other APIs in the future. This last reason can be especially important to a company when they’re looking to integrate their product with a single service that only Kloudless provides connectivity to. SignNow is a recent customer who found great success by leveraging Kloudless for their service’s connectivity. Let’s take a look at how the whole thing came together: The Company SignNow is an award-winning e-signature solution known for its easy-to-use and comprehensive toolkit. SignNow allows users to e-sign documents in seconds, create complex e-signature workflows with multiple recipients and securely protect documents from unauthorized access, all while using any desktop or mobile device. The Problem Integrating SignNow with a storage service can be a complicated process due to the vast level of customizable functionality that Egnyte offers. At the time, SignNow needed a reliable way of connecting to Egnyte before potential customers went looking for alternatives. SignNow needed to find a solution that provided an all-in-one pack integration with Egnyte, DropBox, Google Drive, and Box. Needless to say, finding an ideal match in a speedy timeframe was proving difficult. Up to this point, SignNow had been building connections with outside API services as one-offs; writing code to connect to their specific service, testing connections, and ensuring that integrations still worked after changes on the API’s side were made. Aside from the time needed to become familiar with the minute details of these connectors, a major problem persisted: whenever an API would make changes to its responses or endpoints, SignNow developers had to spend considerable time re-examining docs and refactoring code to accommodate that APIs’ changes. SignNow didn’t want to spend developer time for the upkeep of a single integration, but still needed to add the Egnyte connector that their customers were requesting. On top of that, SignNow had been using automated workflows to manage some connections of their integration. The pressing need to establish an all-in-one integrations pack for their sophisticated API meant little time for a single client.