Skip to main content
Blog

Trending Topics: Latest from our forums (September 2024)

Author undefined
Sr. Product Manager
•

00:0000:00
3 min read

See how our most popular recent threads on the Docusign Community and Stack Overflow can help you solve your own development issues.

    • Additional resources

    Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow opens in a new tab in the month of September 2024. To make sure we see your questions on Stack Overflow, use the tag docusignapi.

    Thread: How to fill values in a document in DocuSign API?

    https://stackoverflow.com/questions/78957209/how-to-fill-values-in-a-document-in-docusign-api opens in a new tab

    Summary: The developer is using PDF form field transformation to create fields in their envelopes, and they want to pre-fill the values for some of those tabs. Setting the value property in their tab definitions isn’t giving them the results that they’re expecting.

    Answer: To pre-fill tabs that have been created through PDF form field transformation, you need to use composite templates. The code snippet below demonstrates how to do this.

    {
      "compositeTemplates": [
        {
          "compositeTemplateId": "1",
          "document": {
            "documentBase64": "{{document}}",
            "transformPdfFields": "true",
            "documentId": "1",
            "fileExtension": "pdf",
            "name": "Example Agreement"
          },
          "inlineTemplates": [
            {
              "recipients": {
                "signers": [
                  {
                    "email": "example@example.com",
                    "name": "FullName",
                    "recipientId": "1",
                    "defaultRecipient": "true",
                    "tabs": {
                      "textTabs": [
                        {
                          "tabLabel": "dealer_name",
                          "value": "Carrie Customer",
                          "locked": "true"
                        }
                      ]
                    }
                  }
                ]
              },
              "sequence": "1"
            }
          ]
        }
      ],
      "emailSubject": "Testing Transform PDF Fields",
      "status": "sent"
    }
    

    Thread: Is it possible to get JWT access token using single rest API call?

    https://community.docusign.com/esignature-api-63/is-it-possible-to-get-jwt-access-token-using-single-rest-api-call-20411

    Summary: The developer is authenticating with JSON Web Token (JWT) Grant, but they are manually constructing the token and they’re wondering if they can simplify the process in a single API call.

    Answer: While authentication with JWT is a two-step process, the token generation should not be manual. You can and should automate all fields, such as start time and expiration, so there is no manual step involved after it has been set up. With the Docusign SDKs you can use the RequestJWTUserToken method to automate the token generation. You can also do this through the Docusign Postman collection.

    Thread: Docusign 500 error when trying to Create Envelope

    https://community.docusign.com/esignature-api-63/docusign-500-error-when-trying-to-create-envelope-20346

    Summary: The developer is using the C# SDK to authenticate with JWT and, using the access token that they received during authentication, they are able to call the user info endpoint. However, when they try to use the same access token to create an envelope, they receive a 500 error.

    Answer: The developer is authenticating successfully, but they are using the incorrect base path when calling the createEnvelope endpoint. They needed to append /restapi to their base URI in order to call the eSignature REST API. This isn’t necessary when calling the user info endpoint. See Docusign API endpoint base paths for more details on the different base paths for each API in the demo and production environments.

    Additional resources

    Author undefined
    Sr. Product Manager

    Paige Rossi is a senior product manager focused on the developer journey. She shapes how developers discover, learn, build, and adopt Docusign technologies. Her work spans the Developer Center, onboarding, developer tooling, and the cross-platform experiences that help developers move from sign-up to their first successful integration. Prior to her current role, Paige has experience at Docusign creating developer content and connecting with builders as a developer advocate.

    More posts from this author

    Related posts

    • Developer Trending Topics
      Author undefined

    Docusign IAM is the agreement platform your business needs

    Start for FreeExplore Docusign IAM
    Person smiling while presenting