EchoSign. You send. They sign. Done.

EchoSign API SOAP Header Information

The EchoSign API uses SOAP over HTTP as the transport protocol. This is something you will typically not need to interact with directly because your SOAP client library will take care of the protocol envelope. However, we present this example of a complete client-server interaction in case you need to write your own implementation for any reason.

The request and response examples referenced on the API methods page show only the SOAP payload, not the HTTP envelope. The envelope shown here is always used around any EchoSign API method call.

For example, if you were calling the testPing method, the complete request would look like this:

POST /echosign/services/EchoSignDocumentService HTTP/1.1
SOAPAction: ""
Content-Type: text/xml; charset=UTF-8
Host: www.echosign.com
Content-Length: 325

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <soap:Body>
    <testPing xmlns="http://api.echosign">
      <apiKey>YOURAPIKEY</apiKey>
    </testPing>
  </soap:Body>
</soap:Envelope>
    

And the complete server response would be:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri, 30 May 2008 23:59:20 GMT

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <soap:Body>
    <testPingResponse xmlns="http://api.echosign">
      <documentKey>
        <message xmlns="http://dto.api.echosign">It works!</message>
      </documentKey>
    </testPingResponse>
  </soap:Body>
</soap:Envelope>