Last week, The DocuSign API Team sponsored the API World Hackathon. For two days, we helped integrate the DocuSign Agreement Cloud into a variety of apps. API World, hosted each year in San Jose, CA, attracts mostly enterprise software engineers, entrepreneurs, and technologists looking to share knowledge, trust, and business within the developer community of API providers and consumers.

Our Workshop

On Wednesday morning, DocuSign Developer Evangelist Matt Roknich gave a workshop entitled “Crash Course on the DocuSign APIs,” which began with a high-level overview of the DocuSign Agreement Cloud and ended with an in-depth overview of a Node.js code example demonstrating how to send a remote envelope using our eSignature API. If you’re interested in experimenting with this code example yourself, clone the repo from the DocuSign API GitHub and check out example #2. 

Our Challenges

As DocuSign looks to expand the functionality accessible to our developer community,  we continue to release new APIs! Our challenges this year reflected this: Hackers were tasked with integrating either the eSignature API or the Click API. The best use of either API would win both bragging rights online and a hefty cash prize. Our intent behind these open-ended challenges was to enable hackers to be as creative as possible with their projects. 

Our Prize (and SWAG)

When it comes to hackathon prizes, we’ve learned that cash is king. The first prize for Best Use of the DocuSign eSignature API was a hefty $1000; second place was $500. Our Click product is designed to be implemented with ease, so the prizes were adjusted accordingly. Our first-place winner for Best Use of the Click API received $500; second place was $250. 

Winners

Our team was incredibly impressed with the ways hackathon teams used both our eSignature API and our Click API to automate agreements or workflows. Because it was so difficult to select our winners, we want to give a special shoutout to all API World teams who successfully integrated with DocuSign. Great job! 

Best Use of the Click API, Second Place: My Journal for iOS

Jim Montoya, the recipient of our 2nd place award, has suffered from a condition called Myalgic Encephalomyelitis/Chronic Fatigue Syndrome (ME/CFS) for over 14 years. He discovered that tracking symptoms on paper or on an existing app was very difficult. Eventually, he decided to take matters into his own hands. 

My Journal helps individuals suffering from chronic conditions to track day-to-day symptoms and vital signs. The app reports can be used to support disability claims, but also to provide historical trends of patient’s health condition. My Journal can be used on an iPhone/iPad, but the web version will work in any modern browser. 

Jim utilized DocuSign Click and the Click API to present “Terms of Service” acknowledgments to his users before allowing them to access his application. He was particularly excited by the “must-read” feature when generating a clickwrap, as many similar legal and medical terms are often skipped or overlooked. 

Head over to our DocuSign Developer center to learn the basics of our Click API

Best Use of the eSignature API, Second Place: BudgetMe

Team BudgetMe recognized that loans are apart of modern commerce and personal finance, but access isn’t always realistic, especially in the case of micro-loans. The team’s platform solves this problem by crowdsourcing the procurement of micro-loans. 

Users can submit a request for micro-loans on this platform. If another user accepts the request, both users are automatically sent a custom contract to be signed via the DocuSign eSignature API. Once the agreement is completed, both users can then proceed with the transaction. 

Head over to our DocuSign Developer center to learn the basics of our eSignature API. 

Best Use of the Click API, First Place: Eagle

Team Eagle was frustrated by the lack of organization in clubs they were a part of. As a result, they built out a task management application using React. The app enables users to create task objects and move them between status columns, not unlike other popular productivity apps such as Asana or Jira. For tasks with legal implications, Eagle wanted to leverage the DocuSign Agreement Cloud APIs to automate terms of service. 

The challenge, however, was that DocuSign Click auto-generates a JavaScript snippet and not JSX. To resolve this, the team created a custom React component to render the DocuSign clickwrap agreements. 

If you are interested in implementing DocuSign Click in your React app, check out the winning team description for some pointers. 

Best Use of the eSignature API, First Place: Guided Signing

Our first place winners, Team Guided Signing, recognized some values in legacy signing processes. Before the age of eSignature, agreement recipients were often forced to sit side-by-side to discuss and sign documents: for example, property purchases. DocuSign eSignature virtualized the process, freeing up recipients to sign when and where they pleased. 

The team wanted to keep these freedoms while allowing recipients to interact with one another virtually before kicking off the DocuSign signing ceremony. 

Guided Signing is an application that enables signing recipients to speak to one another over a private video conference, while simultaneously discussing and editing a document. Once the recipients agree on a final version, a user can send that copy for signature using the DocuSign eSignature API. The team used the TokBox API to implement the live video while embedding Google doc functionality within an iframe to handle the live document edits.

What’s Next? 

Next week, The DocuSign API team is heading to the University of California – Berkeley to support student developers at CalHacks. Stay tuned! 

Additional Developer Resources:

Matthew Roknich is a Developer Evangelist and a lifelong problem solver. His current projects outside of DocuSign involve advanced IoT and sustainability. He can be found on a soapbox talking about the Agreement Cloud APIs at a variety of developer conferences, hackathons, and meetups.