eSignAnyWhere offers you an SOAP and a REST interface. It uses authentication and XML for the datastructures. See our API documentation for the basic information about our interfaces. Most programming languages offer you simple SOAP/REST interfaces moreover for the beginning you may start with SoapUI, a webservice testing tool. |
There are two possibilities to customize the UI
|
You can configure email templates and languages for your eSignAnyWhere signers. It may also helpful if you have a look in the user guide settings section. |
There is an envelope XML guide available. |
You can prefill PDF form field with values via API. The following API methods are supported:
XML Configuration for prefill PDF forms:
|
Yes, just add two ore more documents within the tag in the API call SendEnvelope_v1:
After this configuration you can send an envelope as usual but with multiple documents. |
First you have to create a draft ( XML Configuration
The option The designer can be embedded by modifing the following string: http://www.significant.com/AgentRedirect/index?draftid=#envelopeid# If the draft is finished you can start the envelope. |
If you don’t want to send an email to a specific recipient, you just have to add the following configuration to the envelope XML ( Simple Example:
|
eSignAnyWhere it calling the Callback URL 30 times. With the timeout this should be enough to recover if the called system is down for a few minutes. |
You can modify the message and also the language of the SMS OTP sent via API. Following types can be defined (inclusive max character length - GSM-7 (3GPP TS 23.038 / GSM 03.38) standard):
Please note the following: The tag {tId} (Transaction ID) and {Token} (Token) must be defined in the message. If you do not define a language attribute, this will be used as fallback or specified language or recipient does not exists. Please see the following sample configuration for an otp signature:
The easiest way to implement the TransactionCodeConfiguration in SOAP is to call the GetAdHocWorkstepConfiguration_v1 to receive a default workstep for the document or you can modify it directly via API (see sample below).
|
If you have a finished envelope (all recipients finished) and the state of the evelope is still “in Progress”, the reason could be the post processing (the callback). The callback expects a HTTP 200 and if an error is retured it tries to call the callback after some time again (up to 30 times). This could delay the “finished” or “error” of the envelope. |
The problem is, that the envelope is not yet in the correct status. You have to wait until the status is “InProgress”. Another option would be to either…
Then the link will be generated immediately when calling SendEnvelope_v1. If you use regular notifications (emails), the link is sent to the recipient as soon as the Workstep is ready. |
You can define a reading task, so that the signer has to confirm the reading of the envelope. Details about the configuration you find in the Reading Task Guide. |
Yes, you can store your own meta data in the envelopes.
The |
|
eSAW supports to send out links for the SIGNificant products automatically via notifications. Therefore you just have to add to the recipient configuration (XML) the following parameters:
Otherwise you can connect one workstep of eSignAnyWhere with one of the SIGNificant Apps. First you call the https://demo.xyzmo.com/workstepredirector/sign?identifier=8WNDxmUVr5V/aV1AAN49xjKuVsHMQEIQVuM/ktLNw1jOfWgaovF2mDg3uW9JJbp5Q/k7Yz92eoo=&responseType=returnWorkstepId With this WorkstepId you can now connect the SIGNificant product to the document. If the document is finsihed the workflow continues automatically. Other parameters are:
|
If you want to get a callback on specific events, e.g. when a signer rejects the agreement, you can use the following guide. |
If you upload a PDF/A document to eSignAnyWhere it stays through the workflow a PDF/A valid document. If you are starting with a non-PDF/A document, the final document will be also a non-PDF/A document. |
Yes, you may use our SigStrings to place signature fields in documents. You just have to type a string (the simplest version: If you want to use more complex tags (e.g. for form fields, radio buttons, etc.) you may be interested in our advanced tags. This can be found in our Placeholder Use Case and moreover a look into the PrepareSendEnvelopeSteps_v1 function. This function can be helpful for integrations. |
This is typically caused by an outdated Adobe Reader with not update-to-date certificates. Please install a new version or perform an update of the certificates (Settings > Trust Manager > Update AATL/EUTL). |