Geek Answers Handbook

Strict DocuSign Certification

From the DocuSign API documentation:

[Y] our API certification review includes verifying that you do not exceed 1 status request per unique envelope in 15 minutes to verify compliance for the following methods: ...

REST API: GET / accounts / {accountId} / envelopes

How stringent are these requirements? If 99% of my users make only one status request, but several (who sign up around midnight) make 2 requests in close proximity to each other, will the access to the API be canceled? How risky is this?

+5
source share
1 answer

Recommendations mean that you should not allow end users to switch to docusign continuously to get the latest status.

As Jeff says in the comments, you should use call api or per-envelope callback or cache status responses by making the actual docusign request no more than once every 15 minutes per envelope.

The maximum polling rate and state architecture are one of the key issues that the certification process is trying to investigate.

You can also disable your status button within 15 minutes after the request. But that would be nice. It’s better to effectively disable it through a 15 minute cache. - - like a close button on elevators.

Added

Callback parameter per-envelope eventNotification .

+2
source

More articles:


All Articles