Integrator key not showing/working in production - docusignapi

I have created application that sends docusign document to emails i specify in form.
It's working fine in demo mode, without any error.
I have also signed the integrator key to make it work in production(Live) account (However its not showing any integrator in admin area here).
It gives error this error in live mode "The specified Integrator Key was not found or is disabled"
I have signed up using different email id for demo account then that is for production, but I have got approved my integrator key for production(Live) account. is this might be a problem?
So what's the problem, do i need to do any thing more to the live account (Like adding the demo user, or something like that)?
How do i verify that they have made my integrator key available for production?
Please help.

To make an integration key work in production you have to apply for it to be live. The Go-Live process was automated after this question was asked. https://www.docusign.com/blog/dsdev-docusign-go-live-process-now-automated/ talks about these changes.

Related

Upgrade to the official environment and receive the following error "The client id provided is not registered with DocuSign"

I have applied the integrated key as a live key in the sandbox environment of docusign, and the status is: review passed,
However, I used the domain name of the official environment to obtain the authorization code. When logging into the official account, I received the following error: The client id provided is not registered with DocuSign
Does anyone know what I am missing?
enter image description here
Congrats on passing the review for the DocuSign eSignature API Go-Live process.
However, you still need to take one more step after that. Which is, you need to go to your developer sandbox (demo) env Admin, find your integration key and click "Review Status" where you see it passed, and then click "next" to log into the production (what you called "official" env to get that key activated in there. You would need to have a production account to proceed.
Important: You need administrator privileges to the production account to promote a key into it. If you do not have any valid account memberships, an error will be returned. Also note that certain account types, such as 30-day Free Trials and Freemium accounts, are not eligible for key promotion.

Sending envelopes from one dedicated user

I have been trying to implement JWT Auth grant for our back end application which will be creating URLs for signing operations for our end users.
What I want to active is that there will be no login/granting consent operations while sending the envelopes and creating signing URL. I want to dedicate one user for creating envelopes and sending them for signature.
Firstly, I've created a demo account and an organization. I also created an integration key and a RSA key. I needed to choose Implicit Grant or Authorization Code Grant while creating the integration key and I chose Implicit Grant. Lastly, I gave signature impersonation permissions to the integration key.
I have checked and made experiments with jwt example project after configuring with the required info of the user that I want to dedicate. It asked for the consent. After I gave consent, it worked finely. Then I configured the back end with the same integration key and the guid of the user, again it was working with our back end application that I was able to send automated envelopes.
I created another demo account in DS and this time I directly put it to our back end, I am getting consent_required error which I understand that I couldn't give the admin consent properly and it was just working with previous demo account because I gave the consent to that.
I want to know that how long that consent would last. or Is it the correct way to achieve what I want? because I think, ideally, I need to give admin consent to this dedicated user to have it able to send automated envelopes.
Thank you a lot in advance.
I see two questions:
How long consent would last? - forever. Or if you go and explicitly remove it.
Is it the correct way to achieve what I want? I don't know what you want, but the title says "Sending envelopes from one dedicated user" so, in theory that is correct. However, keep in mind that that user will be different when you move to production ("go live") when your application is ready for real usage.

Docusign promote integrator key from demo to live

I am currently trying to promote an integrator key from the demo environment to a live environment. I have read all of the documentation regarding this process and have had no issues up until this point. Currently, I have an integrator key in my demo environment which has passed review and I am trying to promote this key to my live environment. To do so, I am logging into my demo environment, selecting new admin experience, selecting APIs and Keys, selecting the "Actions" dropdown next to my key which has passed review, and then selecting "go live". After doing this, a terms and conditions popup comes up which I accept and then I am redirected to a login page. I understand from the documentation that my live environment login credentials are used here however I am unable to log in. I can use the same login credentials at na2.docusign.net/Member/MemberLogin.aspx and I am logged into my live admin account error just fine. I have also tried using the forgot password link on this popup in which I am successfully able to reset my password via a secret question. I then go back through the same process to get to the login popup after selecting my key to go live and again, I am unable to login. How can I overcome this as it is a time sensitive issue? I have also sent an e-mail, per the documentation, to go-live#docusign.com outlining this issue and have not yet received a response.
Note that my live account is a member of the administrator group. Are there other permissions that need to be set up that may be preventing me from completing this?
Please resend your email to go-live#docusign.com
Please include the integration key, the account id for your demo account, and the account id for your production na2.docusign.net account.
Your account ids are shown in the drop-down by your name in the web tool's upper right hand corner, by your picture or glyph.
Please accept my apologies for these problems with the new Go-Live system.
There was an issue with the DocuSign go live process. It has now been resolved. Please try again.

Unable to get the DocuSign API integrator key

I am evaluating the DocuSign API, but unable to get the integrator key. Is there any way to get the integrator key?
Currently I am using DocuSign trial version.
Below are the steps followed:
Logged into this link “https://app.docusign.com/home”
Clicked on drop down at the top right corner and clicked on "Go To Admin"
Navigated to "Api and Keys" in "Integration". It asked to “log in” again to manage integrator keys, Below is the screen shot.
![enter image description here][1]
After clicked on log in, it is redirected to “Billing and Usage” page. Below is the screen shot.
![enter image description here][1]
DocuSign has a full demo environment which is a mirror of the live production system and allows for you to test and integrate the APIs. To do so you need to create a developer sandbox (they are free) and create an Integrator Key through the Admin menu of your sandbox - which is the only place the keys can be created - then promote that key to your live production account.
You can create your developer sandbox here: https://secure.docusign.com/signup/develop
To login to your sandbox: https://account-d.docusign.com/#/web/login
Once you've created an Integrator Key and you are ready to access production API endpoints follow these steps:
Run 20 or more error-free transactions that comply with API rules and limits under your Integrator Key.
Purchase an API plan (sounds like you already created your live account)
Make sure you have Admin priveleges to your live production account as they are required to link the Integrator Key.
Fill out the Go Live form to promote your Integrator Key.
You can access the form through the Go Live section of the Developer Center.

One or both of Username and Password are invalid

I have developed an integration using docusign SOAP API. We had the integration certified. It works great using the demo API URLs and my dev account. When I update the API URLs to production and use my live production account I get the return status of "One or both of Username and Password are invalid" when I call CreateEnvelope(). I have verified the user name and password are correct. I use them to log into the production account. I am setting the username in the code like [APIKEY]APIUSERNAME.
Does a DocuSign account need to be authorized to use an integration? How do I know my integrators key was moved over to production after certification? Any ideas when this works in dev but not in production.
Just wanted to follow up and post the answer to this issue. After working with Partner support I was able to get things working.
The issue was related to using the wrong base url when I created my api proxy. I was just passing in the docusign production url, when I actually needed to get this in the configuration for each user that uses the integration. When I get the base url in the config part of the app it return the actual server which the users account resided on (which includes the na1 or na2 etc server name in the url). After adding this to the config and using this new base url in my calls the app works as it should.
Yes I believe DocuSign production accounts need to be authorized to use the API. If you are positive that you are passing the correct username and password in your code then it's quite possible that this is an account issue.
For resolution I would suggest the following. For questions regarding your integration key and if it was indeed promoted to production following your successful certification you should contact
apicertifications#docusign.com
And if you have an account manager you might want to try reaching out to them as well, which might get your questions answered sooner.

Resources