|
In March 2017, the most popular recipes were
Using a webhook to track envelope status,
Signing from Your App, and
Request a signature via email using a template.
The top visited pages in the Developer Center included
API Documentation,
recipes,
embedding,
tabs, and
templates.
Traffic to the Developer Center is the highest in the United States, followed by Canada, UK, Australia, India, France, and Brazil.
The top trending topics on Stack Overflow for the docusignapi tag are determined based on views and/or comments on specific threads. Here are the top three most frequently asked or viewed questions and answers:
Thread: DocuSign - Sending to Multiple Recipients
Summary: Using the eSignature API, the poster receives a [400] Error connecting to the API error when sending to multiple recipients.
Answer: The original poster was kind enough to return to the thread because it was self-answered. The poster discovered that the setRoutingOrder property must be set for the Signer.
Thread: Docusign: Can carbon copy recipients receive a notification when Signer views the envelope
Summary: As the thread title suggests, the poster is trying to determine if a "cc" recipient can receive notifications when a signer views the envelope.
Answer: The poster was advised about the conditions under which a recipient receives a notification. Please review the thread for more info.
Thread: How do I set the ttl on a docusign envelope URL?
Summary: The poster wants to better understand how Time-To-Live (TTL) is set on DocuSign envelopes.
Answer: The TTL value on DocuSign envelopes is fixed at five minutes. However, our own Larry Kluger presents the poster with a way to manage that in the custom app.
|