Trending Topics: Latest from our forums (April 2024)

Inbar GazitSr. Manager, Developer Content and Advocacy

•

Summary•3 min read

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

Additional resources

Additional resources

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

Thread: Allowing "Negotiate Changes" via the Docusign API

https://stackoverflow.com/questions/78272631/

Summary: The developer is attempting to use the document markup feature, which allows signers to negotiate changes to the document inside the envelope. They are getting an error from the API:

{
  "errorCode":"CANNOT_ALLOW_MARKUP",
  "message":"Account does not have permission to set Allow Markup."
}

Answer: Document markup is a premium feature that may not be included in the account plan the developer is using. In the developer account, they should be able to get it enabled for free by contacting the developer support team. For production accounts, they would have to contact their sales representative to enable this functionality.

Thread: Failed to instantiate [com.docusign.esign.client.ApiClient]

https://stackoverflow.com/questions/78243005/

Summary: The developer is using the Docusign eSignature Java SDK. They’re upgrading their integration from Java version 11 to 17 and seeing new errors that they didn’t encounter when using version 11.

Answer: To correctly do this upgrade, the developer had to upgrade their version of the Java SDK, which required additional packages as dependencies. To fix this, they had to add the following section to the pom.xml flag with the new dependencies to allow Java to build their code:

<dependency><groupid>org.glassfish.jersey.media</groupid><artifactid>jersey-media-multipart</artifactid><version>3.0.9</version></dependency><dependency><groupid>org.glassfish.jersey.core</groupid><artifactid>jersey-client</artifactid><version>3.0.9</version></dependency><dependency><groupid>org.glassfish.jersey.media</groupid><artifactid>jersey-media-json-jackson</artifactid><version>3.0.9</version></dependency>

Thread: Error: Access token with Authorization Code Grant

https://community.docusign.com/apis-and-sdks-60/error-access-token-with-authorization-code-grant-3694

Summary: The developer is trying to obtain an access token to authenticate in order to make API calls. They are using Authorization Code Grant and are getting this error:

{
  "error": "invalid_grant",
  "error_description": "unsupported_grant_type"
}

Answer: When using Authorization Code Grant, you first need to obtain an authorization code to be exchanged for an access token. The URL you use for this first step (if using a developer account) looks like this:

https://account-d.docusign.com/oauth/auth?
  response_type=code
  &scope=YOUR_REQUESTED_SCOPES
  &client_id=YOUR_INTEGRATION_KEY
  &state=YOUR_CUSTOM_STATE
  &redirect_uri=YOUR_REDIRECT_URI
  &login_hint=YOUR_LOGIN_EMAIL

If you omit response_type=code from the request, you’ll get the error above.

Additional resources

Inbar GazitSr. Manager, Developer Content and Advocacy

Inbar Gazit has been with Docusign since 2013 in various engineering roles. Since 2019 he has focused on developer content and advocacy. Inbar works on code examples including the launchers, available on GitHub in eight languages, and helps build sample apps showcasing the various Docusign APIs. He is also active on Docusign Community and StackOverflow, answering your questions. Inbar can be reached at inbar.gazit@docusign.com.