Security News
Research
Supply Chain Attack on Rspack npm Packages Injects Cryptojacking Malware
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
hellosign-embedded
Advanced tools
A library which allows you to embed HelloSign signature requests and templates from within an application.
Welcome!
HelloSign Embedded is a JavaScript library which allows you to embed HelloSign signature requests and templates from within a web application.
For more information, review our API documentation.
Contents
Via npm
$ npm install hellosign-embedded
Via CDN
<script type="text/javascript" src="https://s3.amazonaws.com/cdn.hellosign.com/public/js/hellosign-embedded.LATEST.min.js"></script>
This will always use the latest published version of the library. Alternately, omit the .min
for the development version.
<script type="text/javascript" src="https://s3.amazonaws.com/cdn.hellosign.com/public/js/hellosign-embedded.LATEST.js"></script>
And if you'd prefer to use a specific version of the HelloSign Embedded library, you can specify its version in the URL.
<script type="text/javascript" src="https://s3.amazonaws.com/cdn.hellosign.com/public/js/hellosign-embedded.1.2.11.min.js"></script>
We recommend using the latest version of the library so that you'll receive security and feature updates, however be aware that if any breaking changes are introduced, your app may need to be updated to support them.
First you'll need an API key and Client ID. If you haven't done so yet, head on over to the API settings for your account on HelloSign and create an API App.
Import the library into your frontend app. The below example is using ES6 module imports.
import hellosign from 'hellosign-embedded';
If you have installed the library from our global CDN, it will be available at window.HelloSign
.
const hellosign = window.HelloSign;
Initialize the HelloSign Embedded client with your API app's client ID.
const CLIENT_ID = '0123456789abcdef0123456789abcdef';
hellosign.init(CLIENT_ID);
Use your HelloSign SDK of choice to create an embedded signature request and get the signing URL. An example of how this is done using the NodeJS API can be found in the demo in this repository.
Then, open the signature request.
hellosign.open({
url: signUrlFromSdk,
allowCancel: true,
debug: true,
skipDomainVerification: true,
uxVersion: 2
});
A list of available options can be found in the documentation for the open()
method below.
More information and examples can be found in the Embedded Signing Walkthrough in the official HelloSign API docs.
hellosign.init(clientId)
Initializes the HellSign embedded library with the given client id.
Parameters
clientId String
Your API app's unique client id.
hellosign.open(options)
Opens an embedded signature request in an iFrame with the given options.
Parameters
options
Object
Options to send to the hellosign.open()
method.
url
String (required)
The signature request URL to open in the embedded iFrame.
requester
String (required*)
The email of the individual issuing the signature request. This option is required only for "Me and Others" signature requests.
uxVersion
Number (recommended)
An integer representing the version of the embedded signing UX to display to users, where 1
is the legacy UX and 2
is the responsive UX. If you are a new HelloSign API customer, it is recommended that you specify uxVersion: 2
.
Note: This option is only honored if your account has accessed the API prior to Nov 14, 2015. Defaults to 1
.
redirectUrl
String
A URL pointing to where to redirect to after the embedded signature request has been completed by the user.
allowCancel
Boolean
A boolean indicating whether or not a "Cancel" button is displayed to the user. Defaults to true
.
messageListener
Function
A function which is called when window messages are received from the embedded iFrame. See window.postMessage()
. The callback passes the following as arguments:
message
Object
message.event
String - The event that was sent from the embedded iFrame. A list of possible message events can be found here.userCulture
String
The code for the language/culture to use in the embedded request. Use hellosign.CULTURES.supportedCultures
to view a list of supported culture codes.
debug
Boolean
Enable debugging statement in the console. Defaults to false
.
skipDomainVerification
Boolean
Skip domain verification if and only if the signature request was created with test_mode=1
. Defaults to false
.
container
HTMLElement
An HTML element in the DOM which the embedded signature request iFrame will be appended to. Defaults to document.body
.
height
Number
The height of the embedded signature request iFrame in pixels, when a specific container is specified. Minimum height allowed is 480
. Defaults to 900
.
healthCheckTimeoutMs
Number
An integer representing the number of milliseconds to wait for a response from the embedded signature request iFrame. If there is no response in that time, the iFrame will be closed automatically. 15000
is a recommended timeout. If this option is not specified, the embedded signature request will not close if idle.
hideHeader
Boolean
A boolean indicating whether or not to hide the signature request header. Only customers with embedded branding enabled are able to use this option. Defaults to false
.
whiteLabelingOptions
Object
An object used to customize the signer experience for premium users with white-labeling capabilities.
hellosign.close()
Closes the embedded signature request.
There is a demo app available in this repository which is useful for examining how a simple HelloSign Embedded integration can work. To get it up and running, perform the following:
Clone this repo.
$ git clone git@github.com:HelloFax/hellosign-embedded.git
Run the setup script.
$ npm run setup
Start the demo.
$ npm run demo
If all has gone well, you should now be able to access the demo at http://localhost:3000.
In order to test out the demo, you'll need an API Key and Client ID for HelloSign's API. If you haven't done so yet, head on over to the API settings for your account on HelloSign and create an API App.
TypeScript bindings for HelloSign Embedded are available in the DefinitelyTyped repo.
Copyright © 2018 HelloSign. All rights reserved. Contact us.
FAQs
Embed HelloSign signature requests and templates from within your web application.
The npm package hellosign-embedded receives a total of 70,220 weekly downloads. As such, hellosign-embedded popularity was classified as popular.
We found that hellosign-embedded demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.
Security News
Sonar’s acquisition of Tidelift highlights a growing industry shift toward sustainable open source funding, addressing maintainer burnout and critical software dependencies.