Challenges

Jorge Euceda, Foxit eSign, has been with the team since they started building SDKs. Initially, a small team created multi-language SDKs and developer guides by hand using their API specifications to guide them. 

However, maintaining the SDKs and guides with each API update required too much team time.

They found that customers wanted to experience their eSign APIs to better understand the capabilities and confirm that they met their needs. During the evaluation stage, customers had to build a proof of concept to test the APIs—an effort only some were willing to make.

Foxit eSign’s business driver was to help customers move quickly from evaluation to production. 

They wanted to solve customers' main friction points while evaluating Foxit eSign’s APIs and provide confidence that building for production could be done with reliable and up-to-date SDKs in their preferred programming language.

Results

With the Foxit eSign team working on multiple projects simultaneously, it was evident that they needed to reduce the manual work of creating documentation and SDKs. They could hire more engineers and spend time getting them up to speed or choose an automated option that took away the pain altogether.

According to Jorge, a significant driver for this decision was that APIMatic’s developer portal, which includes built-in try-it-out functionality, code samples, and SDKs, came from a single source.

Closing more deals:

Providing SDKs in multiple languages gives their customers the confidence that if they have to build something custom in-house, Foxit eSign APIs can easily integrate the SDKs into their environments.

Faster time to production:

Introducing APIMatic into Foxit eSign’s API landscape has changed how their APIs are adopted. It has drastically reduced the time to get onboarded with the API, and any prospect evaluating Foxit can quickly make a contract and call their endpoint directly through the API code playground during demos.