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

I am currently integrating DocuSign with Oracle Integration (OIC). At present, I am using the following REST API to generate a bearer token:

<BASE_URL>/oauth/token?grant_type=refresh_token&client_id=[client_id]&client_secret=[client_secret]&refresh_token=[refresh_token]

 

This works fine as long as my refresh token is valid. However, when the refresh token itself expires, I currently use Postman to manually log in to my DocuSign account, provide consent, and generate a new refresh token.

This approach is not ideal since it introduces manual intervention and breaks the automation.

My Questions:

  1. What is the best way to avoid this manual Postman step?

  2. Is there a way to fully automate the token generation process in Oracle Integration so that I don’t have to worry about refresh token expiry?

  3. Should I switch to the JWT Grant flow for this type of server-to-server integration?

Any guidance on the recommended approach would be greatly appreciated.

Thanks in advance!

 

Hi Fusion06,

  1. I think you can use one the SDK methods to get a new refresh and access token programmatically, without having to use a manual Postman step. We have a section documenting the methods here.
  2. I don’t have any experience with Oracle Integration, but you can use the refresh token to request a new refresh token before it expires. If you track when the token will expire and use it to refresh before that happens, you should be able to keep your token indefinitely if you have also requested the extended scope.
  3. if your integration uses a single or system user rather than logging in individual users, JWT Grant may be a better fit.
Code of ConductAccessibility statement

Docusign Community

Code of Conduct