I found this thread: Office 365 Rest API read the In-Reply-To field, but there is no follow up on what happened with this request (or at least I can't find any).
I need to know what is the In-Reply-To header for a reply Draft message, so I can send it through the API.
Related
We are using the DocuSign SDK (version 3.3.0) and utilizing webhooks to receive the various envelope and recipient events.
In the envelope, I need to retrieve the fields (status_changed_date_time and last_modified_date_time) in the XML message from the DocuSign Connect. But I identified that those fields are not being sent in the XML message.
Is there any way to include those above mentioned fields in the XML message from DocuSign connect?
The XML notification body is what it is. If it doesn't include the data your application needs, then make additional API calls to DocuSign to obtain the data you want. Doing so is a common pattern.
Note: It is important that you respond to DocuSign with a 200 status right away--all your processing should be done asynchronously on a different thread. Don't delay your 200 response.
When i check format of XML notification for Docusign Connect event - i observe signed field for recipient which contains date time of signment.
When i check REST API for envelope recipients i see that signedDateTime for recipient is Reserved for DocuSign.
https://developers.docusign.com/esign-rest-api/reference/Envelopes/EnvelopeRecipients/list
Why in one place it is available while in another - it is not?
Does REST API is something newer than XML event?
What is the most correct way to determine signment date for each recipient?
making a call to get recipients using the DocuSign eSignature v2.1 API would include this data
See here
https://developers.docusign.com/esign-rest-api/reference/Envelopes/EnvelopeRecipients/list
GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}/recipients
Check the info for dateSigned inside the json
We are using DocuSign Rest API from our Pega application. There is a scenario where we have to delete a particular recipient, and the restful service for this functionality is an HTTP DELETE which expects a message body (JSON format).
But Pega has certain limitation in sending message body for HTTP DELETE requests and hence we are now unable to hit the DocuSign Rest API for Delete Recipient.
API for Docusign
Pega provides some workaround in such scenarios where there is a message body required for DELETE operations.
Can you please let me know if DocuSign provides an alternate way to invoke the service without a message body? We want this information to decide if we need to go the Pega way or DocuSign way to fix this issue.
You can delete the recipient by specifying the recipientId in the URL.
See deleteEnvelopeRecipients api
DELETE /v2/accounts/{accId}/envelopes/{envId}/recipients/{recipientId}
The api you are using is deleteListEnvelopeRecipients
Use deleteListEnvelopeRecipients api if you want to delete multiple recipients in a single call. You will have to specify the HTTP body for this call.
So I'm using REST API for my DocuSign handling, and I have this snippet that checks every 30 mins the status of each envelope, but I'm having hard time find out if there is a way to trigger response (i.e. email) as soon as someone signs the document?
Yes, the DocuSign REST API includes a webhook facility that you can use. When you call Envelopes:Create, include an eventNotification object. In that object you include an internet-accessible URL.
The DocuSign platform will then make HTTPS POSTS to your URL when there is an interesting status change to your envelope. (You define "interesting" status changes as part of the eventNotification object.)
See the eventNotification section in the docs.
I'm able to create an envelope with the API which returns the envelopeId which looks like:
13f23354-7eee-41d3-897a-c1353a1e465c
When I navigate to docusign in my browser and open the envelope the url is:
https://na2.docusign.net/MEMBER/EnvelopeSetup.aspx?ti=ad05458248c54654a16a54195bf72ffe
I don't see what that "ad05458248c54654a16a54195bf72ffe" id is. I've tried every envelope API in the documentation (many don't make sense, but I tried them anyways):
/accounts/{accountId}/envelopes/{envelopeId}
/accounts/{accountId}/envelopes/{envelopeId}/audit_events
/accounts/{accountId}/envelopes/{envelopeId}/custom_fields
/accounts/{accountId}/envelopes/{envelopeId}/email_settings
/accounts/{accountId}/envelopes/{envelopeId}/notification
/accounts/{accountId}/envelopes/{envelopeId}/templates
But that id isn't anywhere.
Is there a way to retrieve that URL id? and/or is there another way I can get the url for the envelope?
The ID that appears as part of any URL when you're using the DocuSign web console is an internal ID -- you cannot use it with the API in any way. The Envelope ID value that DocuSign returns in response to the "Create Envelope" API request is the ID that you'll want to use with any API request that requires an Envelope ID.
It's not exactly clear to me what you mean by "[url for] managing an envelope" -- but I'd suggest you explore the following operations in the DocuSign REST API Guide:
Post Envelope Correction (page 146)
Modify or Correct and Resend Recipient Information (page 137)
Post Sender View (page 149)
(I'd guess that "Post Envelope Correction" is likely what you're after.)