Welcome to developing with DocuSign.
I'm Mei Hseih, a member of the developer center team.
In this screencast, I'll walk through installing and running
the Node Quickstart on Windows and the embedded signing code
example.
The prerequisite to this video is a Quickstart ZIP file.
If you haven't yet downloaded your Node Quickstart,
please follow the steps in the Quickstart Overview page or the
How to Download Quickstart video.
Quickstart is a software wizard that packages a personalized
code example launcher.
You can choose from eight programming languages.
The Quickstart wizard configures an app
in the developer's DocuSign account
that can make API calls.
These steps are completed for the developer.
The launcher is downloaded from GitHub as a ZIP file.
An integration key is created in the developer's account.
A secret key is created to enable Authorization Code
Grant.
An RSA key pair is created to enable JWT Grant.
Redirection URLs are added, and the configuration file
is modified with the developer's personalized information.
To run the Node Quickstart launcher,
I must have the Node prerequisite
software installed.
This list of prerequisites can be found in the readme
on our GitHub page at github.com/docusign/code
examples node.
This readme is also included in the Quickstart ZIP file.
The readme has a description of all the APIs code
examples with their source links to GitHub.
I'll scroll to the installation prerequisites section.
It says, note, if you download this code using Quickstart
from the DocuSign developer center,
skip items one and two below, as they're automatically
performed for you.
The Node prerequisite is step three because Quickstart
takes care of step four by pre-populating my developer
account information, which I'll show later.
In order to install and run the Node launcher,
I'll need Node.js version 8.10 or later with NPM version five
or later.
I can follow the link to download the application.
I'll scroll to the installation steps in the readme.
It says, note, if you download this code using Quickstart
from the DocuSign developer center,
skip step four below, as it was automatically
performed for you.
Next, it says, one, unzip the Quickstart file
or download or clone the code examples Node repository.
The Quickstart automatically downloads into my Downloads
folder I'll unzip my Quickstart ZIP file
into my C:/users/mei.hseih/source
folder.
I'm in my unzipped Quickstart folder
C:/user/mei.hseih//source/source tally customer portal node.
Note that the Quickstart wizard appends a dash and the code
language on the end of my quickstart folder name.
Quickstart enables developers to quickly run DocuSign code
examples by configuring a launcher with a developer's
account information.
For the Node quickstart, this configuration file
is located in the Config folder and is named appsettings.json.
Aside for my email address and name,
my unique client ID, client secret,
and impersonated user GUID are also
displayed in the configuration file.
In my docusign developer account,
OAuth elements have DocuSign names.
I can find these OAuth elements on the Apps and KEys page.
My impersonated user GUID is called the API username
and is located under my account information.
Also, my client ID is called the integration key
and can be found under absent integration keys next to my app
name tally_customer_portal.
In addition, my client secret is called the secret key
and can be found by selecting the Actions
button next to my app name, then the Edit button.
The secret key is located under Authentication.
If I forget my secret key, I can create a new one
by selecting Add Secret Key and pasting it
in my appsettings.json file.
Since the appsettings.json file contains personal information
such as your name, email address, impersonated user
GUID, client ID, and client secret,
please don't store it in your source control.
I can also view and modify the source files
in my Quickstart folder and see my changes
when running that code example.
The Node Quickstart launcher will directly
open the embedded signing code example
page, which I'll show later.
Here's the code for embedded signing in the top level
folder.
The filename is eg001embeddedsigning.js.
I'll change the name of the DocuSign document
from lorem ipsum to hello, world.
This name will be shown when the document is
presented in the browser.
I save my changes.
Two, switch to the folder CD quickstart folder name.
I'll use Git bash to navigate to my unzipped Quickstart folder,
tally_custerom_portal-node.
Three, run NPM install.
All the dependencies have been installed.
Five, NPM start.
The node launcher runs.
Six, open a browser to http://localhost:5000.
I saved the consent window from the application
tally_customer_portal.
In the authorization code grant flow,
the application obtains consent from the individual user
to perform actions on their behalf, then
receives an authorization code that
can be exchanged for an access token which
is required to make API calls.
Note that Quickstart also adds a private dot key file
and configures my appsettings.json
file for a JSON web token or JWT grant.
So I can select that flow after completing embedded signing.
Once the user has granted consent to an application,
they will not be prompted again unless consent is revoked.
I click Accept.
Next, I see the embedded signing code example.
All quick starts are pre-configured to run this code
example.
Embedded signing demonstrates how
to collect signatures directly within my app
without emailing the signer.
Also linked are the API methods used, envelopes create,
and envelope views create recipient.
The links will take me to the developer center pages
that describe those methods.
The link to the source file will show me the node.js code
for embedded signing in GitHub.
Now the signer email name have been
pre-populated with my developer account information.
I can change the signer email and name.
I click Submit to send the envelope.
I'm taken directly to the document.
Now I scroll to the bottom of the document
and see that the document name is no longer lorem ipsum
but has been changed to hello, world per my modification.
I'm going to sign the document and click Finish.
I'm taken to the Signing Complete page.
I click Continue.
Now I see the node launcher homepage
with all the code examples.
I can run the other code examples as well.
All these code examples are also available
in the other quickstart launchers--
Bash, C#, Java, PHP, PowerShell, Python, and Ruby.
If you have any questions about how
to develop your integration with DocuSign,
here are some resources.
I recommend checking out the developer center how to guides,
going to Stack Overflow, reaching out to support,
or signing up for API office hours.
That's it.
Thanks for tuning in.
If you're watching from our YouTube channel,
please post questions and comments below the video
or email us at developers@docusign.com.