Copy link to clipboard
Copied
We are working through API documentation available in:
https://secure.na4.echosign.com/public/static/oauthDoc.jsp
The OAuth authorization is a bit cumbersome.
It seems that the “Authorization Request” has to be initiated via a browser. That would require login to the Adobe sign to authorize access. Which then generates the code needed for the token service.
https://api.adobesign.com/oauth/token
Our solution would like to invoke APIs without the process via browser and that requires login to the Adobe sign. Is there a way to acquire that code programatically. That can be send to the token service without the browser interaction and approval process. Which typically invloves build url and the code from the redirect.
https://secure.na4.echosign.com/public/oauth/v2?redirect_uri=https://example.com/oauthDemo& response_type=code&client_id=d4HQNPFIXFD255H&scope=user_login:self+agreement_write:account& state=S6YQD7KDA556DIV6NAU4ELTGSIV26ZNMXDSF7WIEEP0ZLQCLDQ89OYG78C3K9SROC8DXCGRVSGKU1IT1
Any help is appreciated?
Hi Quamrul,
Thank you for reaching out.
As you have a questions related to the API integration, it can be best answered by the experts. I would suggest you to get in touch with the support team as they can provide you the right information. You may contact support team using the steps suggested in the following help document: https://helpx.adobe.com/sign/using/adobesign-support-resources.html.
Let us know if you need any help.
Thanks,
Meenakshi
Copy link to clipboard
Copied
Hi Quamrul,
Thank you for reaching out.
As you have a questions related to the API integration, it can be best answered by the experts. I would suggest you to get in touch with the support team as they can provide you the right information. You may contact support team using the steps suggested in the following help document: https://helpx.adobe.com/sign/using/adobesign-support-resources.html.
Let us know if you need any help.
Thanks,
Meenakshi
Copy link to clipboard
Copied
Thanks Meenakshi,
I was able to add mmself as support admin and create a case as per your reccomendation.
Regards,
Quamrul Khan
Copy link to clipboard
Copied
You are correct in that a login is required. however along with the initial access token you also get a refresh token. You can use this refreh token to automatically refresh the access token going forward.
The refreh token does not expire, unless it's not used for 60 days
https://secure.eu1.echosign.com/public/static/oauthDoc.jsp
Refresh tokens expire after 60 days of inactivity. In other words, a client can continue to use a refresh token indefinitely, as long as it is being used at least once every 60 days - otherwise it expires automatically. Refresh tokens can also be revoked by the authorizing user, so the application must be prepared for revoked access at any time.
Copy link to clipboard
Copied
Here where the step: