Welcome to developing with DocuSign. I'm Aaaron Jacksonwilde. A member of
the Developer Center team. In this screencast,
I'll walk you through installing and running the PowerShell Quickstart on Windows and the
embedded signing code example. To follow along with this screencast, you'll need a Quickstart
ZIP file. If you haven't yet downloaded your PowerShell Quickstart ZIP file, please first
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 and the developer's
DocuSign account that can make API calls. When you follow the Quickstart wizard, these steps
are completed for you. The launcher is downloaded from GitHub as a zip file and integration key is
created in the developer's account. A secret key is created to enable authorization code grant.
An RSA key pairs created to enable JSON Web Tokens grant.
Redirection URLs are added and the configuration file is
modified with the developer's personalized information. A list of prerequisites can be
found in the readme on our GitHub page at github.com/docusign/codeexamplespowershell.
This readme is also included in the Quickstart ZIP file.
The readme has a description of all API code examples with their source links to GitHub,
all scrolled to the installation prerequisites section.
It says, note, if you downloaded this code using Quickstart from the DocuSign Developer Center,
skip items 1 and 2 as they were automatically performed for you.
To install and run the PowerShell launcher, I'll need PowerShell version 5 or later. I'll scroll to
the installation steps in read me. It says, note, if you downloaded this code using Quickstart from
the DocuSign Developer Center, skip step 3 as it was automatically performed for you. Next, it says
one. Extract the Quickstart ZIP file or download or clone the code-examples-PowerShell repository.
The Quickstart automatically downloads into my Downloads folder. I'll unzip my Quickstart ZIP
file into my desktop folder. I'm in my unzipped Quickstart folder. Note that the Quickstart
wizard depins 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 the developer's account information.
For the PowerShell Quickstart, this configuration file is located in the Config folder
and is named settings.json. Aside from my email address and name, my unique integration key,
secret key, and impersonation user good, are also displayed on the configuration file.
In my DocuSign developer account OAuth elements have DocuSign names.
I can find these OAuth elements on the apps in case page. My impersonation user
it is called the API username and is located under my account information.
My integration key can be found under the apps and integration keys,
next to my app name Tally customer portal.
In addition, my secret key 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 settings.json file.
Since the settings.json file contains personal information such as your name, email address,
impersonation user good, integration key, and secret key, do you not check these files into
source control, such as the Git Repo. I can also view and modify the source files in my Quickstart
folder and see my changes when running that code example. The PowerShell Quickstart launcher will
directly open the embedded signing code example page, which I'll show later.
Here's the code example for embedded signing at the top level folder.
File name is eg001embeddedsigning.ps1. 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 for run the
launcher. In the roof folder, right click the launcher file and select Run with PowerShell.
From here, you'll see the 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.key file
and configures my settings.json file for JSON web token or JWT grant,
so I could select that flow as well.
Dot net dependencies are required to use JSON web tokens with PowerShell and will
be downloaded automatically the first time you attempt JWT. Once the user has granted consent
to an application, they will not be prompted again unless consent is revoked. Click Accept.
Next, Quickstart will run example 1 embedded signing. The signer email and
name have been pre-populated with my developer account information
via the settings.json file. As we see, the envelope is generated in real time
and populated with the signer name and email address from the settings.json file.
Now, I scroll to the bottom of the document and I see that the document 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 a web based HTTP response repository.
Here, I confirmed that the signing event has occurred.
Next, we'll return to the launcher. The PowerShell launcher directs me back to eSignature code
examples menu. I can run other code examples as well. All these code examples are also available
in the other Quickstart launchers, Bash, C# Java, NOGS, PHP, 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.