Docusignapi RecipientId被docusign更改

Docusignapi RecipientId被docusign更改,docusignapi,Docusignapi,我正在使用docusignapi创建信封。在创建信封的同时,我还传递了签名者列表,并为每个签名者设置了自己唯一的“RecipientId”(GUID)。但当信封被创建并检查收件人(签名者)列表时,发现收件人id一直在更改。我通过的不是“接受者ID” 您能帮助我在创建信封时如何设置自己的“RecipientId”吗 --创建信封请求 { "documents": [{ "documentBase64": "<Base64BytesHere>",

我正在使用docusignapi创建信封。在创建信封的同时,我还传递了签名者列表,并为每个签名者设置了自己唯一的“RecipientId”(GUID)。但当信封被创建并检查收件人(签名者)列表时,发现收件人id一直在更改。我通过的不是“接受者ID”

您能帮助我在创建信封时如何设置自己的“RecipientId”吗

--创建信封请求

 { "documents": [{
                    "documentBase64": "<Base64BytesHere>", 
                    "documentId": "1", 
                    "fileExtension": "pdf", 
                    "name": "lite" 
                }], 
    "emailSubject": "test recipient 2", 
    "recipients": { "signers": [ { "email": "xxx.yyy@xxx.com", 
                                    "name": "xxx yyy", 
                                    "recipientId": "1" 
                                    } ]
                  }, 
    "status": "sent" 
 }
{“文档”:[{
“documentBase64”:“,
“documentId”:“1”,
“文件扩展”:“pdf”,
“名称”:“lite”
}], 
“emailSubject”:“测试收件人2”,
“收件人”:{“签名者”:[{“电子邮件”:“xxx”。yyy@xxx.com", 
“名称”:“xxx yyy”,
“收件人ID”:“1”
} ]
}, 
“状态”:“已发送”
}
--Web钩子响应请参阅收件人Id--


签字人
xxx。yyy@abc.com
xxx yyy
1.
2017-08-29T02:13:33.853
发送
活跃的
011eac75-f2fa-4f57-94df-5aedaxxxxxxx
....

创建信封时,您可以为每个收件人指定唯一的recipientId

这是一个示例请求

Json负载

{
 "emailSubject": "Please sign the agreement",
 "status": "sent",
 "recipients": {
     "signers": [
         {
             "email": "janedoe@acme.com",
             "name": "jane doe",
             "recipientId": 1,
             "routingOrder": 1,
             "tabs": {
                 "signHereTabs": [
                     {
                         "documentId": "1", "pageNumber": "1", "xPosition": "80", "yPosition": "80"
                     }

                 ]
             }
         },
         {
             "email": "johnsmith@acme.com",
             "name": "john smith",
             "recipientId": 2,
             "routingOrder": 2,
             "tabs": {
                 "signHereTabs": [
                     {
                         "documentId": "1", "pageNumber": "1", "xPosition": "80", "yPosition": "180"
                     }

                 ]
             }
         }
     ]
 },
 "documents": [
     {
         "documentId": "1",
         "name": "Contract",
         "fileExtension": "txt",
         "documentBase64": "RG9jIFRXTyBUV08gVFdP"
     }
 ]
}

使用api检索信封中的收件人列表

{
  "signers": [
    {
        "creationReason": "sender",
        "isBulkRecipient": "false",
        "name": "jane doe",
        "email": "janedoe@acme.com",
        "recipientId": "1",
        "recipientIdGuid": "98d60cc3-5f67-46e4-9fc0-ca6bb519f1c9",
        "requireIdLookup": "false",
        "userId": "585b8733-b1a9-4329-87e7-4f20bcde00c2",
        "routingOrder": "1",
        "status": "sent"
    },
    {
        "creationReason": "sender",
        "isBulkRecipient": "false",
        "name": "john smith",
        "email": "johnsmith@acme.com",
        "recipientId": "2",
        "recipientIdGuid": "726bd54d-89ed-41ba-a751-fdb129894b8b",
        "requireIdLookup": "false",
        "userId": "45abe022-ae12-4816-8c42-fd66d207807a",
        "routingOrder": "2",
        "status": "created"
    }
  ],
"agents": [],
"editors": [],
"intermediaries": [],
"carbonCopies": [],
"certifiedDeliveries": [],
"inPersonSigners": [],
"recipientCount": "2",
"currentRoutingOrder": "1"
}

另一种解决方法是使用
recipient.customFields
。这是一个字符串数组:

someEnvelopeSigner.customFields=[yourUUID,somethingElse]
在webhook/事件通知中,它将通过
docusingenvelopeinformation.EnvelopeStatus[0].RecipientStatus[0].RecipientStatus[i].CustomFields来传递,看起来类似于(JSONified格式)

{
“自定义字段”:[{
“自定义字段”:[
“6e45cb20-3953-11ea-b02d-dedef9da77b9”,
“还有别的!”
]
}],
}

您可以分享您的请求吗。@CodingDawg{“documents”:[{“documentBase64”:“,”documentId:“1”,“fileExtension:“pdf”,“name:“lite”}],“emailSubject:“test recipient 2”,“recipients:{“signers:”[{“email:“xxx”。yyy@xxx.com“,”名称“:”xxx yyy“,“recipientId”:“1”}]},“状态”:“已发送”}这也是我正在做的..但收件人id已从docusign更改。当我检索收件人列表时,收件人id将更改为某个GUID。连接响应似乎不包含创建信封期间指定的收件人id。docusign在创建信封时还创建了内部收件人id。您可以使用ap我需要检索收件人id之间的映射。我已更新了我的答案。是的,这是正确的。但当收件人状态更改时我需要它。但现在我可以了,首先我将在创建信封时更新收件人列表。它包含RecipientGuidId,然后当状态更改时,在webhook请求中,我将使用RecipientId作为RecipientGuidId。谢谢你的帮助。
{
 "emailSubject": "Please sign the agreement",
 "status": "sent",
 "recipients": {
     "signers": [
         {
             "email": "janedoe@acme.com",
             "name": "jane doe",
             "recipientId": 1,
             "routingOrder": 1,
             "tabs": {
                 "signHereTabs": [
                     {
                         "documentId": "1", "pageNumber": "1", "xPosition": "80", "yPosition": "80"
                     }

                 ]
             }
         },
         {
             "email": "johnsmith@acme.com",
             "name": "john smith",
             "recipientId": 2,
             "routingOrder": 2,
             "tabs": {
                 "signHereTabs": [
                     {
                         "documentId": "1", "pageNumber": "1", "xPosition": "80", "yPosition": "180"
                     }

                 ]
             }
         }
     ]
 },
 "documents": [
     {
         "documentId": "1",
         "name": "Contract",
         "fileExtension": "txt",
         "documentBase64": "RG9jIFRXTyBUV08gVFdP"
     }
 ]
}
{
  "signers": [
    {
        "creationReason": "sender",
        "isBulkRecipient": "false",
        "name": "jane doe",
        "email": "janedoe@acme.com",
        "recipientId": "1",
        "recipientIdGuid": "98d60cc3-5f67-46e4-9fc0-ca6bb519f1c9",
        "requireIdLookup": "false",
        "userId": "585b8733-b1a9-4329-87e7-4f20bcde00c2",
        "routingOrder": "1",
        "status": "sent"
    },
    {
        "creationReason": "sender",
        "isBulkRecipient": "false",
        "name": "john smith",
        "email": "johnsmith@acme.com",
        "recipientId": "2",
        "recipientIdGuid": "726bd54d-89ed-41ba-a751-fdb129894b8b",
        "requireIdLookup": "false",
        "userId": "45abe022-ae12-4816-8c42-fd66d207807a",
        "routingOrder": "2",
        "status": "created"
    }
  ],
"agents": [],
"editors": [],
"intermediaries": [],
"carbonCopies": [],
"certifiedDeliveries": [],
"inPersonSigners": [],
"recipientCount": "2",
"currentRoutingOrder": "1"
}