Trending Topics: Latest from our forums (May 2022)

Here are some of the latest popular questions that the Docusign developers community asked on Stack Overflow in the month of May 2022. You too can ask questions by using the tag docusignapi in Stack Overflow.

Thread: Unable to obtain embedded recipient view from Docusign

Summary: The developer is trying to create an embedded signing session for a recipient in one of the envelopes and is getting back an error from the EnvelopeViews: createRecipient API call that says “The recipient you have identified is not a valid recipient of the specified envelope.”

Answer: To generate an embedded signing session, developers have to make a POST call to EnvelopeViews: createRecipient that includes information about the envelope and recipient they’re interested in. The recipient must have a clientUserId set when the envelope was created, and the same clientUserId must be specified in the POST call. The email and userName fields in the JSON for this call must match exactly what was provided when the envelope was created for the same recipient. Any difference between the two would result in the error message that this developer received. See How to request a signature through your app on the Developer Center for a step-by-step guide with code examples in eight different languages showcasing this scenario. 

Thread: Docusign permanent authentication?

Summary: This developer is building an integration with Docusign APIs and is wondering how they can ensure that the users of their application don’t have to log in to Docusign. They want to have a fixed authentication scheme that works indefinitely.

Answer: If you use Auth Code Grant to authenticate your application, then the user has to log into Docusign frequently, and you can use refresh tokens to increase the time before the user has to log in again, but it’s not permanent.

If you use JWT, you only need to get consent once per user (or use administrative consent for the entire account) and then you won't need to have a user log in or do anything else again to obtain a new access token.

Thread: Uploading a Document via the Docusign CLM API

Summary: The developer is using the Docusign CLM API to try to upload a document to CLM and getting an error suggesting that they didn’t use Base64 encoding correctly, even though they did encode the document using Base64 encoding.

Answer: The Content:Upload endpoint of the CLM API requires that the Base64 document is sent as a binary stream in the HTTP request and not as the body of the JSON, as is commonly done with other APIs.

Additional resources

Inbar Gazit
Inbar Gazit
Sr. Manager, Developer Content