在请求DocuSign API签名时,电子邮件不发送 [英] Emails not sending when requesting signatures for DocuSign API

查看:212
本文介绍了在请求DocuSign API签名时,电子邮件不发送的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述



从模板开始: https://github.com/wadewegner/docusign-sample/blob/master/src/DocuSign/DocuSignClient.cs# L215



从二进制: https://github.com/wadewegner/docusign-sample/blob/master/src/DocuSign/DocuSignClient.cs#L152



两个工作都很好,我可以看到他们出来签名:





麻烦的是收到要求签名的电子邮件最多是多余的。早在我的测试中,似乎我(主要是)收到电子邮件,但是几天之内,我还没有收到您在上图中看到的任何电子邮件。



我正在使用开发人员沙箱。是否有某种限制?



此外,似乎发送到我注册的另一个电子邮件地址是特别有问题的。有更多的限制吗?



谢谢!



修改:添加额外的信息请求。



请求#1(发布文档):

  POST https://demo.docusign.net/restapi/v2/accounts/892965/envelopes HTTP / 1.1 
X-DocuSign-Authentication:< DocuSignCredentials> ...< / DocuSignCredentials>
接受:application / json
Content-Type:multipart / form-data; border =BOUNDARY
主机:demo.docusign.net
内容长度:91206
预期:100-continue

--BOUNDARY
内容-Type:application / xml; charset = utf-8
内容处理:form-data

< envelopeDefinition xmlns =http://www.docusign.com/restapi>< emailSubject> DocuSign API - 文件上的签名请求< / emailSubject>< status>已发送< / status>< documents>< document>< documentId> 1< / documentId>< name> test.pdf< / name>< / document> ;< / documents>< recipient>< signers>< signer>< recipientId> 1< / recipientId>< email> wade.wegner@gmail.com< / email>< name> Wade Wegner<名称><凸片>< signHereTabs>< signHere>< xPosition位置→100< / xPosition位置>< yPosition> 100℃; / yPosition>< documentId→1< / documentId>< PAGENUMBER→1< / PAGENUMBER> < / signHere>< / signHereTabs>< /选项卡>< /签名人>< /签名人>< /收件人>< / envelopeDefinition>
--BOUNDARY
Content-Disposition:form-data;命名=试验;文件名=检验.pdf; filename * = utf-8''test.pdf

< truncating binary>

REQUEST#2(from template):

  POST https://demo.docusign.net/restapi/v2/accounts/892965/envelopes HTTP / 1.1 
X-DocuSign-Authentication:< DocuSignCredentials> .. < / DocuSignCredentials>
接受:application / json
Content-Type:application / xml; charset = utf-8
主机:demo.docusign.net
内容长度:421
预期:100-continue

< envelopeDefinition xmlns =http: //www.docusign.com/restapi\"><status>sent</status><emailSubject>DocuSign API - 从模板签名请求< / emailSubject>< templateId> 29CB97E5-DCE1-4C14-91A8-A8317BCD29AD< / templateId>< templateRoles>< templateRole>< name> Wade Wegner< / name>< email> wade.wegner@gmail.com< email>< roleName>签名角色< / roleName>< clientUserId> 1·/ clientUserId>< / templateRole>< / templateRoles>< / envelopeDefinition>


解决方案

ClientUserId使收件人成为嵌入式收件人。如果您提供了一个值,那么Doc​​uSign将不会发送电子邮件。期望是要处理与签字人的沟通。这使您可以在自己的网站或应用程序中嵌入签名体验。


I have written the following two methods for sending requests for signatures.

From template: https://github.com/wadewegner/docusign-sample/blob/master/src/DocuSign/DocuSignClient.cs#L215

From binary: https://github.com/wadewegner/docusign-sample/blob/master/src/DocuSign/DocuSignClient.cs#L152

Both work great and I can see they are out for signature:

The trouble is receiving the email requesting the signature is spotty at best. Early on in my testing it seemed I'd (mostly) get the email, but a couple days in and I haven't received any of the emails you see in the image above.

I'm using a developer sandbox. Is there some kind of restriction?

Also, it seems sending to a different email address from the one I registered is particularly problematic. Are there even more restrictions?

Thank you!

Edit: adding additional info requested.

REQUEST #1 (posting document):

POST https://demo.docusign.net/restapi/v2/accounts/892965/envelopes HTTP/1.1
X-DocuSign-Authentication: <DocuSignCredentials>...</DocuSignCredentials>
Accept: application/json
Content-Type: multipart/form-data; boundary="BOUNDARY"
Host: demo.docusign.net
Content-Length: 91206
Expect: 100-continue

--BOUNDARY
Content-Type: application/xml; charset=utf-8
Content-Disposition: form-data

<envelopeDefinition xmlns="http://www.docusign.com/restapi"><emailSubject>DocuSign API - Signature Request on Document</emailSubject><status>sent</status><documents><document><documentId>1</documentId><name>test.pdf</name></document></documents><recipients><signers><signer><recipientId>1</recipientId><email>wade.wegner@gmail.com</email><name>Wade Wegner</name><tabs><signHereTabs><signHere><xPosition>100</xPosition><yPosition>100</yPosition><documentId>1</documentId><pageNumber>1</pageNumber></signHere></signHereTabs></tabs></signer></signers></recipients></envelopeDefinition>
--BOUNDARY
Content-Disposition: form-data; name=test; filename=test.pdf; filename*=utf-8''test.pdf

<truncating binary>

REQUEST #2 (from template):

POST https://demo.docusign.net/restapi/v2/accounts/892965/envelopes HTTP/1.1
X-DocuSign-Authentication: <DocuSignCredentials>...</DocuSignCredentials>
Accept: application/json
Content-Type: application/xml; charset=utf-8
Host: demo.docusign.net
Content-Length: 421
Expect: 100-continue

<envelopeDefinition xmlns="http://www.docusign.com/restapi"><status>sent</status><emailSubject>DocuSign API - Signature Request from Template</emailSubject><templateId>29CB97E5-DCE1-4C14-91A8-A8317BCD29AD</templateId><templateRoles><templateRole><name>Wade Wegner</name><email>wade.wegner@gmail.com</email><roleName>Signing Role</roleName><clientUserId>1</clientUserId></templateRole></templateRoles></envelopeDefinition>

解决方案

The ClientUserId causes a recipient to be an embedded recipient. If you provide a value then DocuSign will not send emails. The expectation is that you are going to handle the communication with the signer. This allows you to embed the signing experience within your own website or application.

这篇关于在请求DocuSign API签名时,电子邮件不发送的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