docusign | Docusign gem for Ruby | Data Migration library

we are migrating from legacy authentication to OAuth and I came accross this article. To get the user apiUserName, the post proposes using the users endpoint. Since this link is designed to be used with Connect, I assume this is an unintentional error. Is it necessary for our company to purchase Connect in order to get information about our account's users? We use the account users API endpoint in our integration, and I'm wondering if we were obtaining the erroneous user information all along? Although the post mentions apiUserName multiple times, we don't believe either of the edpoints returns this key. "userName" - my name  and "userId" - my user GUID - are the closest we can get. How and where can we retrieve the value of apiUserName?

I have a problem with creating another user by Admin API. I don't have an organization_id property in /userinfo response. I need it to create new users via my app. There I also use recommended scopes.

This response I have after call /userinfo

I can parse an XML and get this specific chunk off it like so:

I am trying to integrate our web app with DocuSign. We expect our web app customers will authenticate and grant consent to our app to make API calls on behalf of their DocuSign accounts. Then our app will create envelopes (using access tokens to customer DocuSign accounts) and allow our app users to sign them using embedded signing.

We've built a prototype using demo account and everything works like a charm.

The only thing what is still unclear for me is how it is supposed to work after going live.

1. Am I right that our customer will be charged each envelop sending, since our integration makes call on behalf of their account?
2. Is it enough for our customer to pay for Standard eSignature Plan to make embedded signing work, or they should choose Enhanced Plans (the one where API feature is listed)
3. Should our account plan (which holds Integration Key) be at least Advanced Developer to support embedded signing?

Could anyone advise on the matter. Thanks!

There are two issues I am facing for draft envelopes:

1. Envelope with status created i.e. draft created through REST API not visible under users draft folder but create envelope REST API request returns success with created envelope id and path for envelope
2. Draft envelope created directly in DocuSign gets displayed for sometime under draft but once after browser refresh that draft request somehow gets removed from draft folder.

Here is how I am doing that directly in DocuSign:

• Create new envelope request

• Save and close as draft

How to create envelope with custom Envelope EmailBlurb message text in a prettier format like Word document or HTML? How to achieve this, using HTML text in EmailBlurb or other DocuSign attributes & setting to enable rich format of EmailBlurb?

Thanks in advance, CT

For context, we are currently developing a DocuSign integration on our DMS web app product. So far what we have done is that the web app's admin (we assume this would be someone like our customer's IT) can set up the integration by entering API Account ID, Integration Key, Secret Key, Access Token & Refresh Token. All these information was taken/generated using a DocuSign admin account. With this, we see that any user using the DMS can send out signing requests (via API) without logging in to their own DocuSign account.

However, we realised this means that all signing requests will be sent using the common DocuSign admin account, i.e. the envelopes originate from the admin account and all signed documents also stored in the DocuSign admin account. This is not what we want as the DocuSign admin can see confidential signed documents.

I'm quite confused and would like to seek advise on how should we go about this? Ideally, it is that User A of the DMS can associate his DocuSign account with his DMS account. So that when User A sends out the signing request from our DMS, the signer receives the email from DocuSign showing it is from that user instead of the common admin account.

Also, it looks like the go-live process would have to take place for each customer that is using our DMS? Does it mean like each customer need to have their DocuSign developer account so that the integration key can get promoted to production environment? Or am I in the wrong direction & should look at Partner Integration as ISV?

I try these tutorials: https://github.com/docusign/mobile-android-sdk/blob/master/README.md, especially the function getUserSignatureInfo. In this function a REST API call (userSignaturesGetUserSignature) is made.

In my code below I try to return a value (userSignatureId) I get from REST API. I understand, it's impossible this way, because onSuccess() will be invoked later as the outer function getUserSignatureInfo() returns.

I want to call getUserSignatureInfo() from a Fragments onActivityCreated() and use this value on creating a RecyclerView.Adapter.

The question is, what is the (best practice) way to do something like this: make a REST API call, wait for response, and use the response in further code.

I am tying to obtain Access Token using Google Apps Script.

Ref: https://developers.docusign.com/platform/auth/jwt/jwt-get-token/

Using Postman, I can get the ACCESS TOKEN by posting a request using this URL: https://account-d.docusign.com/oauth/token and this two fields in the body:

• grant_type : urn:ietf:params:oauth:grant-type:jwt-bearer
• assertion : MY_JSON_WEB_TOKEN

How do I replicate tis in Apps script?
After endless hours of trial and error I still get this error: {"error":"invalid_grant","error_description":"unsupported_grant_type"}

The script: