We were reviewing the DocuSign integration and found in the C:\Program Files\Laserfiche\Web Import Services\DocuSignConnectService\web.config file the following configuration parameter which appears to specify the URL that LF uses for the DocuSign API:
endpoint address="https://demo.docusign.net/api/3.0/api.asmx" binding="basicHttpBinding" bindingConfiguration="APIServiceSoap" contract="DocuSignAPI.APIServiceSoap" name="APIServiceSoap"
What caught our eye was the hostname in the url, i.e. demo.docusign.net. In reviewing DocuSign's API documentation, it looks like they indicate their production API environment is at www.docusign.net, and indeed the same web service/API appears to be available at https://www.docusign.net/api/3.0/api.asmx.
Our concern is that we're deploying production LF systems that are integrating this feature with a demo (non-production) instance of the DocuSign API. Docusign may not be as concerned about keeping it's demo instance as highly available (uptime) as their production instance, or may make unannounced changes to their demo system, etc.
Was this perhaps an oversight (specifying the demo URL in the config)? Or are we misinterpreting something here?
Just checking - thanks!