...
Note that the text contained in the signer invitation can be defined only in one language, typically the sender language.
Please also see the next table which contains all available placeholders for the message section:
| Placeholder | Description |
|---|---|
| #ContactUrl# | The URL refers to the company’s contact info, which is defined in the organization settings. |
| #EnvelopeMessage# | The message which is defined for the envelope. It may contain the personal message defined per recipient. |
| #EnvelopeName# | The name of the envelope. If not specified differently, it is by default the file name of the first PDF document. |
| #ExpirationDate# | The expiration date of an envelope. The date format is defined in the user account settings. |
| #PersonalMessage# | The personal message for a recipient. It may be included in the general envelope message if it was defined before. |
| #RecipientEmail# | Email address of the envelope recipient. |
| #RecipientFirstName# | First name (given name) of the envelope recipient. |
| #RecipientLastName# | Last name (surname) of the envelope recipient. |
| #SenderFirstName# | First name (given name) of the envelope sender. |
| #SenderLastName# | Last name (surname) of the envelope sender. |
| #SupportUrl# | The URL refers to the company’s support website, which is defined in the organization settings. |
| #Url# | The context specific URL used in a link button to execute an action (e.g. URL for Login, URL to open an envelope, URL to download documents, etc.). |
| #UrlAndroid# | The URL to open a signing request in the Significant App Client Signature Capture for Android. |
| #UrlIos# | The URL to open a signing request in the Significant App Client Signature Capture for iOS. |
| #UrlWindows# | The URL to open a signing request in the Significant App Client Signature Capture for Windows-Store. |
| #UserFirstName# | First name (given name) of a user, who is either the web UI user or the envelope sender(depending on the context). |
| #UserLastName# | Last name (surname) of a user, who is either the web UI user or the envelope sender(depending on the context). |
Meta Data Section
The metadata section allows to set meta data in free-text format, which are accessible for an integration e.g. in a Callback Handler. We recommend (but do not enforce) to fill the data with a valid XML structure.
...