Trending Topics: Latest from our forums (October 2024)
See how our most popular recent threads on the Docusign Community and Stack Overflow can help you solve your own development issues.
Table of contents
Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of October 2024. To make sure we see your questions on Stack Overflow, use the tag docusignapi.
Thread: Automatic Consent for Sending Envelopes with Docusign API in Laravel Application
Summary: The developer has a working Docusign integration using JWT authentication, but they are required to grant consent manually every time an envelope is sent. They are looking to enable automatic consent for all users so the user flow isn’t interrupted when they need to grant consent.
Answer: The solution for this is to obtain admin consent. If all of an app’s users are in the same organization, an admin of that organization can grant consent on behalf of all of those users.
Thread: Create and send multiple Docusign envelopes with a single API call
Summary: The developer is hoping to send multiple envelopes with a single API call. The envelopes each contain different documents and require a different configuration of signer and CC recipients.
Answer: Because the developer requires a different configuration for each envelope, they need to make separate API calls for each envelope. If the envelopes had the same template or configuration, the developer could use bulk sending.
Thread: Focused View with two signers
https://community.docusign.com/esignature-api-63/focused-view-with-two-signers-20984
Summary: The developer wants to create an envelope with multiple recipients and require that the first signer use focused view to sign and the second signer use remote signing to sign via email. They are having a hard time specifying the signing method for each recipient.
Answer: If you want a recipient to use embedded signing or focused view, you need to set the clientUserId property on that recipient. This should be a unique value that can be used to identify the recipient, and the same value will be used when you create the recipient view. The JSON snippet below demonstrates how to set the clientUserId.
"signers": [
{
"email": "'"${SIGNER_EMAIL}"'",
"name": "'"${SIGNER_NAME}"'",
"recipientId": "1",
"routingOrder": "1",
"clientUserId": "'"${UNIQUE_ID}"'"
}
]
If you don’t include the clientUserId property, the recipient will instead receive an email notification to sign with remote signing. The JSON snippet below shows how you may set up the second signer.
"signers": [
{
"email": "'"${SIGNER_EMAIL2}"'",
"name": "'"${SIGNER_NAME2}"'",
"recipientId": "2",
"routingOrder": "2"
}
]Additional resources
Paige has been working for Docusign since 2020. As a Sr. Programmer Writer on the Developer Content team, she writes content and code to help developers learn how to use Docusign APIs.
Related posts
Discover what's new with Docusign IAM or start with eSignature for free
