mSign Addendum

Effective Date: October 26, 2021

If your Pricing Proposal indicates you have purchased Services related to our mSign product, this mSign Addendum (the “Addendum”) governs your use of such Services, as defined in our Terms of Service (the “Terms”) available at Capitalized terms used and not defined in this Addendum have the respective meanings assigned to them in the Terms. Except as otherwise provided herein, the terms and conditions of the Terms are incorporated in this Addendum as if fully set forth herein.

Service Description

mSign is an electronic signature service which allows you to display, deliver, acknowledge, store, and electronically sign documents. mSign Application Programming Interface (“mSign API”) allows you to easily integrate or embed the mSign electronic signature solution into your application or workflow, creating a clean, and seamless online experience allowing users to complete legally-binding agreements or transaction with your company and/or your customers.


A person signing a document via mSign must either have a mSign account or have received a request for signature in their email account.

Audit Trails

Documents completed in mSign include an audit trail that contains information that helps track your document through its lifecycle. This information includes, but is not limited to, unique document ID generated by mSign, email addresses of the sender and recipient(s), IP addresses of the sender and recipient(s), and track events (such as date, time, and located when the following events occur - document uploaded, document viewed, document removed, document sent, document signed, decline to sign, signer email address updated, signer access code authenticated, signature request cancelled).

mSign API

To the extent that you elect to use the mSign API to enable embedded features, you are required to authenticate the identity of each signer/end user through email confirmation or such other means that we may approval in our sole discretion. You are solely responsible and liable for such authentication and will indemnify, defend and hold us harmless against any claim related to such authentication.

Signature Requests

A “Signature Request” is the transaction that takes place when you initiate a new signature process and make a corresponding call to the mSign APIs. For example, if you call “signature_request/send” to send out documents for signature, this will constitute one (1) Signature Request. Note that a single Signature Request can be used to gather signatures from multiple signers in cases where they are all involved in the same contract.

API Keys

In order to use the mSign APIs, you must obtain your unique API credentials (an “API Key”) via the registration process. Customer is solely responsible for all activity associated with its API Key, regardless of whether you have knowledge of such activity. You must not share your API Key with any third party, you must keep such API Key secure, and you must use it as your sole means of accessing the mSign API.


You can make up to 60 requests per minute for standard API requests, and 8 requests per minute for higher tier API requests. Collectively the above are “Transaction Limits.” Please contact our sales department if you wish to increase your Transaction Limits.

We may be required to limit or suspend your use of the mSign APIs when such suspension or limited are necessary to prevent harm or liability to other customers/individuals, or to preserve the security, stability, availability or integrity of the Services.


Only your websites, applications, or other properties (collectively, “Your Properties”) that have been approved by mSign may access and use the Service. mSign reserves the right to reject any of Your Properties, for any reason, in its sole discretion, including but not limited to ensure that you comply with the Terms. Furthermore, you will ensure that the Your Properties contain terms of service and privacy policies that are consistent with the terms of this Agreement.

API Restrictions

You agree that you will not (and will not permit any third party to) directly or indirectly: (a) create an API client that functions substantially the same as the mSign APIs; (b) make any use of the mSign APIs for any purpose independent of the Your Properties; (c) misrepresent the source or ownership of the mSign APIs or remove, obscure, or alter any copyright, trademark or other proprietary rights notices, falsify or delete any author attributions, legal notices or other labels of the origin or source of the mSign APIs; or (d) interfere with or disrupt the mSign APIs or the servers or networks providing the mSign APIs or Service.

Customer Applications

You may use the mSign APIs to develop applications and/or embedded signing experiences for use by you or your clients and their respective end users (collectively “Customer Applications”). You shall be solely responsible for the Customer Applications and shall ensure you have: a) provided its customers, clients, and end users with the applicable terms (including privacy terms) that authorize us to provide the Services hereunder, and b) the proper authority and/or authorization to share user or signer information (including personally identifiable information) with us.