https://community.appian.com/discussions/f/integrations/4603/we-are-using-call-web-service-to-call-docusign-wsdlWe are using Call Web Service to call Docusign WSDL &quot; demo.docusign.net/.../dsapi.asmx . Passing HTTP header values as HTTP Header Keys {&quot;X-DocuSign-Authentication&quot;, &quot;Content-Type&quot;} HTTP Header value {&quot;&lt;DocuSignCredentials&gt;&lt;Username&gt;xx@xx.com&lt;/Usernameen-USTelligent Community 12https://community.appian.com/thread/18154?ContentTypeID=1Thu, 21 May 2015 22:25:52 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:96d4b946-0718-4842-964c-a2fa85363043kevinb382Thanks for the response. We actually got this same error using the wrong port for our endpoint so it was kind of a red herring for us. Glad you got it figured out.<div style="clear:both;"></div>https://community.appian.com/thread/18153?ContentTypeID=1Thu, 21 May 2015 22:24:04 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:5853c737-5c50-46f7-bcec-5ac0347a91c5ankushjYou don&#39;t need to pass Content-Type in header key and corresponding value in header value. It will work with X-DocuSign-Authentication only<div style="clear:both;"></div>https://community.appian.com/thread/17969?ContentTypeID=1Mon, 18 May 2015 20:58:46 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:29574ab2-9048-4cb8-b88e-2b96fd2ca333kevinb382Did you guys ever figure this out? We&#39;re encountering the same issue.<div style="clear:both;"></div>