Skip to main content

Hello,

I apologize if this question has already been raised, but after searching extensively for similar issues, I couldn’t find a definitive answer.

We would like to use a dedicated account specifically created for API access. This account would be shared by all our users to send envelopes to recipients, both inside and outside our organization.

We want the user interaction with the API account to be entirely transparent, they should not need to log in to the API account, even once. I have read online that this setup is possible, but we are struggling to get it working as intended.

I was able to obtain consent to use the API account on my PC, but when I attempt to send an envelope from another PC, it prompts me to sign in to the account to grant consent again.

Shouldn’t the consent only be requested once?

Perhaps we’re missing a critical configuration step?

Here’s the URL we use to obtain consent:

https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=OUR_ID&redirect_uri=OUR_URL

Hi ​@Benjamin N.,

Yes, consent should only be required once per Integration Key + user account. If it's prompting for login on other machines, it's likely because you're using Authorization Code Grant, which is interactive by design.

For fully non-interactive, shared API access, you need to switch to JWT Grant authentication.

You can find more information about Docusign authentication types at the following link:
https://developers.docusign.com/platform/auth/


Hi @Islam.Hassanein,

Thank you for your response.

I initially thought I was already using JWT grant authentication, but it turns out that wasn’t the case.
Thanks to the documentation you shared, I’m now able to generate a valid JWT access token and should be able to perform API calls successfully.

Have a great day!


Reply