DocuSign认证的严格性 [英] Stringency of DocuSign Certification

问题描述

从DocuSign的 API要求信息中：

From the DocuSign "API Requirements Information":

[Y]我们的API认证审核涉及验证您每个唯一身份请求的状态请求数是否超过1每15分钟使用一个信封，以轮询以下方法的合规性：...

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

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

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

这些要求有多严格？如果我99％的用户仅发出1个状态请求，而少数几个（在午夜左右注册）将互相紧接发出2个请求，我的API访问权限会被撤销吗？

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

推荐答案

该准则意味着您不应该允许最终用户连续点击以获取最新状态。

The guidelines mean that you should not allow end users to continously click through to docusign to fetch latest status.

正如Jeff在评论中所说，您应该使用Connect api或每个信封回调，或缓存状态响应，发出实际的docusign请求不超过每个信封每15分钟一次。

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

最大轮询频率和状态体系结构是认证过程要研究的关键问题之一。

Maximum polling frequency and status architecture is one of the key issues that the certification process seeks to investigate.

在请求后，您也可以禁用状态按钮15分钟。但这不是好习惯。最好通过15分钟的缓存有效地禁用它。 --就像电梯上的关闭按钮。

You could also disable your "status" button for 15 minutes after a request. But that wouldn't be a good ux. Better to effectively disable it via a 15 minute cache. - - like the close button on elevators.

已添加

每信封回调参数为 eventNotification 。

这篇关于DocuSign认证的严格性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！