Go-live

We are Caretta, an AI sales-call assistant (SaaS) with paying customers and under 20 employees. We built a public integration with Docusign's MCP server; it works end to end in our demo account and the integration key shows "Ready to Submit". Since the go-live docs require Partner Program membership for public integrations, we applied, and were rejected with the stated reason that companies must have at least 20 employees.We read the two closest threads before posting:- https://community.docusign.com/go-live-70/go-live-eligibility-question-isv-connector-public-integration-for-a-small-isv-27321 — a small ISV asked the same thing. Developer support said a partner account is not required, then support said the opposite when a Business Pro account could not promote the key. The thread ends unresolved.- https://community.docusign.com/go-live-70/go-live-for-a-public-integration-when-every-customer-uses-their-own-docusign-account-27596 — a Docusign employee confirmed partnership is mandatory

Hey,I am developing an app that prefills all my data in a PDF and I want to send that PDF through my Docusign account to my customers to sign.I have the developer account and app in demo mode - all works fine.I am trying to get it to my live Docusign account, however it is a part of an organization - they pay for our company envelopes, so technically I’m probably not the admin (when I login I see the organization name under my name). So when I click “Select Go-Live account” from my demo account I am prompted to login and then I see this: Select Production AccountSelect an eligible production account to manage this integration key.Select an eligible production account to manage this integration key.You can't select this account because you aren't an administrator for it. Select a different account, or ask an administrator for this account to login. Learn more“CURRENT ORGANIZATION”, Inc - XXXXXXX So is there a way to finish this - the organisation is quite big and I doubt they will deal

am building a multi-tenant SaaS product and I want to make sure I pick the correct integration type before I promote my integration key.Setup:- One integration key, eSignature REST API, Authorization Code Grant, confidential client- Each customer connects THEIR OWN existing Docusign account via OAuth consent- Envelopes are created in, sent from, and billed to that customer's account- No reselling, no billing through my company, no embedded signing ceremony in my UIWhat the docs say, as I read them: "private custom integration" is for customers building an app for their own use, while "public integration" is for apps used by multiple Docusign customers and requires Docusign Partner Program membership to go live.My questions:1. Does my setup count as a public integration, or does private custom cover it, given that every account involved belongs to the customer and not to me?2. If it is public, is Partner Program membership enforced at go-live even when there is no reselling and no embed

We have a public integration built and tested in the demo environment. Each user connects their own Docusign account via OAuth; envelopes are sent from and billed to the users' own accounts. We are not reselling or embedding Docusign.We cannot submit the Partner Program application. The form at partners.docusign.com/s/join-now fails every time with "Failed to Insert record — List has no rows for assignment to SObject". Latest attempt: 2026-08-10, English-only ASCII input, corporate email domain, clean incognito session with extensions disabled. No field-level error is shown, so this appears to be an uncaught QueryException rather than a validation error.Question：Is there an alternative way to submit the application, or could a Partner Onboarding rep set us up directly? I can provide the exact submission timestamp and email address for the Apex debug log.

Hi, I'm the founder of a transaction-management SaaSfor residential real estate teams. I'm planning a Docusign integration and need toconfirm go-live eligibility before I invest the build time.The model is a standard ISV Connector / Public integration:- One integration key, Authorization Code Grant (confidential client)- Each user connects THEIR OWN existing Docusign account via OAuth- All envelopes are sent from and billed to the users' own Docusign accounts.  Nothing is billed to my company, and I am not reselling or embedding Docusign.My company is an established LLC with a corporate domain, but it is a smallcompany: fewer than 20 employees and less than one year old. The Partner Programrequirements page lists "established for at least one year and with at least 20employees," which is why I'm asking before building.Three specific questions:1. For a Public integration under the model above, is Docusign Partner Program   membership strictly required to complete Go-Live, or can Go-Live

I have created an Integration Key in my DocuSign Demo account and would like to promote it to the Production environment.Could you please let me know the steps involved? Also, while creating the Integration Key, it asks me to select an Integration Type. Which option should I choose?I have attached a screenshot for reference.Are there any prerequisites or approval requirements that must be completed before the Integration Key can be used in the Production environment? Do we need to purchase a DocuSign Production plan or subscription before an Integration Key can be promoted and used in Production?  

Hello,I'm going through the Go-Live process for a private custom integration and have a few questions before resubmitting:1. Corporate email requirementThe production Admin account is currently registered with a @gmail address. Is it mandatory that the Admin account itself be registered with a corporate email domain, or is it sufficient that the person filling out the verification form uses a corporate email — even if the DocuSign account is linked to a @gmail address?2. Plan eligibilityIs a specific DocuSign plan required to complete the Go-Live process for a private custom integration using JWT authentication? If so, which plans are supported?3. Signing the formIs it mandatory to complete the identity verification step (document photo + selfie) during the Go-Live form, or can the process be approved without it?

