This tutorial shows how to use Postman with REST/JSON and the eSignAnyWhere API.

Download files for tutorial (JSON for Tutorial, JSON for variables, PDF): Tutorial Files

You can either use the following guide which explains Postman and shows the individual api calls or you can import the Swagger in Postman with this link: https://demo.esignanywhere.net/Api

After the import you have already imported all api calls with the descriptions. How to import: Just select “import” in Postman and then select the “import from link” and add the link above.

Collection

In this tutorial you will do the first API Call as well as sending envelopes, upload documents and download signed papers. Let us start with creating a Collection so that we can save all request there. Therefore, you must go to the register “new” and select Collection. Then Figure 1 should appear where we define a name for our Collection.

Create a Request

After creating a new Collection, we will save our first request into it. Therefore, you select again the register “new” and pick request. Afterwards the Figure 2 should appear where you choose a name for the request and make sure to save it in the Collection we just created.

First API Call (get the version)

Let us start now with the first API call. As the name of our request tells we will first make an easy call to examine the current version.

You can see all requests here:

https://demo.esignanywhere.net/Api

Therefore, you must select the request type to a “Get” request and you must fill in the URL. For a detailed overview see the next Figure.

As you may see from the Figure 3 you just have to fill in the URL, select the correct type (in this case it is a “Get” type) and then you just have to click the send button and you will get such a result as shown in the Figure 3.

If an error appears, make sure you have chosen the correct request type and the right URL.

Version Request JSON

not required

Version Response JSON

{
    "Success": true,
    "Version": "3.4.110.12913"
}

Authorization

The next request will show you an authorization. This is an important part of the requests for sure but not only because of security but also because we will need the authorization for all other requests.

Let us create another request to make our second API Call to try the authorization. The only extension to the previous call is to define the headers. If you click on “Headers” you will see three columns. The first and second one, so the keys and the values are necessary for the authorization.

One key is “userLoginName” and the second one is “organizationKey”. The value for the login name is your email-address and the value for organization key is your organization key.

Authorization Request JSON

not required

Authorization Response JSON

Should response 200 OK

Upload a File

Before we can send an envelope, we must make sure that we have already uploaded a file. Therefore, the next request will be about uploading a file.

As you can see in Figure 5 you must also edit the body. So, the header will be the same as we have already seen in the authorization. In the body you must select that you will upload a file and you must choose a file which you wanted to be uploaded. (In this case “Tutorial.pdf”)

It is necessary to change from “none” to “form-data”.

Afterwards you should get a file ID. It is necessary that we do not forget this ID because we will need it for the envelope sending request.

Upload Request JSON

not required

Upload Response JSON

{
    "SspFileId": "17d23c79-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

Sending an Envelope

The sending request is a bit more complicated than the previous once. First, copy the sending description (Example value) from this link:

https://demo.esignanywhere.net/Api/swagger/ui/index#/Envelope/Envelope_Send

and paste it in the body of the sending request. Then change from “none” to “raw” and change the File ID to the one you get from the upload file request.

The next Figure should give you an overview of all changes you have to do to get a positive result. (in this case the result is the envelope ID)

Sending Response JSON

{
“EnvelopeId”: “d4f71aec-e332-48c3-8ca9-b0be6adf9ea8”
}

Get the Envelope Description

The last request of this tutorial will be the download of the document which has been signed.

But before we will check if the envelope with the ID which we got from the sending is correct. Furthermore, we need the request “get the envelope” because of the document ID`s which we only get because of this request.

The following Figure will help you with the request and give you an overview how it should be done.

In Figure 7 you can see that you just have to do the authorization as usual and you have to attach your envelope ID to the URL. In the result we can see that the status is in progress so the one who got the envelope has not signed yet.

If we do the same request after the recipient has signed the envelope, we will get the result which is shown in Figure 8.

In this case the status says completed so we have now the document ID`s which we need to download the signed document.

Download the Signed Document

The request to download the signed document is quite easy. You must attach the document ID which we got from the “get the envelope” request to the URL.

The next Figure will give you an overview.

Download Request JSON

not required

Download Response JSON

Should response 200 OK

You can choose between three document ID`s which you got from the “get the envelope” request.

For the “LogDocumentId” you get an Audit, for the “LogXmlDocumentId” you get an XML and for the “FlowDocumentId” you get the original document with the sign of the recipient.

After the tutorial you should have the same requests which are shown in the next Figure.

How to Use Variables in Postman

Let us start with the authorization but this time we will use variables, so we do not have to remember the organization key and the user name for all other requests.

Manage Environments

After selecting the configuration button which is shown in Figure 11 another window should appear which is shown in Figure 12. There you must give the environment a name and we have to create the two variables which are necessary for the authorization. Further details in the next Figure:

First give your two variables names (it does not matter how you name them). Then fill in “initial value” and “current value” your email address for the username and the organization key for the key. After filling up the environments for both variables, we now can use them in the header of the next request.

Authorization

Figure 13 shows you the same request we have already done in the tutorial above but this time we will use the variables we have just created.

In the first column we have our keys. In the second column we now do not have to fill in our email addresses and organizational keys, but we must write {{##name_of_the_variable##}}. From now on you can always use the variables instead of continual writing your address and your organizational key because all the dates are saved in the environments. If you run this request, you should get the status “200 OK”.

Upload a File

Now we will upload a file and save the file ID which we will get from the request in another variable in the environments.

Just these three lines of code are necessary to save the file ID in another variable. First we will parse the response, then we set the file ID with the command (“pm.environment.set(“name_of_the_variable”, response.” name_of_the_response”).

After running this request, the new variable “sspFileId” should be in the environments. See next Figure:

Send an Envelope

After saving the file id we can now send the envelope with an integration of the variable. Therefore we just fill in Template:Name of the variable for the fileID instead of copy paste the file ID. This is shown in the next Figure. In the Figure 17 there is another example of how you save a date from the response. In this case we will save the envelope ID.

Get Envelope Description

We now want to save the different document ID`s (LogDocumentId, LogXmlDocumentId, FlowMDocumentId).

Therefore, we must check if the array has a length higher than 0. After that, we must do the same “set” command as in the previous once but now we have to “go” into the array. So we write again response.”name_of_the_array[on which place].”name_of_the_variable”.

After we have saved all documentId we can use them for the download request. You can find the configuration for saving the documentId here: Configuration

Download the File

Therefore, we just have to attach the variable to the URL which is shown in the next Figure.

Overview of all Variables

Advantages of Using Variables in Postman

First, we do not have to remember all dates which we get through all the requests. Furthermore, we can simply change the organization key and the username and wen can play all requests without other changes because the variables auto fill in the new dates in the requests. Moreover we have a better overview of all ID`s so that we can easily match them with the requirements of the requests.