Skip to main content
Newcomer
September 20, 2024
Question

Getting error :The specified Integrator Key was not found or is disabled. Invalid account specified for user

Hi, 

I am working on setting up an integration with Docusign for Salesforce, the last thing I did was update the token, then I tried to send an envelope and got the error message:  The specified Integrator Key was not found or is disabled. Invalid account specified for user” in a demo account.

Checked in salesforce that integration key is matching with integration key is matching DocuSign account integration key. The below url I am using is this, please advise. Thank you

Docusign Account URL https://account-d.docusign.com/oauth/token

4 replies

Docusign Alumni
September 23, 2024

Hello,

From my understanding, in the demo account you’ve been receiving the error “The specified Integrator Key was not found or is disabled. Invalid account specified for user” ”.

The DocuSign Account Url would need to be changed. from what it currently is.

The base path to connect to the developer environment(Demo) should be to the base url path “https://demo.docusign.net/restapi...”.

Depending on if there is a different endpoint in the future, I suggest following this article to ensure you’re connecting with the correct one.

Best,

DocuSign Support

Translate
Hengfeng Ge
Hero
Hero
September 23, 2024

do you have more than two account for this user? is it integrate by code grant or jwt? Have you try authorize url whether it is success? thanks.

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🏆 2024 APAC Reseller Growth Partner of the Year
🔧 The first in APAC to pass the DocuSign eSignature Technical Consultant certification.
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries.

Feel free to reach out for collaboration opportunities.

 

Translate
Welcome to the DocuSign Community! Your feedback is highly valued. If you find my response helpful, please give it a "Like" and consider marking it as the "Best Answer" to assist others with similar issues.
Docusign Alumni
September 24, 2024

The article suggested  to ensure you’re connecting with the correct one is listed below:

https://developers.docusign.com/platform/api-endpoint-base-paths/

 

Best,

DocuSign Support

Translate
Docusign Employee
October 20, 2026

Hello, 

Apologies for the late reply. For anyone experiencing this issue today, the above still does apply when considering baseUrls when connecting to Docusign systems.

In this case, the URL in question appears to have been set with a baseUrl of https://account-d.docusign.com, which is the baseUrl for the Demo Account Server, instead of the baseUrl for the REST API, which is https://demo.docusign.net/restapi. Changing the baseUrl in this case should fix this as an issue. 

If you’re seeing this error today, you may also be experiencing a cutoff related to Docusign’s Legacy Auth Migration Project, which you can find more information on here: https://developers.docusign.com/platform/auth/oauth2-requirements-migration/

Docusign is in the final phases of deprecating Legacy Authentication. If you feel that you may have been affected, please reach out to your Account Manager or open a ticket with Customer Support or via https://support.docusign.com/ in order to engage with one of our representatives to help with your migration efforts. If possible, please have your Integrator Key ready as it will greatly assist us in expediting your requests. 

Regards,
Matt King | Sr. Advanced API Support Engineer | Docusign

Translate