Skip to main content
arrow-left Back to Docusign.com

Hello,

We set up a DocuSign app on our client’s dev account, passed the Go-Live check, and published to production. As the next step, a production user opened the consent link and approved it. We can see the app listed under the user’s Connected Apps.

However, our OAuth token request to https://account.docusign.com/oauth/token still returns:
{"error":"consent_required"}

Note: We also have another production account where this flow works as expected—authentication succeeds—so the issue appears to be specific to this production account.

 

I’m out of ideas on what else to verify and would appreciate any tips or guidance. Thank you.

​@UriP 

The general approach to troubleshooting this issue appears to be correct. Since you've confirmed that the consent is visible in the production environment, we can confidently rule out the common misconception that this issue is isolated to the demo environment.

The problem is likely that the required scopes were not successfully applied during the initial consent process.

This often occurs due to issues with the consent URI's formatting or encryption, which prevents the necessary scopes from being granted. This is a common situation I've encountered with other customers that results in insufficient application access.

To resolve this, you can re-run the consent process URI to correctly apply the additional, missing scopes.

While not strictly required, I suggest removing the existing entry for the integrator key/app from the user's profile before re-running the URI. This ensures a clean slate and minimizes the chance of previous, partial consent entries conflicting with the new request.

Code of ConductAccessibility statement

Docusign Community

Code of Conduct