Trending Topics: Latest From Our Forums (Oct 2019)
Here are some of the latest popular questions that the Docusign developers community asked on Stack Overflow in the month of October 2019.
Here are some of the latest popular questions that the Docusign developers community asked on Stack Overflow in the month of October 2019.You too can ask questions by using the tag docusignapi in Stack Overflow.
Thread: API returning a USER_LACKS_MEMBERSHIP error
https://stackoverflow.com/questions/58243909
Summary: The developer had an integration using JWT that they were taking from the Developer Sandbox (demo) into production (Go Live Process). The developer was only getting the error USER_LACKS_MEMBERSHIP in production while everything was working fine in demo.
Answer: The Developer Sandbox only has a single endpoint for API calls: demo.docusign.net. In production we have multiple endpoints for different locales. Making calls to www.docusign.net may result in this error. To discover the correct baseUrl for your account, you need to call the getUserInfo() method of the eSignature REST API.
Thread: Docusign Connect Webhook with .NET Core 3
https://stackoverflow.com/questions/58440255/
Summary: The developer is building an app using Microsoft .NET Core version 3 that attempts to receive notifications from Docusign using the Docusign Connect Webook. The developer was checking their Connect logs and found they consistently get “The remote server returned an error: (415) Unsupported Media Type.”
Answer: The media type for Connect calls is XML. The developer had to add AddXmlSerializerFormatters() to the ConfigureServices method in Startup.cs instead of services.AddMVC().AddXmlSerializerFormatters() as well as added the [FromForm] attribute to resolve this issue.
Thread: How to fix curl error “Could not resolve host: account-d.docusign.com%2Foauth%2Ftoken” in Docusign API in php
https://stackoverflow.com/questions/58320308
Summary: The developer is building an application using the PHP language and making Curl calls to the API (not using the SDK) and is getting the error about a bad URL as part of the Auth Code Grant authentication flow.
Answer: The URL in question has an encoding issue, as it should be the encoded URL https://account-d.docusign.com/oauth/token; but the code somehow has some of the slashes encoded. The slash character can be encoded within a URL parameter (after the ‘?’ mark) that is passed to an endpoint, but not within the actual URL path itself.
Additional developer resources
Inbar Gazit has been with Docusign since 2013 in various engineering roles. Since 2019 he has focused on developer content. 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 StackOverflow, answering your questions. Inbar can be reached at inbar.gazit@docusign.com.
Related posts
Discover what's new with Docusign IAM or start with eSignature for free
