DocuSign

DocuSign Developer Newsletter

ISSUE DATE: April 3, 2017

Welcome to the April 2017 issue of the DocuSign Developer newsletter! We aim to bring together in one place all the most valuable and interesting updates on everything from the DocuSign APIs themselves, to tools and resources (such as SDKs, release notes, documentation updates), to API recipes, upcoming events, trending topics, and more.

In this issue, we cover DocuSign in the news, developer center and best practices, developer spotlight, release notes, top trending topics, and upcoming events.

IN THIS EDITION:
IN THE NEWS | DEVELOPER CENTER AND BEST PRACTICES | DEVELOPER SPOTLIGHT | RELEASE NOTES ROUNDUP | TOP TRENDING TOPICS | UPCOMING EVENTS

IN THE NEWS


API GO-LIVE PROCESS NOW AUTOMATED

We've now automated the Go-Live process for moving your API-integrated apps from our development (sandbox) environment to production. What used to take days or weeks is dramatically reduced to minutes or hours. Read this blog post to learn more.



DocuSign Developer Community Now 40,000+ Strong

You've probably noticed that we've been laser-focused on developers. We've created lots of free tools and resources to make it easy to integrate our eSignature API into your apps. Well, we've reached an important milestone and our community is now 40,000+ developers strong. Read this blog post for the full story.



DEVELOPER CENTER AND BEST PRACTICES


Configuring an F5 Load Balancer for Mutual TLS

Our own Larry Kluger continues his series on Mutual TLS with a new blog post focusing on using DocuSign with F5's Load Balancer. Read all about it this blog post.


DEVELOPER SPOTLIGHT

Laura Busuioc - Alameda County


Laura Busuioc has been a Systems Analyst for the Alameda County Information Technology Department since 2013. Since receiving her Master’s Degree in Computer Science from Romania, she has spent over 20 years developing quality software, while enjoying the challenges of keeping up with the changes in the latest technologies.

Alameda County started the initiative of reducing paper usage in 2012, and selected DocuSign technology as the best candidate for providing electronic signature technology to the County. Laura started working on DocuSign projects shortly after she joined Alameda County. She developed a reusable library using Microsoft.NET that allowed her and other team members to work with DocuSign API’s, making it possible to quickly deliver projects on time.

Due to the large volume of DocuSign project requests, Laura guided the effort to develop reusable components and generic DocuSign Connect listeners that would help the team speed up the development of future projects. These components and generic listeners read configuration data from a SQL Server database, and the business logic executes actions based on the configuration.

Besides the passion for her work, Laura loves reading, skiing and hiking.



If you have deployed solutions using the DocuSign eSignature API and you’d like to be considered for a future Developer spotlight, please send an email to tony.mann@docusign.com and supply information about your solution and a bio.

RELEASE NOTES ROUNDUP

We routinely update the platform to add new functionality and to address issues. This article outlines the recent high-level changes made to the platform. Detailed Release Notes for all releases can be found here.


April'17 Service Pack Notes
  • Release Type — Service Pack
  • Release Date — March 23, 2017
  • Platform(s) Affected — Demo (Sandbox)
  • Release Notes Detail — Click here

April'17 Service Pack Notes SUMMARY

  • Domain updates for Direct API Deployments — Specifies which DocuSign domains your system should allow.
  • Connect HTTP Listener Sunset Announcement — New accounts cannot use the Connect HTTP listener connection starting 6/15/2017; no account will be able to use HTTP after 2/1/2018.
  • Various Bug Fixes

Spring '17 Release Notes
  • Release Type — Quarterly Release
  • Release Date — March 3, 2017
  • Platform(s) Affected — Production
  • Release Notes Detail — Click here

Spring '17 Release Notes SUMMARY

  • SMS Phone Number for Recipient Authentication — Allows SMS providers to show recipients the best number they have available for a specific region or a specific carrier.
  • Fax Documents for Signature — Allows recipients to receive and return documents by fax.
  • Domain updates for Direct API Deployments — Specifies which DocuSign domains your system should allow.
  • Connect HTTP Listener Sunset Announcement — New accounts cannot use the Connect HTTP listener connection starting 6/15/2017; no account will be able to use HTTP after 2/1/2018.
  • DocuSign Payments Updates — Additional currencies and bulk send features have been added.
  • Various Bug Fixes

TOP TRENDING TOPICS

In March 2017, the most popular recipes were Using a webhook to track envelope status, Signing from Your App, and Request a signature via email using a template.

The top visited pages in the Developer Center included API Documentation, recipes, embedding, tabs, and templates.

Traffic to the Developer Center is the highest in the United States, followed by Canada, UK, Australia, India, France, and Brazil.

The top trending topics on Stack Overflow for the docusignapi tag are determined based on views and/or comments on specific threads. Here are the top three most frequently asked or viewed questions and answers:

Thread: DocuSign - Sending to Multiple Recipients

Summary: Using the eSignature API, the poster receives a [400] Error connecting to the API error when sending to multiple recipients.

Answer: The original poster was kind enough to return to the thread because it was self-answered. The poster discovered that the setRoutingOrder property must be set for the Signer.


Thread: Docusign: Can carbon copy recipients receive a notification when Signer views the envelope

Summary: As the thread title suggests, the poster is trying to determine if a "cc" recipient can receive notifications when a signer views the envelope.

Answer: The poster was advised about the conditions under which a recipient receives a notification. Please review the thread for more info.


Thread: How do I set the ttl on a docusign envelope URL?

Summary: The poster wants to better understand how Time-To-Live (TTL) is set on DocuSign envelopes.

Answer: The TTL value on DocuSign envelopes is fixed at five minutes. However, our own Larry Kluger presents the poster with a way to manage that in the custom app.



If you’d like to contribute to the community or ask a question, please visit us on Stack Overflow. Don’t forget to visit our Developer Center for complete documentation on how to use the DocuSign eSignature API.


UPCOMING EVENTS

DocuSign Momentum
Join us for our two-day annual conference called DocuSign Momentum in San Francisco on May 3-4, 2017. Developers can register free for Momentum, and we have lots of great sessions that you've asked for, including an in-depth look at our roadmap for developers, the eSignature API, Webhooks, app security, composite templates, sneak peeks into new products and APIs, and more. Plus, hear from customers and partners – more than 30 sessions in all. A few of the esteemed companies and organizations that have done amazing work with our eSignature API you'll hear from are:

Don't forget to bring ideas for your ground-breaking eSignature implementations to compete for the grand prize of $2500 in our on-site hackathon during the Momentum pre-day on May 2. We'll have more to announce as we get closer to the event. You can register for the hackathon here. Read more about what developers can expect from Momentum in this blog post.


Microsoft Build
Going to Microsoft Build in Seattle from May 10-12? So are we! Come see us at our booth and ask us about our Microsoft partnership and incorporating our eSignature API into your apps.


Twilio Signal
We'll be at the Twilio Signal conference in San Francisco from May 24-25. We'd love for you to stop by our booth to discuss our eSignature API.

SHARE YOUR FEEDBACK
We want to make sure that this newsletter is as useful as possible. Here is a link to a very short survey – please take a minute to give us feedback.
GO TO THE SURVEY

OTHER RESOURCES

Stay up to date with our developer blog series
Follow us on Twitter: @DocuSignAPI
Find us on GitHub: https://github.com/docusign

LIKE FOLLOW CONNECT YOUTUBE INSTAGRAM

www.docusign.com | docusign@docusign.com

221 Main Street, Suite 1000 San Francisco, CA 94105

To unsubscribe from future DocuSign emails click here.