Versions Compared

Old Version 24

changes.mady.by.user Unknown User (gierlinger)

Saved on

compared with

New Version 25

changes.mady.by.user Unknown User (gierlinger)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

eSignAnyWhere can be easily implemented. This tutorial shows you how to send your first envelope via api REST service of eSignAnyWhere. If you are using Postman for your REST calls please also have a look at the following Tutorial: Visit postman tutorial.
Please also see the developer mode for this tutorial: Visit developer mode.
For this tutorial you can use your desired programming language (with REST support) or any REST tool (e. g. Postman). Moreover you will need an active eSignAnyWhere account for the authorization. (Even a trial account will work).

If you want to use SOAP for your API calls you can use SoapUI. For this tool you can find a tutorial here: Visit SoapUI Sample. For SOAP you might be also interested in the envelope XML guide which explains you more about the XML configuration.

...

You can either authorize with the organizationKey and the UserLoginName or you can use the apiToken for the authorization. For more informtaion about the two different authorizations please have a look at the Postman Tutorial

Expand
titleAlternative: SOAP implementation (deprecated)

The authorization XML has to be encoded via HTML special characters (“<” in “&lt;” and “>” in “&gt;”). If this encoding is not done you will receive a HTTP 400 Bad Request error.
Higher programming languages takes automatically care of the conversation, so just in lower languages it is required (or also SOAPUI). You can find a configuration for the authorization for SOAP (XML) in the next lines:

Note: The next lines show a authorization with the organizationKey and the userLoginName.

Code Block
languagexml
themeEclipse
firstline0
<authorization>
	<organizationKey>4647688a-xxxx-xxxx-xxxx-xxxxxxxx</organizationKey>
	<userLoginName>your@email.address</userLoginName>
</authorization>

Inline-XML (with HTML special characters):

Code Block
languagexml
themeEclipse
firstline0
&lt;authorization&gt;
&lt;organizationKey&gt;4647688a-xxxx-xxxx-xxxx-xxxxxxxx&lt;/organizationKey&gt;
&lt;userLoginName&gt;your@email.address&lt;/userLoginName&gt;
&lt;/authorization&gt;

You can also authorize with the apiToken. Please see the following configurations:

Code Block
languagexml
themeEclipse
firstline0
<authorization>
	<apiToken >hizit4enf8ellb6b5hwh5b------------------------------</apiToken >
</authorization>

Inline-XML (with HTML special characters):

Code Block
languagexml
themeEclipse
firstline0
&lt;authorization&gt;
	&lt;apiToken &gt;hizit4enf8ellb6b5hwh5b------------------------------&lt;/apiToken &gt; 
&lt;/authorization&gt;


...

For more information about the process of finding the template and send an envelope from the template please also have a look at the template use case.

If you have not finished the envelope then search for “Active” envelopes, if the envelope is already finished please search for “Completed” envelopes to find the envelope you have sent in the api call above.
As response from this api call you will get a list of all envelopes which fulfill the status.

...

Info
titleAdditional Information

Depending on the signature method used, it might be necessary or recommended to store additional documents beside the signed document, to ensure having the necessary evidence. For advanced electronic signatures, you might have to store also the audit trail document; and for Namirial Disposable Certificate, also the Certificate Request Form by which the signer requested issuance of the QEC. Those documents can be downloaded using the same method, just with the different file IDs.

Helpful Features and Resources

In this section you find some helpful features or hints you may use after the tutorial.