This document summarizes a seminar on DocuSign certification. It outlines why certification is important, when it is necessary, how to prepare for certification including demo requirements, the certification process, and next steps after certification. Certification ensures applications are sustainable, scalable and compliant before being listed in the DocuSign Marketplace and moving to production. The seminar provides guidance on best practices and addresses upcoming API rate limits.

1. Welcome to the Deep Dive into DocuSign Certification Seminar If you would like to ask questions during this session, please: Call into the conference line (on your confirmation email) Enter access code: (on your confirmation email) Enter audio PIN (# shown after joining webinar) Presenter: Mike Borozdin The webinar will begin shortly…

3. Developer Workshop Deep Dive into DocuSign Certification

4. Webinar Outline Why do I need to certify? DocuSign Marketplace When certification is necessary Fees and other information How to be prepared for the meeting Preparing a demo Sample demo, or the meta-demo What happens after certification Next steps…

5. Why do I need to certify? Important change from the demo environment to production environment Need to ensure that the behaviors that occur in development are sustainable and scalable Confirm that the application complies with certain guidelines and standards Most of all, we want to make you as successful as possible!

6. DocuSign Marketplace Listing of applications that add value to the DocuSign service Being included in the DocuSign Marketplace gives you access to reviews, download statistics and greater visibility Getting certified gives you the option of being included in the DocuSign Marketplace!

9. How to be prepared for the meeting Fill out your certification checklist Prepare a demo of you integration Make sure you can explain the security protocols of your integration Be prepared to show that you are using your integrator’s key! Test your error handling for when you cannot reach DocuSign Know how to capture the trace of an envelope Audit your own API calls

10. Preparing a demo When preparing your demo, you will want to test several use cases. Some cases are: User declines to sign User’s information is incorrect Sender voids the envelope User takes more than one session to sign Application cannot connect to DocuSign Someone resets your DocuSign credentials

11. API Rate Limits coming soon! To maintain reliability and stability within our demo and production environments, DocuSign has operated with certain API call efficiency guidelines. To ensure effective load balance, we continually monitor the API calls in our backend systems and reach out to work with developers putting unnecessary burden on the system. Going forward, DocuSign will implement an API Call Rate Limit to further balance loads on the system. Effective March 1, the demo environment (demo.docusign.net) will be limited to a call rate of 1,000 API calls per hour per account Effective April 1, the production environment (www.docusign.net) will be limited to a call rate of 1,000 API calls per hour per account Please note that when the API call rate limit is reached you will receive an exception on every call for up to 60 minutes, until the next hour starts.

12. Sample Demo, or the meta-demo

14. Polling our system

15. Using the wrong authentication

17. Put recipient specific messages into the recipient note

19. Next steps… Change your endpoints to point to production Cease any polling behaviors you may have in our demo environment Remember, our demo environment is only for active development Continue to use our demo environment for any code changes Production is for code that has been thoroughly developed, tested and certified Remember, re-certification is only necessary for new functionality, code paths or framework changes

20. Q & A

21. Thank you!