I'm currently trying to build a back-end system, i.e. no user interface which should send documents out for signature using Echosign.
The page for configuring the Oath token requires a redirect URL, but obviously my application doesn't have a UI and therefore no redirect URL either.
Clearly there is a whole OAuth world that I can dive into now, but I'm hoping to use their API quickly without needing to understand all the ins-and-outs of OAuth first. All of the samples seem to be based on a web interface scenario, which is not the case for me.
Any pointers would be appreciated.
The only way I've been able to do things like this in the past is to initially follow the default authentication process, then once you have an access token you can create a cron task that runs every say 30 minutes to refresh your access token before it expires.
As long as the cron task continues to run you will always have a valid access token and wont need to go through the login/redirect url process.