docusign-node-client | Official DocuSign Node.js Client Library | REST library

by docusign JavaScript Version: v5.8.1 License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | docusign-node-client Summary

docusign-node-client is a JavaScript library typically used in Web Services, REST, Nodejs, NPM applications. docusign-node-client has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i docusign-rooms' or download it from GitHub, npm.

NPM module that wraps the DocuSign API.

Support

Quality

Security

License

Reuse

Support

docusign-node-client has a low active ecosystem.

It has 110 star(s) with 73 fork(s). There are 17 watchers for this library.

It had no major release in the last 12 months.

There are 8 open issues and 106 have been closed. On average issues are closed in 94 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of docusign-node-client is v5.8.1

Quality

docusign-node-client has 0 bugs and 0 code smells.

Security

docusign-node-client has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

docusign-node-client code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

docusign-node-client is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

docusign-node-client releases are available to install and integrate.

Deployable package is available in npm.

Installation instructions are available. Examples and code snippets are not available.

docusign-node-client saves you 908 person hours of effort in developing the same functionality from scratch.

It has 2073 lines of code, 0 functions and 544 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of docusign-node-client

Get all kandi verified functions for this library.

docusign-node-client Key Features

No Key Features are available at this moment for docusign-node-client.

docusign-node-client Examples and Code Snippets

No Code Snippets are available at this moment for docusign-node-client.

Community Discussions

Trending Discussions on docusign-node-client

How can i get docusign access token in nodejs to sign the document

DocuSign Node SDK not returning loginInfo in Production

Error Sending Composite Template to Docusign API

QUESTION

How can i get docusign access token in nodejs to sign the document

Asked 2020-Feb-25 at 08:26

I want to use DocuSign embedded signing to sign a document.

How can I get a access token to sign a document?

I manually get the access token, which is valid for 8 hour, but I want to generate access token in Node.js API. How can I get it?

I have tried the following:

doc1
doc2

...

ANSWER

Answered 2019-Mar-14 at 22:19

If you are using User Application then you need to check Authorization Code Grant to learn how DocuSign using this type of Grant to generate AccessToken and RefreshToken.

In User Application flow, AccessToken is provided for 8 hours and once AccessToken expires then your App needs to use Refresh Token to generate new set of Access and Refresh Token.

But if you are using System Integration then you need to check JSON Web Token Grant to learn how DocuSign provides AccessToken using JWT.

In System Integration flow, it is assumed that an API user in your App behind the scene will call DS API, and there is no DocuSign User interaction to login after certain interval to provide access to your App to generate Access token on behalf of the logged in user once Refresh token expires. System Integration Flow will get one time consent, Obtaining Consent explains how to get Consent. Once consent in provided to the Integrator Key then Integrator Key via your app can generate AccessToken any time, and this AccessToken will be valid for 3600 seconds, once it expires then you create new JWT and call DocuSign OAUTH API to generate new AccessToken for next 3600 seconds.

Node JS_03 is an example showing how User Application flow works.

Node JS_01, check for dsJwtAuth.js is an example showing how System Integration flow works using JWT.

Source https://stackoverflow.com/questions/55160047

QUESTION

DocuSign Node SDK not returning loginInfo in Production

Asked 2017-Dec-12 at 21:19

I've built out an integration using DocuSign's Node SDK. While testing using a DocuSign sandbox account, the authentication flow works just fine using the example in the docs.

I'm now trying to do the same within a live DocuSign production account using the Integrator Key that was promoted from the sandbox account. authApi.login() seems to work just fine, I get no error and the status code of the response is 200. However, the value of loginInfo comes back as exports {} with no account info included.

I've made sure to change the base path from https://demo.docusign.net/restapi to www.docusign.net/restapi and as far as I can tell from the docs, there doesn't seem to be anything else I need to make the switch to production. Here is the code I am using:

...

ANSWER

Answered 2017-Dec-12 at 21:19

www.docusign.net endpoint will only work if your PROD account is in NA1, if your PROD Account is in NA2, then you need to use na2.docusign.net and if it is in NA3 then na3.docusign.net. This is the main reason you should use /oauth/userinfo call with OAUTH2 Access Token to know your base URL, and then call all APIs with this baseURL. You can find more details at https://docs.docusign.com/esign/guide/authentication/userinfo.html

Source https://stackoverflow.com/questions/47781493

QUESTION

Error Sending Composite Template to Docusign API

Asked 2017-Jun-07 at 06:48

I am trying to use the docusign-node-client to send an envelope using the createEnvelope class. This class sends a REST API request to the /envelopes endpoint. The envelope I am trying to send contains a Composite Template.

Here is the body I am attempting to send to docusign

...

ANSWER

Answered 2017-Apr-08 at 01:38

You are specifying the inlineTemplate.envelope property incorrectly. You can define the recipients and custom fields directly within the inlineTemplate. You do not have to specify the emailSubject/emailBlurb within the inlineTemplate.

Also note that the custom fields specified at the root level will be ignored when using composite templates. See this answer

The following json should work for you.

Source https://stackoverflow.com/questions/43288467

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install docusign-node-client

This SDK is provided as open source, which enables you to customize its functionality to suit your particular use case. To do so, download or clone the repository. If the SDK’s given functionality meets your integration needs, or if you’re working through our code examples from the DocuSign Developer Center, you merely need to install it by following the instructions below.