I'm using the DocuSign API to POST to the Post Recipient View URL.
I receive a response URL, but if I follow the URL it tells me: ...?event=ttl_expired.
Example URL: https://demo.docusign.net/Signing/startinsession.aspx?t=66e01470-4fcb-xxxx-xxxx-2f9029036d21
I'm using the URL within seconds, so is there a reason I'm getting this error?
TTL does indeed refer to "Time to Life" so if you're getting that error and you're positive it's within the 5 minute TTL window (2 seconds sounds well inside :]) then I would guess one of three things:
You're requesting a signing URL on an invalid envelope (ie you're not the sender or do not have rights on it)
You're requesting for a recipient that is not properly embedded.
You're requesting on a completed envelope or other terminal state (like voided).
Please confirm it's not one of these 3 things causing your error.
Related
I tried calling DocuSign sales and support (transferred around 3 times) and no one could give me a straight answer on this. Their "support" actually told be to try stackoverflow, so here I am...
I'm looking at their API pricing levels here: https://www.docusign.com/products-and-pricing/api-plans-b
If I have the Intermediate API, can I make the following API requests?
GET /restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents/{documentId}
GET /restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/form_data
The part that's throwing me for a loop is the DocuSign Connect feature in the Advanced API plan. The description of it is:
The DocuSign Connect module lets you configure webhooks for envelope events and recipient actions for some or all users in your account. It can also be used to transport the completed documents back to your app or website and to retrieve any form field data entered by your recipients.
I don't need the webhooks, but I need to be able to get the completed documents as PDFs and get the form field data. Do I really need the DocuSign Connect feature for that?
You will be fine with the intermediate plan. Here is the basic distinction between polling and Connect - With Connect, we will proactively notify YOU when key envelope events occur.
Otherwise, it's up to you to call GET /envelopes and/or GET /form_data to retrieve that information. Be wary of the resource limits when you poll.
As a quick aside, instead of making two requests to retrive that information, just make one - GET /envelopes?include=recipients,tabs. This will provide you all the information you seek in one request.
The important excerpt from that guide:
You may not exceed one GET request per unique envelope endpoint per 15
minutes. If you exceed this limit the request will not fail, but it
will be flagged as a violation of rate limits which can cause your app
to fail review to go-live review.
For example, the following transactions violate API rules due to the repeated GET requests to the first document and second recipient:
[12:00:00] POST /accounts/12345/envelopes
[12:01:00] GET /accounts/12345/envelopes/AAA/documents/1
[12:02:00] GET /accounts/12345/envelopes/AAA/recipients/2
[12:03:00] POST /accounts/12345/envelopes
[12:04:00] GET /accounts/12345/envelopes/AAA/documents/1 *
[12:05:00] GET /accounts/12345/envelopes/AAA/recipients/2 *
However, the following set of requests comply with API rules and limits and would not be flagged by the platform:
[12:00:00] POST /accounts/12345/envelopes
[12:01:00] GET /accounts/12345/envelopes/AAA
[12:16:00] GET /accounts/12345/envelopes/AAA
[12:17:00] GET /accounts/12345/envelopes/AAA/documents/1
[12:32:00] GET /accounts/12345/envelopes/AAA/documents/1
[12:40:00] PUT /accounts/12345/envelopes/AAA/recipients/1
[12:41:00] PUT /accounts/12345/envelopes/AAA/recipients/1
I'm performing a DocuSign integration with a FileMaker solution to send signature requests via email, and receive a copy of the signed document once completed. I'm using the Java SDK to email signature request, as well as a Javalin app process to listen for the completed signature event, as well as more Java to pull the document back into FileMaker.
When the completed document is sent to my listener and pulled in, the document lacks a signature and tab field. It essentially looks just like the pdf document before being sent.
I have a feeling there's a variable I can tweak in some object to allow the signature to appear after being signed. I've played with all the usual suspects (e.g., eventNotification.setIncludeDocumentFields("true")), but nothing seems to do the trick. Any hints?
Aside from looking through the code for every object I'm instantiating and trying different variations, it's hard to pinpoint the exact source of failure in this. Thanks for any leads!
Sounds like you're receiving notifications by either including the eventNotification object in your Envelopes::create call or are using Connect at the account level. Either way, that's great, that's exactly right.
You can request notifications at many different points along the processing route of the envelope. To receive signed documents, you'll want the notification when the envelope is completed. At that point all signer recipients have signed.
To receive the notification when the envelope is complete, either adjust your Envelope Send parameters (the eventNotification value) or the settings for Connect (via the Admin tool), whichever one you're using.
Q: Anyone know any working method, or alternate URL, to create an Authorize.Net Sandbox Account?
After filling out the Sandbox Account form at, https://developer.authorize.net/hello_world/sandbox/ , I received the error message:
URL: https://developer.authorize.net/hello_world/sandbox/
Complete Page Body:
ERROR
The request could not be satisfied.
This distribution is not configured to allow the HTTP request method that was used for this request. The distribution supports only cachable requests.
Generated by cloudfront (CloudFront)
Request ID: eA28WPE73_KAV2p91ixOhETSVWssiFeOdvnr0az40wxLVIT2bDBhBw==
==EOF==
Edit 2017-12-04:
While not an answer to my question (which may be “There is none.”), I ‘mis’-used Authorize.Net’s contact form to request a manual account creation. As opposed to the ~2 days they give for reply ETA, the above form was ‘fixed’ and they replied, “I just tested the page and I could not recreate the error” within ~5 hours.
I’ll leave the question open for a week in case someone knows an answer, and afterwards close it with ‘None.’
Using the API, I generate the document and place my tags. User goes to sign and decides to finish later. It passes an event="cancelled" to my callback. I make note in my system that they cancelled it. But how can I get them back to the form later? There is no "authentication" with this. I do all the authentication on my end. So I need a URL to send them back to. Using the URL the api gives me to load in iframe expires. So how do I sent them Back to document?
I use PHP by the way.
Here are 2 possible causes (there may be others):
A 'Signing ceremony UX URL' has a short time to live (300 seconds or less I believe) so ensure you are making the call to retrieve a URL right when the user intends to perform the signing session.
A 'Signing ceremony UX URL' can only be rendered once. Verify that you are in fact retrieving a new URL each time and not reusing the original URL.
See this recipe from the DocuSign Developer Center. Repeat step 3 to retrieve a new URL to present to your user.
When making a request for a document through the Rest 2.0 API, I receive the error response:
{
"errorCode": "UNSPECIFIED_ERROR",
"message": "Sign or Initial or Signer Attachment Image not set for recipient {recipGUID}"
}
(actual GUID replaced)
The URL being accessed to get the document is
https://na2.docusign.net/restapi/v2/accounts/5689423/envelopes/{guid}/documents/1?show_changes=true
The envelope in question contains one signer, with one signature and one signer attachment, both of which are filled out. The only recipient shows a correct signedDateTime value, indicating that it was signed and completed. When I view the document in docusign, I see both the signature image, as well as the attachment as the second page of the document.
This method has worked well for hundreds of other envelopes, but a small few seem to be giving me this message, even though it looks from my side like those documents are actually completed.
This bug will be resolved on the next release to Production, I will update this post when that has been completed.
Update:
This was fixed earlier this year and should no longer be an issue.