Construction Company to Go Green By Eliminating Paper Contracts Using the Number One eSignature Solution Provider

Do you like coding up awesome solutions in a room with other innovators while a DJ spins some music in the background? Want a chance at up to $25,000 USD in cash prizes? Will you be in the San Francisco Bay Area on May 14th and 15th?

If you've answered yes to any of these questions...

Join us at the DocuSign San Francisco office for the DocuSign Hackathon!

Develop some code to make life paperless and be considered for awards totaling $25,000 USD.

This was originally posted on ProgrammableWeb.

Although it's hard to do justice to the topic of API security in the space of a blog post, the topic is important because it affects every API architect creating a new web service. Advice that has come from experience may be of particular value—and that's what follows here.

Flashing back to the days before DocuSign:
You sat by the printer, hoping you had enough toner to print the stacks of documents that needed get sent and returned ASAP. Then you settled down at your desk, with stacks of color-coded sticky notes meticulously marking where others needed to fill out information and sign. Next you trekked to the post office, sending your documents and notes to your signer, and returned to the office with a tracking number, your only tie to the just-sent envelope.

And you waited and crossed your fingers.