...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
You can modify the message and also the language of the SMS OTP sent via API. The easiest way is to call the GetAdHocWorkstepConfiguration_v1 to recive a default workstep for the document or you can modify it directly via API (see example below). Following Three 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) 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.
|
...
Expand | ||
---|---|---|
| ||
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. |
...