The Migration Guide helps you if you want to switch from SOAP to REST API. In addition to all the differences between the individual calls, this guide also contains detailed information corresponding on the significant differences (structure, syntax and semantic) between SOAP and REST that will help you with your integration transition.
First the endpoints are different
One REST endpoint (base URI):
You can find the latest version here: https://demo.esignanywhere.net/Api
The names of the api calls are different:
* api calls from the following endpoint: https://demo.esignanywhere.net/api.asmx?WSDL
** api calls from the following endpoint: https://demo.esignanywhere.net/UserManagementApi.asmx?WSDL
*** api calls which are offered by both endpoints
Api calls which are only available with SOAP:
Api calls which are only available with REST:
Apart from the different endpoints and the fundamental changes in the syntax (from XML to JSON), there are also the following significant changes if you switch from SOAP to REST.
For this changes please also have a look at the postman tutorial: https://www.esignanywhere.net/esignature-api/tutorial-hello-world/esignanywhere-api-postman-sample/
In the next section you can find a sample for the fundamental changes in the syntax:
The authentication section in SOAP:
would look like the following in REST:
In REST the authentication is transferred in the header. In SOAP there is a separate section for the authentication.
Upload a File
In REST, files are sent as HTTP POST with multipart/form-data encoding of the JSON in the POST body. In SOAP you have to BASE64 encode the file and then you have to add the encoded file in the api call.
In SOAP the signature fields are in the section signatureTemplate in REST the signature fields are in the section Tasks. You can find a sample for REST and SOAP in the next section. This sample includes a Click2Sign a Draw2Sign and a Type2Sign.
Note (Only in SOAP): For every interactive field(signature field, text field, checkbox etc.) you have to add a workstep task.
For example for the three signature fields above you would have to add three tasks within the WorkstepTasks section:
In REST the task is already given in the configuration when the signature field is added.
You can send the metadata within the workstep configuration in REST. For the metadata please use the XML format. You can find a sample in the next section.
SOAP to REST proxy
You can of course continue to send all SOAP calls in the future. To do this, you would have to implement a proxy to transform the SOAP calls into REST calls. Please see the next figure for more information: