且构网

分享程序员开发的那些事...
且构网 - 分享程序员编程开发的那些事

DocuSign REST API-RecipientView异常“ UNKNOWN_ENVELOPE_RECIPIENT”

更新时间:2022-03-05 07:23:35

首先,关于指定顺序收件人,只需为每个收件人设置 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": "johnsemail@outlook.com",
            "recipientId": "1",
            "routingOrder": "1",
        },
        {
            "name": "Jane Smith",
            "email": "janesemail@outlook.com",
            "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