SemTech Conference talk on the key trends in open APIs as well as data on semantic APIs in 2011. API market growth, changes from SOAP to REST and XML to JSON, and new API business models. Semantic portion looks at adoption of RDF/RDFa in open APIs.
KPIs for APIs (and how API Calls are the new Web Hits, and you may be measuri...John Musser
How do you measure API success? What KPIs do APIs need? What mistakes should I avoid? Find out what you should, and shouldn't, be measuring as part of your API program in this Business of APIs Conference NYC talk. Dive into a breadth of API metrics, the 6 keys to better API metrics, and the traps to beware of (the important do's and don'ts). Also real-world API case studies show who measures what.
6 Reasons Why APIs Are Reshaping Your BusinessFabernovel
A study on APIs to demonstrate the advantages of APIs for businesses in terms of scalability, flexibility, business development, product development, supply chain management...
SemTech Conference talk on the key trends in open APIs as well as data on semantic APIs in 2011. API market growth, changes from SOAP to REST and XML to JSON, and new API business models. Semantic portion looks at adoption of RDF/RDFa in open APIs.
KPIs for APIs (and how API Calls are the new Web Hits, and you may be measuri...John Musser
How do you measure API success? What KPIs do APIs need? What mistakes should I avoid? Find out what you should, and shouldn't, be measuring as part of your API program in this Business of APIs Conference NYC talk. Dive into a breadth of API metrics, the 6 keys to better API metrics, and the traps to beware of (the important do's and don'ts). Also real-world API case studies show who measures what.
6 Reasons Why APIs Are Reshaping Your BusinessFabernovel
A study on APIs to demonstrate the advantages of APIs for businesses in terms of scalability, flexibility, business development, product development, supply chain management...
My presentation from Nordic APIs 2014 in Stockholm, Sweden.
How can the architecture of one API platform look like? How can you break down things to make this challenge easier?
APIs are everywhere today and can be a great building block of modern applications. But all too often APIs are not truly great. Rather than love your API, developers curse it. How can you avoid that fate? In this session we'll look at the most common mistakes API providers make and you can avoid making them too. Do you offer a bad developer experience (DX)? Poor, inconsistent API design? Unreliable services? This talk is a deep dive on not just what to avoid but what to do instead. And you'll leave knowing how to get developers to love your API, not hate it.
Real World API Business Models That Worked
Mark Boyd, Writer, ProgrammableWeb
What business revenue models are most successful for API providers seeking to build active third-party developer communities? How much can an API act to leverage revenue growth and market share, and what timeline for success is realistic? This presentation goes beyond the theory to share some initial data on what businesses are experiencing when implementing an API strategy.
This presentation summarizes the critical success factors from 15 API business case studies including:
- Type of business model used and revenue-share data against cost estimations
- What developer engagement strategies grew API usage the fastest
- What factors reduced churn rate amongst third-party developers
- Developer onboarding timeframe
- What factors influenced internal support for an API strategy
Don't let broken APIs get you down. This talk looks at how API Ops, a new wave in DevOps, lets you design, build, test and release APIs more rapidly, frequently and reliably. Whether you're building public facing APIs, internal APIs, or building a microservices architecture, API Ops can help. We look at how the whole API lifecycle, the API tools, and the API teams all fit together to build better APIs and services.
Be My API How to Implement an API Strategy Everyone will Love CA API Management
Mike Amundsen,
Principal API Architect, Layer 7 Technologies
Mike is the author of Building Hypermedia APIs with HTML5 & Node and is a regular speaker at leading industry events on the subject of API design, Web application development and cloud computing.
Learn how to create and publish APIs that will help your business thrive and grow
February 7, 2013
9am PST | 12pm EST
Building great APIs is about more than just design; it requires detailed, thoughtful execution. Your API strategy needs to meet the business requirements of your organization but it must also be flexible enough to meet your developer community’s diverse needs. This webinar with Mike Amundsen, Layer 7's Principal API Architect, will examine the key foundational elements necessary for a solid API implementation strategy.
You Will Learn
Align API design with business goals
Architect flexible and robust APIs that are developer-accessible
Design for multiple client platforms (Web, mobile and cloud)
Implement USE methodology, versioning, reusability and hypermedia
Address issues around security, identity, social integration, reliability and scalability
Presented By
What is it that turns an ordinary API into a great API? This talk from OSCON 2012 outlines the 5 "keys" to having a great API. Lots of examples from successful real-world APIs are used to highlight what matters. Also, this talk reveals 7 lesser known but very important "API secrets".
Extend your legacy SOA/ESB infrastructure to Mobile & IoT
This webinar recording provides a use-case driven discussion around appropriate use of existing middleware infrastructure as well as its shortcomings. It dives deep into how APIs can not only complement an ESB or SOA infrastructure but also fill existing gaps.
Watch this webinar recording to learn about:
- Strengths and weaknesses of your existing ESB/SOA infrastructure
- Architecture strategy: extend and add value to legacy middleware with APIs
- Integration / API use cases in Retail, Manufacturing and Telecom
- The API360 approach to digital strategy
Sachin Agarwal, SOA Software VP of Product Marketing, explains the frenzy around the mass development and adoption of APIs. In this presentation, he describes the business and technology implications of developing an API stratgy.
My presentation from Nordic APIs 2014 in Stockholm, Sweden.
How can the architecture of one API platform look like? How can you break down things to make this challenge easier?
APIs are everywhere today and can be a great building block of modern applications. But all too often APIs are not truly great. Rather than love your API, developers curse it. How can you avoid that fate? In this session we'll look at the most common mistakes API providers make and you can avoid making them too. Do you offer a bad developer experience (DX)? Poor, inconsistent API design? Unreliable services? This talk is a deep dive on not just what to avoid but what to do instead. And you'll leave knowing how to get developers to love your API, not hate it.
Real World API Business Models That Worked
Mark Boyd, Writer, ProgrammableWeb
What business revenue models are most successful for API providers seeking to build active third-party developer communities? How much can an API act to leverage revenue growth and market share, and what timeline for success is realistic? This presentation goes beyond the theory to share some initial data on what businesses are experiencing when implementing an API strategy.
This presentation summarizes the critical success factors from 15 API business case studies including:
- Type of business model used and revenue-share data against cost estimations
- What developer engagement strategies grew API usage the fastest
- What factors reduced churn rate amongst third-party developers
- Developer onboarding timeframe
- What factors influenced internal support for an API strategy
Don't let broken APIs get you down. This talk looks at how API Ops, a new wave in DevOps, lets you design, build, test and release APIs more rapidly, frequently and reliably. Whether you're building public facing APIs, internal APIs, or building a microservices architecture, API Ops can help. We look at how the whole API lifecycle, the API tools, and the API teams all fit together to build better APIs and services.
Be My API How to Implement an API Strategy Everyone will Love CA API Management
Mike Amundsen,
Principal API Architect, Layer 7 Technologies
Mike is the author of Building Hypermedia APIs with HTML5 & Node and is a regular speaker at leading industry events on the subject of API design, Web application development and cloud computing.
Learn how to create and publish APIs that will help your business thrive and grow
February 7, 2013
9am PST | 12pm EST
Building great APIs is about more than just design; it requires detailed, thoughtful execution. Your API strategy needs to meet the business requirements of your organization but it must also be flexible enough to meet your developer community’s diverse needs. This webinar with Mike Amundsen, Layer 7's Principal API Architect, will examine the key foundational elements necessary for a solid API implementation strategy.
You Will Learn
Align API design with business goals
Architect flexible and robust APIs that are developer-accessible
Design for multiple client platforms (Web, mobile and cloud)
Implement USE methodology, versioning, reusability and hypermedia
Address issues around security, identity, social integration, reliability and scalability
Presented By
What is it that turns an ordinary API into a great API? This talk from OSCON 2012 outlines the 5 "keys" to having a great API. Lots of examples from successful real-world APIs are used to highlight what matters. Also, this talk reveals 7 lesser known but very important "API secrets".
Extend your legacy SOA/ESB infrastructure to Mobile & IoT
This webinar recording provides a use-case driven discussion around appropriate use of existing middleware infrastructure as well as its shortcomings. It dives deep into how APIs can not only complement an ESB or SOA infrastructure but also fill existing gaps.
Watch this webinar recording to learn about:
- Strengths and weaknesses of your existing ESB/SOA infrastructure
- Architecture strategy: extend and add value to legacy middleware with APIs
- Integration / API use cases in Retail, Manufacturing and Telecom
- The API360 approach to digital strategy
Sachin Agarwal, SOA Software VP of Product Marketing, explains the frenzy around the mass development and adoption of APIs. In this presentation, he describes the business and technology implications of developing an API stratgy.
The slideset used to conduct an introduction/tutorial
on DBpedia use cases, concepts and implementation
aspects held during the DBpedia community meeting
in Dublin on the 9th of February 2015.
(slide creators: M. Ackermann, M. Freudenberg
additional presenter: Ali Ismayilov)
How to Develop APIs - Importance, Types, Tools, Terminology, and Best Practic...Techugo Inc
Wondering how to develop APIs? And want to perform API integration for your business? Then you must know everything about API development. Also, get top-notch API solutions from the best API app development company. So, contact us to build an API for your business application right now! Visit: https://www.techugo.com/blog/how-to-develop-apis-importance-types-tools-terminology-and-best-practices/
Guide To API Development – Cost, Importance, Types, Tools, Terminology, and B...Techugo
Building an API is the foundation for any apps dealing with data or requiring communication between two goods or services. A collection of guidelines or standards known as an API allows the software to use the capabilities of another app. For example, when you choose “Connect with Facebook,” Candy Crush immediately gets your Facebook account information. It can access the Facebook server using API integration, saving you the trouble of manually entering your information.
API (Application Programming Interface) development has become an essential aspect of modern software development. It allows different applications to interact with each other, exchange data and provide services seamlessly. To develop a successful API, you need to follow some crucial steps like defining API requirements, choosing the right protocol, designing the API interface, and testing it thoroughly. Furthermore, you should consider the security aspects of API development, including authentication, authorization, and encryption. Finally, you should document your API comprehensively, providing clear instructions for developers to use and integrate it with their applications.
The API SlideShare for Bankers and Fintech ExecutivesMX
In this guidebook we’ll walk you through what you need to know about why APIs matter in today’s banking environment. First we’ll discuss the basics, then we’ll dive into details about what specific features you should look for when using a fintech provider’s API or when building your own.
Also download the official guidebook version of this presentation:
https://www.mx.com/api-guidebook
What are ap is, how do they work, and why are they beneficial to developers a...Shelly Megan
We’re living in an API centric world Many of our daily activities revolve around APIs, and most of us are not even aware of it! You can instantly browse information on the current weather conditions.
Modern APIs: The Non-Technical User’s Guide | The Enterprise WorldTEWMAGAZINE
A Modern APIs (Application Programming Interface) is a software interface that allows two applications to communicate with each other. APIs have been around for quite a while.
Securely expose protected resources as ap is with app42 api gatewayZuaib
App42 API Gateway is a comprehensive & battle-tested API Management solution that enables companies of all sizes and even individuals to launch APIs in minutes.
Understanding API Architectures: Web API vs. Minimal API – An In-Depth Compar...Polyxer Systems
In this comprehensive guide learn the distinctions between Web API & Minimal API for your project understanding and get detailed insights on framework differences, benefits & limits.
Cloud Elements | State of API Integration Report 2018Cloud Elements
The State of API Integration 2018 Report contains a full breakdown on the current state of the API industry, a look at what’s trending and why, and a look ahead to where we believe API integration is headed. This year’s report builds on observations from 2017, with the help of over 400 API enthusiasts who took the State of API Integration Survey at the end of last year.
API Development has become one of the most often used phrases among tech enthusiasts and any organization developing web applications worldwide.
In today’s environment, API is crucial to businesses and, by extension, to the economy as a whole.
APIs are everywhere and are regularly used by regular people.
DFY Suite is an all-in-one social syndication platform that makes it easy to syndicate your content to high-quality social media platforms and manage your social syndication campaigns.
Syndicate your content to a wide range of social media platforms, including Facebook, Twitter, LinkedIn, Pinterest, and more.
Schedule your social media posts in advance.
Track your social media results.
Interact with your audience on social media.
DFY Suite is perfect for businesses of all sizes who want to increase their website traffic, improve their website authority, and rank higher in search engine results pages.
6 Best OpenAPI Documentation Tools that You must KnowMars Devs
Unless you re alone utilizing the API, you should thoroughly document it But manually would be tedious. But which is the best? To solve your dilemma, MarsDevs will highlight some of the best API documentation tools available to make documentation simpler! Let’s start with the basics.
Click here to know more: https://www.marsdevs.com/blogs/6-best-openapi-documentation-tools
apidays Australia 2023 - API Strategy In The Era Of Generative AI,Shreshta Sh...apidays
apidays Australia 2023 - Platforms, Products, and People: The Power of APIs
October 11 & 12, 2023
https://www.apidays.global/australia/
API Strategy In The Era Of Generative AI
Shreshta Shyamsundar, Distinguished Technologist at Infosys
------
Check out our conferences at https://www.apidays.global/
Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8
Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io
Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/
Similar to ProgrammableWeb's eSignature API Research Report (20)
Building A Business-Facing Mobile Developer CommunityProgrammableWeb
Building A Business-Facing Mobile Developer Community
Andy Jones, Technical Director EMEA, SOA Software
The proliferation of mobile apps has led to increased interaction between two previously separate groups: mobile app developers and corporate managers of enterprise systems. The API is the connector. Creating a developer community that serves your mobile strategy is a challenge on both technical and business levels. Mobile developers are essentially business partners, even if they do not see themselves as such and successfully engaging them will be key to delivering value from the API. In this presentation, we will discuss some proven practices that can ensure that businesses make the best use of APIs to extend themselves into the mobile realm:
Offering business capabilities that are important to partners
Tailoring APIs to each partner
Managing partner registration with workflow
Allowing partners to monitor and analyze their own API usage
Accelerating the process of externalizing applications
Securing the apps
Mediating transports protocols
Mark Boyd, Writer, ProgrammableWeb
APIs are increasingly being used by city authorities around the world to connect and share their data. This presentation describes five case studies of how third party developers are leveraging the API advantage to create viable business models. The presentation will summarize case studies across public transport, open 311, urban planning, citizen engagement, and crime prevention. The presentation will document a success matrix, describing the common factors that are making it possible for third party developers to create viable business models by leveraging smart city APIs.
Jack Thorley, Software Developer, Esendex
Jack Thorley, software developer at Esendex, will be demonstrating how easy it is to get your software s peaking SMS using Esendex’s API. Jack will talk you through what Esendex’s API can do, offer tips, best practices and some great ideas on how to use SMS to revolutionise your business communications. Bring your laptop along if you’d like to try it out for yourself.
David Johnston, Managing Director, Decentralized Application Funds
Using the power of bitcoin for payments and flexible open source platforms we can reduce the friction in today's API infrastructure and finally connect the programable web to programable money.
Simon Phipps, President, Open Source Initiative
Open source is not about free stuff. It's a way of granting permission in advance so that innovation can happen without obstruction and so loose-knit communities can collaborate freely. As such, it's more important than ever in an age of APIs, devices and distributed web infrastructure.
This session will:
Explain the dynamics of open source licensing
Consider the relative merits of licensing "strengths" for IoT
Discuss the challenges of software patents to APIs and open collaboration.
Your API Deserves More Respect: Make It A ProductProgrammableWeb
Your API Deserves More Respect: Make It A Product
Andrew Seward, Technical Product Manager, Esendex
Your API is a product in its own right - it has its own customer base, its own target market, customer journeys, interface considerations, profit margins, features, bugs, strengths and weaknesses. That idea is an easy sell for most of us here, but how do you get your whole company on board, particularly when many of your colleagues haven't heard of APIs before? I will share my experience of changing how Esendex thinks about and approaches its API - where we were with our API and how we went about raising it to be our main product. What worked, what didn't, what problems we encountered, how we overcame them and what we're still trying to figure out. We also want to hear from you and your experiences so we can all benefit from the conclusions you've drawn.
Why API Security Is More Complicated Than You Think (and Why It’s Your #1 Pri...ProgrammableWeb
Why API Security Is More Complicated Than You Think (and Why It’s Your #1 Priority)
David Berlind, Editor-in-Chief, ProgrammableWeb
In the last year, the users of various social media services have had their accounts compromised due to API security related issues. ProgrammableWeb’s investigations into these transgressions reveals a degree of hacker sophistication that could never have been anticipated. The attacks were layered and complicated and one can only guess at the final objectives (but we have our hunches). In this presentation, ProgrammableWeb editor-in-chief reveals the sophistication of these attacks with a step-by-step walkthrough of what the perpetrators did and then offers a a layered-security prescription for preventing your organization, APIs, and applications from being similarly compromised.
Zohar Babin, Senior Director, Ecosystem and Community, Kaltura
While a great many API enthusiasts will tell you that achieving API utopia means re-architecting all of your applications (Web, mobile, or otherwise) on top of the same APIs that you make available to external developers, very few organizations have actually succeeded at doing what's necessary; turning their infrastructures inside out. Many organizations can't envision having the time, patience, or resources to fly a plane while the wings are being ripped-off and reinstalled. But open source video platform provider Kaltura pulled it off. As a result, Kaltura's core infrastructure -- back end servers, core applications, etc. --- rely on the same APIs that front-facing partners' applications rely on. The result was a highly flexible future-proof platform that enables customers, partners, developers and startups to rapidly extend the platform with innovative implementations that continuously push the limits of what Kaltura can do. In this presentation, Kaltura willl cover the principles of what makes a great, dogfoodable API, how to make it resilient, future-proof and yet backward compatible, and most importantly how to enable and support customers and partners looking to extend an API platform.
HTTP APIs as first class procedures in your language: cutting out SDK complex...ProgrammableWeb
Andy Bennett, Founder, Knodium
This talk looks at how to make an HTTP API available as a self-contained procedure or function, just like any other library or API code that you might be used to using or importing into your programs.
Whether you're implementing an SDK for your own API or just trying to bind to an adhoc API that you want to use, this talk will cover how to do it in an elegant and simple way without lots of adhoc code duplication, needless boilerplate or irrelevant detail.
Intro To Orchestrate DBaaS: A Single API For Key/Value, Search, Graph, And Ev...ProgrammableWeb
Ian Plosker, CTO and Co-founder, Orchestrate
Learn how to get the most out of all of Orchestrate's features. We'll cover the API, the data model, how to query from the web, from a shell and a lot more. Each of the major API endpoints will be covered along with advanced topics like consistency, concurrency, and application placement.
Case Study: A Real-World Implementation Of Linked DataProgrammableWeb
Dimitri van Hees, Technical Architect/Data Specialist, Freshheads BV
Learn how one organization put Linked Data to work for it by adding a sixth star --- using APIs --- to Sir Tim Berners-Lee’s 5-Star Scale for implementing Linked Open Data. This session includes an introduction to Linked Open Data, Linked Closed Data, and Berners-Lee's 5 star scale and do a step-by-step walk-through of a successful implementation. It will include a frank discussion regarding the technical and organizational challenges encountered with a real-world Linked Data project and how those challenges were overcome. In this session, you will not only learn how to think about Linked Data APIs in real world terms, but also how to "sell" it to the organization." If you are attending this presentation, you may also want to attend Markus Lanthaler's presentation on Why and How to Optimize Your Data Architecture for an Integrated Future.
Pivoting Your Business From Product To PlatformProgrammableWeb
Marco Herbst, CEO, Evercam.io
The reason software can be so profitable is that nothing scales as well as code. Even before the Internet (back in the days of disk-based software distribution), the cost of manufacturing software were nil when compared to manufacturing and distributing a manufactured product. But what if a product company --- maybe your company --- could become a code company and scale like one too? Formerly a product company, Evercam saw in its product a chance to become a code company instead -- a chance to pivot from a product to a platform. In this session, Evercam founder Marco Herbst tells the story of how his product-first company converted itself into an API-first company instead. The company took on huge risk as it massively transformed its business, its offerings, and its customer base. Herbst will look back on that transition, explain the motivations for going all-platform, and draw some lessons for anybody looking to pivot a product business into an API-based platform business (or to build a new platform business from scratch).
Exploring UK Bus And Train Data With TransportAPIProgrammableWeb
Harry Wood, Software Engineer, TransportAPI.com
TransportAPI provides UK public transport data with live and timetable information for bus, train, and tube, available to developers through an easy to use API. UK transport data is a complex and shifting landscape. In this workshop we'll talk through some of the challenges we're facing, and how we're working to solve them to take the pain away for developers (inviting more feedback and suggestions from the API community!). We'll look at the resulting API and a tour of the different data offered, some examples of how it might be used, and some bespoke work we're doing for clients.
- See more at: http://www.apiconuk.com/apiconukschedule#sthash.gdIvEBWy.dpuf
DDD (Delight-Driven Development) Of APIs With RAMLProgrammableWeb
Uri Sarid, CTO, MuleSoft
API-first development is an approach in which the APIs between systems are designed and validated without requiring any implementation, and then form the requirements for implementing the API provider and consumer(s). RAML, the RESTful API Modeling Language (http://raml.org), is a relatively new open format for specifying web APIs. It’s distinguished by focusing on writeability as well as readability, on minimality and elegance, and on enabling and encouraging reusability and consistency of APIs. This makes RAML an ideal basis for API-first development. In particular, RAML is a fitting foundation for API initiatives whose success is predicated on delighting their customers: the developers who will be consuming the API. In this talk I’ll introduce RAML, API-first development, API design, and some tools that not only produce delightful APIs but are also delightful on their own. I hope you find this useful whether you’re just documenting existing APIs, looking to improve your APIs and their lifecycle, or embarking on new API initiatives.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
3. ProgrammableWeb Report: APIs for eSignature Products 1
APIs for e-Signature Products:
Introduction
In the last few years, e-signature products have helped to automate a tedious, time-consuming, costly and
very common task: signing documents. The need to circulate physical documents and obtain signatures on
them creates delays and the potential for error in many business processes, particularly sales. E-signature
products put the process online, and now APIs are enabling companies to integrate the electronic signature
process directly into their workflow.
In this report we present the results of our evaluation of seven e-signature services:
Adobe EchoSign RightSignature
Barracuda SignNow Sertifi eSignature
DocuSign Silanis e-Sign Live
HelloSign
Six of the services have REST APIs, including two that also have SOAP, and one of the services is SOAP-only.
It’s hard to look closely at these products and not conclude that DocuSign is in a class by itself.
The DocuSign API is far more comprehensive than the rest. The documentation, sample code, tools and
community are superior to that of all the other products. And no other product came close in terms of
support for multiple languages, particularly with respect to sample code.
HelloSign and Sertifi e-Sign Live are also strong contenders. HelloSign, in particular, was very easy to get up
and running in our tests and had excellent documentation. Sertifi e-Sign Live, the one SOAP-only product
we tested, was also easy to work with. There were problems with its documentation, but, due to the nature of
SOAP, these issues weren’t as thorny as they would have been with REST.
The others—Adobe EchoSign, Barracuda SignNow, RightSignature and Silanis e-Sign Live—were all
disappointing in tests. While each has some merits, their documentation was brief and/or confusing. None
of them had adequate sample code, although some had SDKs and samples for .NET and/or Java. Still, if you
want to use these products by programming the APIs directly, we found all of them to be severely lacking in
what we think makes for a great API and developer experience.
We evaluated the products from a programmer’s perspective, focusing on features that would help a
company to use the API quickly and effectively. We considered the availability of evaluation accounts for
programming tests, the quality and availability of documentation and sample code, tools for programmers
and community for support. A more extensive discussion of our testing philosophy follows in the “What
Matters to Us” section.
4. 2 ProgrammableWeb Report: APIs for eSignature Products
What do these products do?
The seven e-signature products we tested are cloud services that at their most basic level provide two main
capabilities:
• They collect electronic signatures in some form from a user and incorporate the signatures into a
document
• They manage workflow by routing the document for review and/or signature from other users,
based on rules set by the developer and/or administrator
Some of the products we tested go further—providing forms control, for example—but signatures and
workflow are at the core of all the products. All of the services we tested have an interactive product that allows
users to perform basic e-signature functions with no programming. But they all also provide an API that allows
organizations to build these functions into their own applications.
It is important to note that there are differentiating factors among these products that are not evident at all in
the APIs. Indeed, the API serves in large part to hide implementation differences from the programmer.
REST vs. SOAP, JSON vs. XML
As in the rest of the world of APIs, SOAP is declining as a technique among e-signature products, and REST
is ascendant. The same is true, to a lesser extent, of JSON (on the rise) and XML (going out of favor).
One of the products we tested, Sertifi eSignature, has only a SOAP API. Barracuda SignNow, HelloSign,
RightSignature and Silanis e-Sign Live have only a REST API. DocuSign and Adobe EchoSign have both. In
the case of DocuSign and EchoSign, we tested only the REST APIs. Both DocuSign and Adobe claim that
their SOAP and REST APIs provide equivalent functionality.
API Types
Adobe
Echo Sign
Barracuda
SignNow
DocuSign HelloSign Right
Signature
Sertifi
eSignature
Silanis
e-Sign
Live
REST 4 4 4 4 4 4
SOAP 4 4 4
Request and response data is another case where it’s easy to see which way the wind blows. Sertifi
eSignature is, by nature of using SOAP, reliant on XML for both request and response data. The REST
products support JSON in nearly all cases, although some also support XML.
E-signatures vs. digital signatures
A common point of confusion, sometimes even in vendor marketing, is the distinction between e-signatures
and digital signatures.
E-signatures, which are the core function of the products we evaluated, are a digital analog of a signature
that a person signs with a pen on paper. Sometimes it is a literal graphical image of the person’s signature,
but it can also be simply a digital statement of some kind that a specific person signed a document.
5. ProgrammableWeb Report: APIs for eSignature Products 3
The United States and many other countries have adapted laws to make these sorts of signatures
acceptable in a wide variety of cases, such as signing contracts, government forms and deeds to property.
E-signatures are not a particularly strong method of authentication, but then neither is a signature written
with pen on paper.
Digital signatures are data created to strongly connect a block of data with a particular identity. For
instance, the digital signature of an e-mail message can be used to prove to the recipient that the message
did, in fact, come from the apparent sender and that it was not modified after it was signed. There is a role
for digital signatures in e-signature products, but most products do not bother with them and instead use
simpler techniques to identify documents and verify document integrity.
Pre-built integrations
It may be hard to believe, but not everyone wants (or is able) to write code. Fortunately, for these situations,
each of the products we tested provides pre-built integrations with other cloud services.
At the simplest level, these integrations allow the e-signature service to read or write documents on another
service—say, DropBox. Business applications like Salesforce and Microsoft Dynamics CRM are obvious targets
for e-signing because contracts and other agreements are so central to their operation, and several of the
products do work specifically with them. DocuSign and Microsoft also recently announced a partnership to
make DocuSign available within Office 365. We did not study these integrations as part of our evaluation, but
for many companies, the integrations will be an easier solution than writing their own code.
How we compared the products and APIs
In tests, we approached each of these services as a developer would.
We checked the developer facilities at each. Is it easy to find documentation for the API? Can you get an
eval account? Can you actually test the APIs and the entire environment without signing up? How good is
developer support and community? Is quality sample code available?
We also tested some of the APIs for each service to get a feel for working with them. We looked at each
API and the API set as a whole for design quality. We checked with the vendor and community to see if the
company has policies for adding and retiring API features.
One can argue that any platform that can make HTTP calls can support any of these products, but that’s
a pretty low standard. (In fact, for SOAP, not even HTTP is necessarily required.) We expect more from a
development system than just an API specification. Indeed, an API spec just isn’t enough in a world in
which numerous languages and operating systems are used to access APIs. Still, some of the products
provide a higher level of support to a broader range of programming platforms: PHP, Java, .NET, Ruby and
Python are some of the platforms and languages we encountered.
It’s important to make a distinction between what an e-signature provider can do and what is made
available via its API. This report is focused on the API because we believe this is how the e-signature
industry will continue to expand—through both internal and developer usage of provider APIs to help
automate and integrate e-signatures into business workflows.
6. 4 ProgrammableWeb Report: APIs for eSignature Products
Warning: Features may shift as you work on them
We want to make it clear that this report represents a snapshot in time—and we all know how much
things can change from one minute to the next. After all, this is the cloud we’re talking about: Features,
documentation and anything else may change at any time. Good companies provide clear and advance
notice of such changes, but it’s not like you have to run apt-get for the changes to happen.
Several vendors told us that important changes in the APIs and documentation would be rolled out around
the time of our evaluation. We have noted these where applicable.
What matters to us
We prepared this analysis with the interests of programmers in mind—and web API programmers in
particular. To that end, we focused our analysis on the breadth of the API itself and on the features and
functions that help web API programmers do their work more efficiently.
These included:
• Documentation: We consider great documentation to be very important. Documentation should
explain in detail the API, its methods, the JSON or XML schema, and other important factors.
• Code samples: The vendor should offer lots of code samples in the major languages used to write
web and mobile apps: JavaScript, PHP, Python, Ruby, Java, Objective-C, and C# and other .Net
languages. It should also show how to use cURL or some other interactive test tool for the API’s
endpoints, except in the case where SDKs are the primary method of access.
• Interactive consoles: Interactive consoles, sometimes called playgrounds, are good for developers.
Many API providers, including two in this comparison, offer Web-based tools that allow a developer to
test the many different types of calls and methods interactively using forms and wizards.
We think it’s important for developers to be able to at least minimally poke at an API in some way without
having to go through any sort of lengthy registration or paying a fee. It’s fine if that access is provided using
only sample data, and we also think it’s fair that vendors take special measures—such as watermarking
documents created with eval accounts—to prevent the documents from being used for production. But
taking the API for an actual spin is an important part of the discovery and evaluation process, and API
providers need to know that developers are more likely to go with a company that offers this capability.
• SDKs and libraries: SDKs and/or libraries for the languages listed above (including support for
Node.js) are a huge plus.
Web APIs began with SOAP and XML, but these have gone out of favor in recent times. The new de-facto
standard for web APIs is to use REST and JSON. These are considerably simpler than SOAP and XML.
Some may argue that SOAP and XML are more versatile, but the market has spoken. Two of the products
we evaluated—Adobe EchoSign and DocuSign—offer both SOAP/XML and REST/JSON; all the customer
action is with the latter, according to vendors we spoke to while conducting this study.
If an SDK is the main programming interface, then these issues may not be as important. For example,
while it isn’t an e-signature service, Evernote is an example of an API that doesn’t even support REST/
JSON. That hardly matters because all of its developers go through SDKs. (Evernote uses Apache Thrift to
generate these SDKs.)
7. ProgrammableWeb Report: APIs for eSignature Products 5
How the products stack up
Adobe EchoSign
Product Home Page:
https://www.echosign.adobe.com/
Developer Portal:
https://www.echosign.adobe.com/en/products/echosign-api-dev-center.html
You’ve heard of Adobe, and that counts for something. EchoSign has some good features and, by
the standards of this market segment, is a mature product. Adobe has not, however, taken the time
to create what developers need to use EchoSign well.
Developers can sign up for a free developer account at the developer portal. There are no
constraints on time or number of documents. But documents are watermarked to prevent production
use. Adobe makes it easy to get an API key from the Account tab on the Developer portal. EchoSign
has both REST and SOAP APIs, and both request and response data can be in JSON or XML.
EchoSign has good audit trail functionality. Exposing the feature through the API allows companies
to ensure that transactions are archived, for legal and other compliance reasons.
There are three different types of keys that can be used with EchoSign: user-specific keys,
organization-specific keys and application-specific keys. This adds some programming complexity,
but it could provide useful flexibility for keeping billing organized. A good reporting system could
accomplish the same thing, but using keys automatically separates charges. Only Adobe has this
capability automatically, although other vendors would probably make arrangements for multiple
keys if you asked for them.
Like DocuSign, EchoSign includes a tool, called Try It Out, for testing APIs interactively. However,
while DocuSign’s API Explorer includes a developer-friendly form for populating JSON-based
requests, EchoSign’s tool requires hand-coding of literals into a single field that includes all of the
JSON (which awkwardly wraps when the lines get too long, interfering with readability). The former
approach is better for entering name/value pairs, while the latter is better for developers who want to
cut and paste their JSON from some other editor or app.
EchoSign’s interactive interface included one nice touch: It lists all of the HTTP error codes that the
API could return, as well as what each means.
The really unfortunate problem with EchoSign is the dearth of help for REST developers. The
documentation consists of the API Explorer itself and a PDF with fewer than five pages of content.
The only sample code provided for the REST API is in Java.
Documentation for the SOAP API is better, but still nothing special. There is one set of trivial SOAP
code samples for C#, Perl, PHP, Ruby and Java. Adobe calls this set of sample programs an “SDK,”
but it’s not worthy of the acronym.
In addition, Adobe has not yet created any developer community features. Developer support is
handled through standard Adobe support, and there is some EchoSign action at StackOverflow.
However, there are no organized developer forums for EchoSign. This places it on par with most of
the other products. Only DocuSign and Sertifi put any effort into providing dedicated communities for
developers.
8. 6 ProgrammableWeb Report: APIs for eSignature Products
Barracuda SignNow
Product Home Page:
https://signnow.com/
Developer Portal:
http://developers.signnow.com/
SignNow from Barracuda—best known for its security products but diversifying rapidly—looked simple
to us at first glance. How wrong we were. To put it generously, SignNow is still under construction.
On our own, we were unable to make a single successful call with the SignNow API. The root cause,
as it were, was insufficient and confusing documentation, and the absence of community features
didn’t help.
Very late in testing, a Ruby SDK and Ruby library for OAuth 2 authentication appeared on the site,
but for the rest of the time, Barracuda provided only one example program (written in C). The API
documentation itself includes a cURL sample command. We really would have preferred PHP or
JavaScript, but it might not have made a difference.
Late in the production of this report, Barracuda notified us of features that were available but
undocumented. The company offered to send us the documentation and put it online, but our
deadline for testing the APIs had passed. As we’ve already said, these are cloud services, and
features in any of them can change on a moment’s notice. Readers of this report are encouraged to
double-check with the API providers to see what, if anything, has changed.
Applications written to take advantage of SignNow’s e-signature services use a basic authentication
call (username:password) in order to retrieve a bearer access token. This token is then used for
subsequent commands.
SignNow appears to be the only product in this comparison that supports three-legged OAuth
authentication, which would allow a third-party authentication.
9. ProgrammableWeb Report: APIs for eSignature Products 7
DocuSign
Product Home Page:
https://www.docusign.com/
Developer Portal:
http://www.docusign.com/developer-center
To put at least one difference between DocuSign and the other products in perspective, one need
only compare API calls: With the exception of Sertifi eSignature, the other products reviewed in this
report have about 10 to 20 API calls. DocuSign has about 130. You can see in the section on the
API feature set that this translates into access to a large variety of capabilities that the other products
simply can’t offer.
Some examples of features accessible through the API that are unavailable elsewhere are:
• Offline Signing: Going from an offline to online scenario (that is, start an envelope offline, build it
and configure it to upload once back online)
• Formula Tabs: This feature provides the ability to reference other fields and do basic calculations
(+, -, *, /)
• Customized branding: DocuSign gives companies the ability to customize the signing
experience to a greater degree than other products
• Authentication abundance: DocuSign has the widest variety of options for authentication of
signers, including digital certificates, voice phone call and geolocation
The benefits of all these features are clear: Developers integrating e-signing functionality into their
software have more possibilities with DocuSign. Also, in many cases, the APIs are not new signing
features but ancillary features that developers would otherwise have to implement on their own or,
more likely, rely on from an outside product like Acrobat. These include numerous page and form
manipulation features, such as manipulating fields, and even the ability to rotate a page image from
a document.
Like Adobe EchoSign, DocuSign has both SOAP and REST APIs. The REST APIs support JSON and
XML for both request and response. The SOAP APIs, like all SOAP APIs, support only XML.
DocuSign’s documentation and developer tools are first-rate. Indeed, they are head-and-shoulders
above those of the other products we tested. As with Adobe EchoSign, DocuSign offers an API test
tool that enables developers to interactively fill in values and execute a call. With that said, DocuSign
API Explorer has some clear advantages over Adobe’s RESTTry It Out tool. The main one is that
DocuSign API Explorer opens up fields in which developers can enter values in a JSON record; with
EchoSign, you have to manually write JSON record constants.
Where DocuSign clearly stands out is in documentation and sample code. The other products
we tested provide very little in the way of sample code, and usually in just one or two languages.
DocuSign’s API WalkThroughs provide illustrations of the API flow and sample code for nine
common scenarios, including Request Signature via Template, Get Envelope Recipient Status and
Get Document List Download Docs. Sample code is provided in PHP, JavaScript, Java, C#, Python
and Objective-C. This will save many a developer a lot of time getting up and running.
Obtaining a development account and an API key for DocuSign is easy: Simply sign up for a free
developer eval account, and you will get an API username and account ID. A demo integrator key is
then just a click away.
10. 8 ProgrammableWeb Report: APIs for eSignature Products
DocuSign has no formal community on its site, instead sending developers to StackOverflow, a
more general-interest development community where representatives from DocuSign monitor the
activity. This seems to work well, especially if you have other development community interests that
are covered by StackOverflow.
DocuSign does what it can to make its API quickly accessible to developers, but the breadth of
the DocuSign API does make it more complicated. If it weren’t for the sample code, it would be
more complicated to get that first app up and running. DocuSign’s sample code helps. But a longer
learning curve is the price that’s paid for the DocuSign API’s superior feature set.
We did run into some problems with our DocuSign testing. We ran into cURL SSL Cert errors,
probably because DocuSign had to add a client PublicKey to its server table and enable Certificate-
Based Authentication for our DocuSign account. We weren’t able to get this resolved before testing
was complete. This problem may not happen with paid accounts.
We also had trouble using JSON in the X-DocuSign-Authentication header for API authentication.
XML worked for us. Due to time limitations, we didn’t pursue this as far as we might have, and
threads on StackOverflow indicate that others use JSON with no problem.
11. ProgrammableWeb Report: APIs for eSignature Products 9
HelloSign
Product Home Page:
https://www.hellosign.com/
Developer Portal:
https://www.hellosign.com/api/gettingStarted
HelloSign was the easiest product we tested in terms of getting up and running quickly with APIs.
The documentation is well-designed and readable. All calls include cURL command examples with
thorough JSON enumerations. We also were able to use the Postman REST client for testing.
We got an API key from HelloSign, but, surprisingly, the key wasn’t strictly
necessary—you can make all calls with just username:password. The company says it is attempting to
move developers away from this model and toward using keys.
The HelloSign platform provides five walkthroughs: for signature requests, templates, embedded
signing, events and callbacks, and OAuth 2.0. These are very useful as documentation, but no
sample code as such is provided; all the examples show cURL. As a result, it took us longer than it
should have to get a PHP script up and running to make API calls.
HelloSign also provides a client library for Java and links to third-party libraries for Ruby and .Net.
Had we used one of these, we might have gotten up and running more quickly, but none of these
provides real sample programs. The Java library includes a few code fragments, and the others
provide one each. This is a relative weakness for HelloSign, but we were able to overcome it with
reasonable speed.
HelloSign does not have free developer accounts, but all of its plans come with a 30-day free trial.
This is probably what disappointed us most about HelloSign: Sometimes you just get busy, and 30
days isn’t enough. The HelloSign model does not make sense, especially since signature requests
will be watermarked as tests and not legally binding without a paid account. This is all the more
reason to give developers more freedom. Nor does HelloSign have any community features. The
company would do well to move to a more developer-friendly model.
With all of that said, HelloSign made a surprisingly good impression on us for a product we’d never
heard of from a small and relatively new company.
12. 10 ProgrammableWeb Report: APIs for eSignature Products
RightSignature
Product Home Page:
https://rightsignature.com
Developer Portal:
https://rightsignature.com/apidocs/overview
RightSignature is one of the more mature products out there, but we found it confusing. From the
API point of view, it is atypical in many ways and difficult to get up and running. The documentation
sends mixed signals and, considering how long RightSignature has been around, should be more
comprehensive.
Authentication with RightSignature appears to require the use of OAuth. We gave it a try, but were
unable to get past a lot of “Invalid OAuth Request” errors. There is documentation and sample code
for authentication via OAuth and a secure token (a long encoded string provided by RightSignature),
but we couldn’t get it to work. Indeed, this organization kept us from testing the APIs interactively
with cURL, Postman or anything else.
Oddly, sample code for the authentication process is provided (Ruby, Java, PHP, Python and C#),
but there is no general documentation of the process. The APIs themselves have better, but still
skimpy, documentation. There are no JSON examples, and the XML is illustrated only with examples,
not a description (although the examples seem adequate). RightSignature has no community
features.
There are two sample programs: a perfunctory one in Java and a more substantial one in PHP. We
gave the PHP example the old college try, but it requires the creation of a MySQL database.
RightSignature API request data must be XML, but the response can be either in XML or JSON. This
seems like an odd state of affairs, and we can only assume that JSON will eventually be available as
a request format.
13. ProgrammableWeb Report: APIs for eSignature Products 11
Sertifi eSignature
Product Home Page:
http://www.sertifi.com/
Developer Portal:
https://sertifi.zendesk.com/forums
Sertifi eSignature is the only product in this comparison that provides only SOAP APIs. Sertifi says it
will be releasing a REST API in the second quarter of 2014, but it was unavailable for testing at the
time we compiled this report. This makes a direct comparison to the other products tricky, but we’ll
do our best.
Sertifi is designed to ease the stress of implementation and, for the most part in our tests, it lived up
to that promise. With the exception of DocuSign, Sertifi also has the most extensive API we tested.
Documentation for SOAP APIs is still important. But an associated technology, WSDL (Web Service
Description Language), serves some of the same purposes. SOAP tools read the provider’s WSDL
to build documentation directly into the process. Using the API is a matter of filling in the fields
described by the WSDL.
We used the well-known free SOAP utility SoapUI and the one WSDL gateway that was included in
the API Developer’s Kit, along with the customer API key. With these, we were able to generate all
the required method operations for the majority of functionality needed.
Sertifi does not advertise free developer accounts on its web sites, but the company told us it will
give an evaluation sandbox to anyone who asks for it.
Excellent API documentation was available both in HTML and PDF. Sample code is available for C#
and PHP and is perfunctory, touching only one or two API calls apiece.
Overall, Sertifi made a good impression as straightforward and usable, although the WSDL
contained methods that weren’t in the documentation. We didn’t test every one of the API’s
methods, so we can’t say just how serious this problem is. Seasoned SOAP developers tend to rely
on WSDL rather than the documentation, and might not even notice the discrepancy.
Sertifi uses ZenDesk for support, including a discussion forum and knowledge base. Both are
sufficient and functional, and more than most other vendors provide.
14. 12 ProgrammableWeb Report: APIs for eSignature Products
Silanis e-Sign Live
Product Home Page: http://www.silanis.com/
Developer Portal: http://www.developers.silanis.com/
API Documentation:
http://docs.e-signlive.com/doku.php?id=esl:e-signlive_api-routes
JSON Schema:
http://docs.e-signlive.com/10.0/schema/index.html
Silanis comes to the e-signing game from an enterprise background—specifically, banking and
insurance. Its heritage shows up in many ways, including integration with the business-focused IBM
Smart Cloud. (Other integrations are in the works.) Regulated enterprises and governments form the
bulk of Silanis’ client base. The company’s Java and .NET SDKs appeal to these customers, although
not as often to smaller companies and independent developers.
Just a glance at the API documentation and you can tell that Silanis’ approach is different. The
calls are oriented around working with packages, the basic unit of a transaction for e-Sign Live. A
package contains all the elements of a signing transaction: documents, approvals, users with roles,
workflow routes and more. The actual process of applying all this is called an “e-Sign Ceremony.”
If you plan to write Java or .NET code, Silanis e-Sign is a very friendly environment. The SDKs are fairly
extensive and give well-designed access to higher-level features than are found in the base API calls.
Silanis says that other SDKs are in the works. If you’re not writing Java or .NET code, e-Sign Live is
completely unhelpful. It’s theoretically possible to program the API directly (using REST and JSON) from
some other language, but you’d be much better off just taking your business elsewhere.
In addition, the documentation for the API is scant. In other products, much of the division of
functions is accomplished by creating separate APIs. In e-Sign Live, this is accomplished by
manipulating the large and complex JSON schema.
Another interesting example of the difference in the Silanis approach is that it tends not to incorporate
functions that are in the other APIs. For example, each package has a package ID (a GUID) that the
program must supply to E-Sign in order to access and manage that package, but there is no function
for enumerating packages. That must be done by the outside application (or the Silanis user interface for
the standard business version of e-Sign). Other APIs typically have a means of enumerating documents
associated with the account or user.
All of this supports the conclusion that Silanis e-Sign Live is not usable without a higher-level
language SDK; even with that, it is lacking in many ways compared to other products. Because of
Silanis’ background with heavily regulated businesses, e-Sign has a good set of APIs and SDK interfaces
for documents, metadata and audit trails. But the documentation and other facilities are written only for
Java and .NET programmers.
Silanis provides two kinds of trial accounts: a business user trial, which gives access to its stand-alone
user interface and does not include API access; and a sandbox account for developers. The developer
sandbox accounts do not expire and has no limit on the number of documents a company can create,
but all documents put into the system get watermarked by Silanis. This is a very developer-friendly
arrangement, allowing testing and analysis of the system without any time rush.
Silanis is weak when it comes to developer community. There are no forums or other means for
developers to interact, although the company says it is working on it. The Developer Portal has a
“Forums” link which says “Coming soon!”
15. ProgrammableWeb Report: APIs for eSignature Products 13
Products Not Tested
Arx CoSign
ARX CoSign (http://www.arx.com/) is an enterprise tool for using digital signatures to authenticate users
and other objects in the system. CoSign also has an e-signature feature, which it refers to as “graphical
signatures,” but, for the most part, the product associates digital signatures to documents so that others,
inside or outside the organization, can verify the authenticity and integrity of documents. (For more on the
distinction between e-signatures and digital signatures, read the section that appears earlier in this paper.)
In many ways, the use case for digital signatures as CoSign provides them is the same as that of
e-signatures. But CoSign is a far more complex product that does much more than any of the e-signature-
only products.
If all you are looking for is e-signatures, then CoSign is not for you. However, if your organization is large
enough and needs security standards that are more rigorous than those found in the products analyzed in
this paper, CoSign is a good candidate. For example, CoSign offers both a cloud and on-premise version of
its platform. Companies in heavily regulated industries—such as health care, finance and transportation—are
likely to have these requirements.
We did not include this product in our report because e-signing represents only a fraction of its functionality.
AssureSign
AssureSign (http://www.assuresign.com/) has had a SOAP/XML API for e-signing for many years. Until
fairly recently, the company restricted access to the API to licensed partners. Now, however, the API is open.
We intended to include AssureSign in this comparison, but we had to remove the product late in the process
because we had some difficulty getting the service to work and could not resolve the issues before press time.
Universign
Universign (https://www.universign.eu/en/) focuses on ease of use, simplicity and legal compliance
for the European market. Its API (https://www.universign.eu/en/api/electronic-signature/) is based on
XML-RPC, a technology that was the inspiration for SOAP. This makes it much simpler than SOAP, but it will
perhaps be unfamiliar to many developers. We decided not to include it at the suggestion of Universign and
because its European focus would make comparison difficult.
API Feature Set
The features of e-signature providers are segmented into eight categories:
• Signing Options: Define and handle signing locations and signing process
• Transaction Verification: Access status updates, view audit logs and verify transaction steps
• Template Support: Apply pre-defined templates to documents in order to facilitate document
sending
• Document Support Functionality: Create and send documents
• Form Form Field Support: create dynamic documents to define the transaction workflow
• Workflow Support: Define the signing process in a way that best fits the parameters of the
transaction
• Security Fraud Prevention: Secure transaction documents and authenticate document recipients
• API and Data Types: Does the product support REST and/or SOAP, JSON and/or XML?
16. 14 ProgrammableWeb Report: APIs for eSignature Products
The charts in this section cover only features supported through the API. Some of the products may support
features in this chart, but only through their user interface.
Signing Options
Number
of signing
modes
Sender
can choose
signing
option Custom Options
Adobe Echo Sign 4 4 Specify signing page/email language
Barracuda SignNow 4 In person, freeform, embedded signing, email invitation
DocuSign 4 4 Language of signing page + emails can now be
specified via the API. DocuSign now allows users to sign
with a digital certificate (SAFE-BioPharma, DocuSign
Express). Branding of signing and sending experiences is
customizable via the APIs, leveraging branding capability.
HelloSign 2 Three signature location options
RightSignature 1 Embedded signing in client interface; signer sequencing
to set specific signing order
Sertifi eSignature 4 4 eSign (type signature, biometric touch), paper (print, sign,
fax), in-person, in-session (integrated in customers portal),
multiple language support
Silanis e-Sign Live 3 3 modes: Click-to-Initial, Click-to-Sign, Scripted Signature.
eSignLive account holders may store captured signatures
and other associated files for one click application to future
signed documents.
Several of the products provide a good selection of methods and locations for signing. All support the
obvious electronic signature—the whole point of this market. Many support some form of paper signature.
Other options uploaded signature images, digital signatures, required in-person signature and specification of
different locations for the signature. RightSignature does support paper/fax signing, but it is an account setting
and not controllable through the API.
17. ProgrammableWeb Report: APIs for eSignature Products 15
Transaction Verification
Adobe
Echo Sign
Barracuda
SignNow
DocuSign HelloSign RightSignature Sertifi
eSignature
Silanis
e-Sign
Live
Receive event-
driven status
updates
4 4 4 4 4 4 4
Event failure
notification
4 4 4 4 4 4
Send remind/
expire/
no receive
audit log of
transactions
4 4 4 4 4 4
Receive
audit log of
transaction
4 4* 4 4 4 4 4
Access
certificate of
completion
and
authoritative
copy
4* 4 4 4 4 4
* Barracuda says it has this feature but that it is undocumented. We did not verify this claim.
You can see that there are a few gaps in this chart—mostly attributable to SignNow. The absence of failure
notification and remind/expire notices is a pretty serious problem, particularly when competing products
perform better in those areas. RightSignature notes that the product can be configured to provide email
notifications to the API key holder if the callback fails.
Template Support
Adobe
Echo Sign
Barracuda
SignNow
DocuSign HelloSign RightSignature Sertifi
eSignature
Silanis
e-Sign
Live
Apply
template to
documents
4 4 4 4 4 4 4
Templates are frequently used documents that are customized to a particular signing. Certain contracts that
are sent out frequently but differ just in terms of, say, the name of a party and dates are good candidates for
templating. Adobe did not claim template support, but its Library Documents—which are, in effect, PDFs—
serve many of the same functions. The EchoSign API cannot create Library Documents, but it can use them.
The level of support for templates differs among the products. DocuSign, Sertifi and, to a lesser extent, Silanis,
have layout support and field creation/editing support for templates.
18. 16 ProgrammableWeb Report: APIs for eSignature Products
Document Support and Functionality
Adobe
Echo Sign
Barracuda
SignNow
DocuSign HelloSign RightSignature Sertifi
eSignature
Silanis
e-Sign
Live
Send
document
to multiple
recipients
4 4 4 4 4 4 4
Create/Send
batches
4 4* 4 4 4 4
Define
document
visibility
4 4* 4 4 4 4 4
Submit
complete
and partially-
finished
batches for
delivery
4* 4 4 4
Void batches 4 4* 4 4 4 4 4
Edit recipient
info or transfer
ownership of
an existing
batch
4 4 4
* Barracuda says it has this feature but that it is undocumented. We did not verify this claim.
All of the products can send a document to multiple recipients and send batches of multiple documents. In a
sense, this is a minor convenience because your software can always just loop through a list of documents,
calling the APIs for each. But there is certainly value in being able to do just one API call.
The level of support differs among products. With the exception of Adobe EchoSign, all of the products we
tested can specify the signing order for signers. Some can specify that certain signers are required while
others are optional. Sertifi claims to have the ability to specify as many as 10 sequential levels of signing with
parallel signing orders at each level.
Things get more complicated with batches of documents. EchoSign, SignNow and HelloSign can
send documents in batches; DocuSign and RightSignature can send templates and forms in batches
(RightSignature calls them “packages”).
DocuSign and Sertifi are the clear leaders in the area of document visibility. They can specify which users
can see which documents. DocuSign supports Accessibility Reading Zones, which permit screen reading
applications to read instructions, envelope documents and DocuSign tags.
SignNow, DocuSign and Sertifi allow software to submit complete and partially finished batches for delivery.
Only DocuSign and Sertifi allow programs to edit the participants in an already-created batch and transfer or
modify ownership.
19. ProgrammableWeb Report: APIs for eSignature Products 17
Form Field Support
Form Support
Adobe
Echo Sign
Barracuda
SignNow
DocuSign HelloSign RightSignature Sertifi
eSignature
Silanis
e-Sign
Live
Create forms,
distribute
forms via
multiple
protocols
4 4
Field Support
Adobe
Echo Sign
Barracuda
SignNow
DocuSign HelloSign RightSignature Sertifi
eSignature
Silanis
e-Sign
Live
Create/Place
form fields
4 4 4
Multiple form
field types
4 4 4
Define field
locations
and field
operations
4 4 4
Assign
specific
signing tasks
or data fields
to specific
individuals
4 4 4
Most simpler applications will use Acrobat or some other product for form design and modification, but
Barracuda SignNow, DocuSign and Silanis e-Sign Live all allow users to manipulate forms in their system
directly.
DocuSign can use free form text fields or date, company, title, radio, check and drop-downs. Barracuda
supports signatures, test fields, initials, checkboxes and enumerations. Silanis claims support for boolean,
text field and pick list fields, and in its documentation we see dates and check boxes, but it’s difficult to tell
for sure what is supported. Silanis is not designed for this level of control at the API level, but rather through
its Java and .NET SDKs.
20. 18 ProgrammableWeb Report: APIs for eSignature Products
Workflow Support
Adobe
Echo Sign
Barracuda
SignNow
DocuSign HelloSign Right
Signature
Sertifi
eSignature
Silanis
e-Sign
Live
Routing type
for signatures
Serial Serial Serial,
parallel and
combination
Serial,
parallel and
combination
Serial Serial,
parallel and
combination
Serial
Assign agent
(3rd party
management)
or editor roles
for recipient
4 4 4 4
Correct/
reassign
workflow
for batches
already
submitted
4 4 4
Workflow control is a core feature of these products, and all have at least minimal support for it through their
APIs. Minimal is all Adobe and Barracuda claim. DocuSign and Sertifi are the leaders here. Both, along with
HelloSign, support both serial and parallel signing and a combination of both. Both DocuSign and Sertifi
also allow the designation of a third-party agent role (what Sertifi calls a “Power Admin”). RightSignature
and Silanis also support this feature. DocuSign, Sertifi and Silanis support a program to change the
workflow of an already submitted batch.
With respect to correcting/reassigning workflow for already-submitted batches, RightSignature says that to
maintain legal audit logs, the document and designated recipients cannot be edited after the document
has been sent. However, it is possible to easily resend documents to new recipients with a duplicated
document overlay. The company calls this its Import Overlay feature.
21. ProgrammableWeb Report: APIs for eSignature Products 19
Security Fraud Protection
Adobe
Echo Sign
Barracuda
SignNow
DocuSign HelloSign Right
Signature
Sertifi
eSignature
Silanis
e-Sign
Live
Number of
methods of
recipient
authentication
3 1 8 2 3 5 4
Password
protection for
documents
4 4 4 4 4
Public key
infrastructure
(PKI) digital
certificates to
seal exported
documents
4 4 4
Define
authentication
requirements
for signing/
accessing
batches
4 4 4 4
E-signatures aren’t an inherently secure system. When you electronically submit a document for signature
to a recipient, it is important to be able to authenticate the recipient.
In a sense, when the system sends out an e-signature request to an email address, it is inherently
authenticated as going to a person with access to that email account. That’s not much, but we’ll count it as
one method here.
Adobe has three methods for authentication, including email: Through a partnership with LexisNexis,
EchoSign programs can be programmed to require knowledge-based authentication through a series of
customized, non-trivial questions from the recipient’s past. Recipients can also sign with their Facebook,
LinkedIn or Google accounts, and EchoSign will automatically capture their picture and a URL link for their
public web identity. EchoSign also supports password-based encryption of documents.
DocuSign blows away the field with eight methods: email; a special shared access code; digital
certificates; a code sent through SMS; phone authentication in which the recipient must call a number and
enter their name and a special code; third-party authentication (Google, Salesforce, Yahoo or Microsoft);
knowledge-based authentication (recipients are asked a series of credit-check-like questions); and
geolocation capture.
In addition to email, HelloSign allows a signer PIN that needs to be entered, similar to DocuSign’s access code.
Sertifi has a very respectable selection: email; a folder-based password (this is a special password
particular to Sertifi’s architecture); users can be required to create and log in with a Sertifi account;
knowledge-based authentication; and a phone verification similar to DocuSign’s.
RightSignature supports email, a custom password, and (uniquely, we believe) a webcam photo to be
returned with the signature.
Silanis supports email; a shared secret (access code); SMS code; and third-party authentication.
SignNow only supports email.
22. 20 ProgrammableWeb Report: APIs for eSignature Products
There are other techniques to strengthen security: EchoSign, DocuSign, HelloSign, RightSignature and
Sertifi allow password protection of documents themselves.
DocuSign, Sertifi and Silanis support digital certificates to “seal” documents. Sertifi requires an additional
module and fee for this feature, whereas Silanis says that all its documents are sealed in this way.
Finally, DocuSign, Sertifi and Silanis all support special authentication requirements for signing or accessing
batches.
API Types
Adobe
Echo Sign
Barracuda
SignNow
DocuSign HelloSign Right
Signature
Sertifi
eSignature
Silanis
e-Sign
Live
REST 4 4 4 4 4 4
SOAP 4 4 4
Both EchoSign and DocuSign started out with SOAP APIs and more recently added REST. Sertifi supports
only SOAP now, but says it will soon release a REST API. The other products support only REST.
Data Types
Adobe
Echo Sign
Barracuda
SignNow
DocuSign HelloSign Right
Signature
Sertifi
eSignature
Silanis
e-Sign
Live
Request
body formats
supported
JSON JSON JSON, XML
JSONX
JSON XML XML JSON
Response
body formats
supported
JSON
(Some
PDF,
some raw
data)
JSON JSON, XML JSON JSON, XML XML JSON
(Some
ZIP,
PDF)
Both XML and JSON have their fans, but it’s clear that JSON is on the rise. Other than Sertifi, the products
all support JSON in at least some context, and it would seem that RightSignature will eventually support
JSON for request data. As SOAP is an XML protocol by definition, Sertifi supports it and only it. Sertifi says
that when its REST API comes out it will support JSON.
23. ProgrammableWeb Report: APIs for eSignature Products 21
Conclusion
A lot has changed since our last look at e-signing APIs, three years ago: The market is much bigger, with
many more products to choose from. But one thing has not changed: DocuSign is still the clear leader.
Our evaluation showed that DocuSign has the greatest breadth of features available under the API, the best
developer tools and the best code samples and documentation. However, for some users, the API is so
large that it may be intimidating and difficult to get off the ground. With that said, one man’s complicated is
another man’s powerful and comprehensive.
At the other end of the complexity spectrum is HelloSign. Both the product and the API are simple and easy to
use. The feature analysis chart shows at a glance that HelloSign doesn’t have anywhere near the capabilities
of DocuSign, but some users have simple needs—and/or an aversion to complexity—that will be satisfied
by HelloSign. If you need to write a quick program that incorporates digital signing and you don’t have any
expectations of growing it, HelloSign may be the right choice.
Sertifi eSignature supports only SOAP and XML for now, which will limit its appeal among some users,
but SOAP programmers should feel at ease with the platform. It has excellent documentation and a very
capable API, if not quite as many features as DocuSign. Of course, DocuSign also provides support for
SOAP/XML, even if the company says there is little interest in SOAP among its current customers. If you
want to write SOAP code for e-signing, both DocuSign and Sertifi are good choices.
The other four products—Adobe EchoSign, Barracuda SignNow, RightSignature and Silanis e-Sign Live—
were disappointing to varying degrees in our evaluation. EchoSign may be the most disappointing, as
Adobe seems to be letting the product, or at least the API in the product, stagnate.
RightSignature’s, Silanis’ and Barracuda’s products were all challenging to work with, had API
documentation that ranged from bad to worse, and offered minimal sample code. SignNow is least ready
for prime time.
The good news is that developers have several good options—with DocuSign leading the pack—for
automating the most old-world of processes, leading to great leaps in productivity.
DISCLOSURE:
ProgrammableWeb was retained by DocuSign to develop this report. However, one of the conditions under which ProgrammableWeb accepts such
custom research work is that the reports’ underwriters can, in no way, influence the methodologies used in evaluating the various players or the final
outcome of the report. In fact, the only part of the outcome that DocuSign influenced was the inclusion of its API in the comparison. Beyond that,
the testers, writers and editors who had a hand in this report’s production received no guidance, instructions or influence—directly or indirectly—from
DocuSign. Questions about this report or ProgrammableWeb’s custom research program should be directed to editor@programmableweb.com.
24. 22 ProgrammableWeb Report: APIs for eSignature Products
ProgrammableWeb gets you the latest on what’s new and interesting with mashups, Web 2.0
APIs, and the Web as Platform. It’s a directory, a news source, a reference guide, a community.
Visit us at programmableweb.com.