Trending Topics: Latest from our forums (December 2020)

Trending Topics

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

Thread: “The validation of the PDF file failed.” When trying to send a generated PDF via email - Docusign

Summary: The developer is getting an error trying to update an envelope document using a Base64-encoded PDF which was stored in Google Drive. The error message says, “PDF_VALIDATION_FAILED”. Uploading the file manually via the Docusign web app works fine. 

Answer: The developer took two steps to get his document from Google Drive into Docusign. They first used the Google API to get the bits to the server, and then used the Docusign eSignature REST API to update an envelope. The issue was on the first step, where they used a stream option instead of an arrayBuffer. The file should be Base64-encoded when sent to Docusign unless you're using the binary upload option. 

Thread: Not accessible 'Side' field in Docusign Rooms API

Summary: The developer is using the Docusign Rooms API and is trying to determine what is the transactionSideId of a room. Each room in Docusign Rooms for Real Estate has a “side” (buy/sell/list/refinance), which is used to identify what side in the transaction is being represented by this room. The developer was looking for a way to get this information using the Rooms API.

Answer: As of December 2020, the Docusign Rooms API does not yet have an endpoint that includes this information. A ticket was created to request this functionality, and we believe it will be added sometime in the future. Check back on the thread for an update. A workaround exists if you know the userId for the room’s owner. You can call the /v2/accounts/{accountId}/rooms/{roomId}/users endpoint, which includes the transactionSideId for the room based on its owner. 

(Note: as of December 2020, there’s not yet a way to identify the owner of a room or its userId, and this functionality was also requested from the product group).

Thread: Received certificate error message when returning to redirect URI in Docusign API

Summary: The developer is using Oracle Application Express to build an integration using the Docusign eSignature REST API. They are getting the following error: ORA-29273: HTTP request failed ORA-06512: at "SYS.UTL_HTTP", line 1130 ORA-29024: Certificate validation failure

Answer: The error indicates that the Oracle server is unable to validate the certificate for the HTTP call. To resolve this, you must install root certificates on your Oracle servers that are going to be used for this integration. Using the list of Docusign public certificates, the DBA can download the Docusign Digicert and install it on the Oracle servers. 

If you are still receiving a TLS error, you may need to use a tool such as WireShark to inspect and read the trace file, which may indicate the root cause. Remember, you have to use TLS version 1.2 or higher.

Additional resources

Inbar Gazit
Inbar Gazit
Sr. Manager, Developer Content