Preparing for DocuSign Connect API Certification

Introduction
DocuSign Connect API is a powerful way to include an electronic signature and automate parts of your electronic contract execution process. The DocuSign Connect Application Programming Interface allows you to send documents, get status of outstanding or completed contracts, retrieve signed files and control the signing process workflow.  Supporting an integrated application includes challenges not experienced by users that interact with DocuSign user interface.
The complexities of support and management of API customers  In order to make sure DocuSign customers have access to the best possible solutions, DocuSign has created a DocuSign certification session (Certification) requirement. Any new system that intends to interact with DocuSign web services must be introduced to DocuSign developer support and operations staff.
During the Certification session, your operations and development team and DocuSign personnel go through the Certification Checklist available from your DocuSign account manager. The latest version of the checklist is 2.7.
What are some best practices when preparing for the Certification session?

Demonstrate Use Cases
To schedule a Certification, your application needs to be close to complete. We understand that you will keep innovating in your space and continue converting more document execution to DocuSign. For us to get the proper context, we need to see at least a Beta.
Most of the applications we certify have multiple use cases. If only select use cases deal with electronic contract execution or electronic signatures, we recommend isolating your DocuSign use cases and preparing data, if possible, to provide the most benefit.
For example: What if your user needs to establish an account, input 3 screens of data and then sign the appropriate application? You can pre-create a user with all the data entered prior to Certification.
Commonly missed edge use cases:
1.    Users can decline to sign: DocuSign interface supports that.
2.    Users can take several sessions to sign: DocuSign allows someone to review the document, leave the signing experience and come back later to re-start signing.
3.    Network connectivity issues: Network code needs to account for circumstance. You can simulate that by plugging in the wrong web service URL.
4.    Mistyped username or password: While it's unlikely that your API enabled user account will mistype passwords, you do want to be ready when someone resets the password through DocuSign account management console.

Timing
You might get some actionable feedback during the Certification process. That means your code, your workflow and maybe your configuration may need to change. If your company has actively engaged DocuSign Professional Services, then most likely you will have no surprises waiting for you. However, if you were coding on your own, it's probably best to structure additional review time in your schedule to ensure sufficient time in your application release cycle.
Keep in mind that DocuSign Professional Services are booked out about 2-3 weeks in advance. The earlier you can let your account manager know that you have a new application getting ready to certify, the better.

Participants
During the Certification, your sustained engineering staff and the implementation team will be introduced to DocuSign developer support, operations and escalations personnel.
One of the goals of certification is to ensure that, in case of an emergency, precious time is not wasted determining who needs to be contacted and who can fix the business critical systems.
Re-certification: “When Do I Need to Re-certify?”
Given the fee associated with the Certification, it's natural to try to minimize the number of Certifications. That's a fine strategy as long as the supportability of your application doesn't suffer.
In a case where you are adding more signatures or documents to the same process, it's probably not going to change the calls or architecture of the application. You can continue innovation on that scale without looping DocuSign in. However, if you introduce a brand new module, change frameworks, or change programming languages then you might end up in a situation where the DocuSign documentation on your solution is out of date. Contact your Account Manager!

Summary
Please let us know if you need additional clarity into the certification process and our expectations. As mentioned above, the latest checklist can be obtained from your DocuSign Account Manager. While the contents of the Certification Checklist are constantly refined and improved, the spirit of ensuring quality, supportable integrations with DocuSign service remains the same.