Hello, I’m getting the following error when trying to use Docusign JS for production embedded signing.I have set the frameAncestors to be http://localhost:8080 and https://apps.docusign.com when calling the API to create the embedded signing view URL.The same setup worked with the demo integration where the frameAncestors had https://apps-d.docusign.com.Could you please help me resolve this issue? Error Message:Framing 'https://apps.docusign.com/' violates the following Content Security Policy directive: "frame-ancestors 'self' https://ca.docusign.net". The request has been blocked.

Hello DocuSign Support,We have completed the Go Live process successfully and are now in production, but every OAuth token exchange request is failing with the following error:  "error": "invalid_grant"  "error_description": "unauthorized_client"This has been confirmed via direct Postman testing with a correct request structure. Our technical team has ruled out all client-side configuration issues. We believe the root cause is that API access entitlement is not active on our production account. On our current IAM Starter plan, API access is listed as "Contact sales."We need the following resolved as quickly as possible:1. Confirm whether API access can be activated on our current IAM Starter plan or whether an upgrade is required.2. Provide pricing for the appropriate plan that includes full production OAuth token issuance.3. Activate API entitlement on production account ID 2********* immediately.This is blocking a live production business workflow for our client and every hour of del

Hi everyone,I currently have one application running in production, and now I want to promote another application from my Dev account to Production.Can a single DocuSign production account handle multiple applications/integrations?If yes, what impact could this have on the existing production application (API keys, integrations, users, limits, etc.)?If not, what is the recommended approach for running multiple applications in production? Should we create a separate DocuSign production account, or is there another best practice?

My integration key shows as Live in the developer portal, but when I try to authorize against production (account.docusign.com), I get 'The client id provided is not registered with Docusign.' My production account also shows no integration keys available. Go Live form was signed and counter-signed (Envelope ID: 132D960E...). This has been unresolved for over a week

Hello everyone,I am currently integrating the DocuSign API for a client project and would like some guidance on the correct process to move from the developer demo environment to production.Here is what I have done so far.Step 1 – Create developer accountI created a developer account using my email: abc@gmail.com.Inside the developer dashboard I created an application and generated the required credentials:• Integration Key (Client ID)• Account ID• API base URL• RSA private key for JWT authenticationI have already tested the integration in the demo environment and API calls are working correctly.Step 2 – Purchase Developer Starter planNext I plan to purchase the Developer Starter plan from the DocuSign plans page:https://ecom.docusign.com/plans-and-pricing/developerThe purchase will also use the same email (abc@gmail.com). After completing the payment I expect to receive a confirmation email.My question here is:After purchasing the plan, will I receive a link or instructions to activat

Hi, we’ve had our dev docusign integration working and ready for several months now, and the questionnaires / applications have been submitted for several weeks. We haven’t heard anything back yet and really need to take our integration live. Can we please get a response? Thank you!

Hello, When setting up a tool using the DocuSign API, do you need to login and sign with a personal account?In our case we are setting up a DocuSign integration with our internal Software for customers.So a customer must personally sign and be liable for all signatures done in Docusign under that application?

Hello, I had a docusign working application in development environment where I was calling apis from nodejs application. I created a JWT key using the call back by going here : https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature&client_id={iKey}&redirect_uri={callback}I used integration key and user id as shown on my screen. This setup was working fine.  Then I moved to a new setup by just promoting the application to production. For this I had to add a new member to my account as they have administrative rights to my account. Once I did that, I am not able to make any requests. I even updated the docusign links in my app as follows: DOCUSIGN_AUTH_SERVER="account.docusign.com"DOCUSIGN_BASE_PATH="https://na3.docusign.net"I also updated the JWT by hitting account.docusign.com instead of account-d.docusign.com in the above but I am still getting error of: DocuSign error data: {  error: 'invalid_grant',  error_description: 'no_valid_keys_or_signatures'}

Dear DocuSign Team,I am writing to express my extreme frustration regarding the Go-Live process for my Integration Key (Podio-API). I have been stuck in a loop between your technical and sales teams for several days now.Here are the facts of my case: Technical Compliance: I have successfully completed 26+ API calls in the developer environment, and my status is currently "Ready to Submit". Account Status: I have already upgraded my account to the Business Pro plan (Account ID: *******), which should support custom integrations. And my Developer Account ID is ******* The Issue: Despite the upgrade, the "Select" button remains disabled, and the system shows my account as "ineligible" to promote an integrator key. I have been told by your technical team that I am on the right track, yet the Account Manager system has not reflected the upgrade. This delay is causing significant downtime for my project.I request you to immediately: Manually verify and sync my account's billing status

