DocuSign REST API-RecipientView异常“ UNKNOWN_ENVELOPE_RECIPIENT”

本文介绍了DocuSign REST API-RecipientView异常“ UNKNOWN_ENVELOPE_RECIPIENT”的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

在使用docusign开发集成的Web解决方案时，我们目前遇到一些技术难题。您能否提出以下建议：

We are currently experiencing some technical difficulties whilst developing an integrated web solution using docusign. Can you advise on the following please:

我们如何在基于文档的rest api调用中为接收者分配签名顺序？我们可以有一个json示例吗？

How do we assign an order of signing to recipients on a document based rest api call? Can we have a json example?

我们目前无法检索已添加到已创建信封中的用户的签名URL。这段代码以前可用于基于模板的信封创建，但不适用于基于PDF的信封。

We are currently unable to retrieve a signing url for a user that has been added to a created envelope. This code was previously working for Template based envelope creation but does not work for ones based on using PDFs.

调用并显示了对docusign API的响应（已删除密码）。尝试了两种失败的身份验证方法。通过信封中找到的任意一封电子邮件检索也失败。

The call and response to the docusign API (with the password removed) is shown below. Two kinds of authentication method have been tried which failed. Retrieval via either of the emails found in the envelope also fails.

POST \\https://demo.docusign.net/restapi/v2/accounts/426142/envelopes/3b2d7418-27d3-4a80-8969-d875b6fb9548/views/recipient HTTP/1.1
X-DocuSign-Authentication: {"Username":"18f90756-70b1-4f5f-b360-48b198a17215","Password":"*REMOVED*","IntegratorKey":"*REMOVED*"}
Accept: application/json, application/xml, text/json, text/x-json, text/javascript, text/xml
Content-Type: application/json
Host: demo.docusign.net<http://demo.docusign.net>
Content-Length: 128
Accept-Encoding: gzip, deflate

{
    "authenticationMethod": "email",
    "userName": "Simon",
    "email": "test@email",
    "returnUrl": "http://www.google.com"
}

HTTP/1.1 400 Bad Request
Cache-Control: no-cache
Content-Length: 274
Content-Type: application/json; charset=utf-8
Date: Fri, 24 Jan 2014 12:11:38 GMT
Strict-Transport-Security: max-age=7776000; includeSubDomains

{
"errorCode": "UNKNOWN_ENVELOPE_RECIPIENT",
"message": "The recipient you have identified is not a valid recipient of the specified envelope. Envelope recipient could not be determined. 'clientUserId', 'email', or 'userName' in request and envelope may not match."
}

推荐答案

首先，关于指定顺序收件人，只需为每个收件人设置 routingOrder 属性即可。例如，此示例JSON显示了一个收件人结构，该结构指定John应首先接收信封（ routingOrder = 1），Jane应首先接收信封（ routingOrder = 2）：

First, regarding specifying order of recipients, this is simply done by setting the routingOrder property for each recipient. For example, this sample JSON shows a recipients structure that specifies John should receive the Envelope first (routingOrder=1) and Jane should receive the Envelope second (routingOrder=2):

"recipients": {
    "signers": [
        {
            "name": "John Doe",
            "email": "[email protected]",
            "recipientId": "1",
            "routingOrder": "1",
        },
        {
            "name": "Jane Smith",
            "email": "[email protected]",
            "recipientId": "2",
            "routingOrder": "2",
        }
    ]
}

响应 POST收件人视图请求而收到的 UNKNOWN_ENVELOPE_RECIPIENT错误消息仅表示您所提供的收件人信息没有（完全/完全）匹配任何您指定的信封中的收件人。

The "UNKNOWN_ENVELOPE_RECIPIENT" error message that you're receiving in response to the POST Recipient View request simply means that the recipient information you're supplying doesn't (exactly/completely) match info for any of the recipients in the Envelope you're specifying.

首先，请记住，如果您要使用 POST收件人视图调用检索可用于启动收件人的签名会话的URL，然后 Create Envelope 请求和 POST收件人视图请求都必须包含（相同） clientUserId 收件人的属性值。（您发布的请求JSON不包含 clientUserId 。）

First, keep in mind that if you're wanting to use the POST Recipient View call to retrieve the URL that can be used to launch the recipient's signing session, then BOTH the Create Envelope request AND the POST Recipient View request must include the (same) clientUserId property value for the recipient. (The request JSON you posted doesn't include clientUserId.)

如果在< POST收件人查看请求无法解决您的问题，因此，为了进一步解决问题，建议您对同一信封执行获取收件人调用，并比较收件人属性在响应中，提供您在（不成功的） POST收件人视图调用中提供的属性值。 获取收件人请求非常简单：

If including the clientUserId property in the POST Recipient View request doesn't resolve your issue, then to troubleshoot further, I'd suggest that you execute a Get Recipients call for the same Envelope, and compare the recipient properties in the response with the property values that you're supplying in your (unsuccessful) POST Recipient View call. The GET Recipients request is simply:

GET / accounts / {accountId} / envelopes / {envelopeId} / recipients

这篇关于DocuSign REST API-RecipientView异常“ UNKNOWN_ENVELOPE_RECIPIENT”的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！