I have submitted and signed the Docusign API Go Live Form that is linked to the ‘Submit verification form’ button. I would like to know if I need to do anything else aside from wait until the manual Go Live review finishes. My dashboard status did not change status which is making me unsure. And how long might the Go Live process take on average? Thanks 

Hello,I'm reaching out because my Go Live request was recently declined, and I'm unsure why — no feedback or rejection reason was provided.About Our IntegrationWe're building a B2B SaaS platform (Getmany.com) that requires customers to sign commitment agreements.  The Go Live form was declined by Drew Martin, but I received:- No email explaining the issue- No checklist of what failed- No comments or next steps I'd appreciate any help with:1. Visibility - Is there somewhere I can view the rejection reason?2. Common Issues - What typically causes silent rejections? Or it’s normal?3. Checklist - What should I verify before resubmitting? I did more than 80 tests.4. Escalation - Can someone from DocuSign review my submission?I'm ready to fix whatever is needed - I just need to know what it is.Thank you for any guidance you can offer.Kyrylo Kozak 

Hi DocuSign Community,I recently submitted a Go Live request for a DocuSign API integration, and it was declined, but I did not receive any explanation, comments, or guidance on what needs to be fixed or updated.This has left me a bit stuck, so I’m hoping someone here (or a moderator) can point me in the right direction.Integration Details Authentication: JWT Signing method: Embedded Signing (Recipient View) Webhooks: DocuSign Connect for envelope completion Status: Fully working and tested in Demo Use case: Users sign a required agreement before account activation What I’m Confused About I never received: An email A checklist Or any rejection reason explaining why the Go Live form was declined I’m not sure whether the issue is related to: Redirect URLs Branding / consent screens JWT configuration Webhook configuration Or something else entirely My Questions Is there a way to see the rejection reason for a Go Live submission? Are there

 After changing my development account to a production account, the last step was to get this authorization code. I allowed access (granted permission) and tested it in Postman. I keep receiving this 400 error “Invalid Grant” “ Unauthorized Client”.  Has anyone encountered this error before? 

My team has submitted my go live request for about 4 days now and i still haven’t gotten an approval , does anybody know what the issue might be or how to speed this up ? i have a deadline to meet, it will be nice to get this working as fast as possible. 

We are attempting to Go Live and moving our developer integration key to production, however we have been systematically declined every time for… not having a production key. How are we supposed to provide a key which we are applying for? 

For years, developers building integrations with Docusign APIs have voiced a common frustration: “Why do I need to make 20 eSignature API calls to take my integration live?”We heard you. And we’ve fixed it.Today, we’re excited to announce the launch of a streamlined Go-Live experience in Apps & Keys that eliminates the 20 API calls requirement, making it easier for developers to take their integrations live. 🌟 What’s NewNo more 20 eSignature API calls for Go-Live: Going live is now seamless. Simply select your integration type, enter your production account details, and the built-in validation will check if your integration is eligible to go-live in that production account. If eligible, your integration can, in most cases, go live instantly. 🎯 Why This MattersPreviously, developers were required to make 20 eSignature API calls to start the Go-Live process. In many cases, this effort added no value and slowed down launches. This requirement was especially painful for those working

Hello, community!I’m having trouble publishing my app to production. I had already started the process, but it was rejected due to not meeting the requirement of 20 test requests. After completing this step, I resubmitted the request, but now the go live status only shows “error”, without specifying what went wrong. In addition, I no longer have the option to resubmit. I reached out to support, and they advised me to look for a solution here in the community.

We've met the following criteria and we're thinking that this is a platform bug because what we're seeing in the go-live dashboard isn't reflecting the "declined" state that's indicated in Go-Live process documentation. We have a status of “Ready to submit” but received decline email. We have the IAM Standard subscription. Here are the criteria we're meeting:- We have, and are submitting this request from, a dev sandbox account and integration key- 20 or more successful API calls in a 24 hour period- Integration exclusively using OAuth 2.0 for authentication- Active production account with a plan activated (this account)- Admin privileges on both the dev and prod accounts- Review submitted via the actions -> go live process- Logs are clean- We’re thousands of calls below the rate limits- The go-live request attached to this message is the one that's been declined twiceWe’re not getting anything in the dev dashboard indicating a declined state, only that it’s ready to submit, even af