This isn't a critical issue, but it's one I've found a handful of times dating back at least a year online, so it seems to be something people want. I'm currently implementing the eSignature REST API into a webapp I'm working on. The main functionality involves generating and emailing invoices from job information created and stored on the app. I've been searching for about a week now for a way to use the node SDK to generate a refresh token, however there is only a method to generate the original authorization token. I can use axios to make a post request on my frontend to generate a new token when my endpoints hit a 400 error, however I'd prefer to keep authorization and refresh tokens away from my frontend for security purposes (especially since its every 8 hours). If you could just add a slightly modified generateAccessToken() method to the API which specifies a grant type of refresh_token as opposed to authorization_token I'd greatly appreciate it.
This isn't a critical issue, but it's one I've found a handful of times dating back at least a year online, so it seems to be something people want. I'm currently implementing the eSignature REST API into a webapp I'm working on. The main functionality involves generating and emailing invoices from job information created and stored on the app. I've been searching for about a week now for a way to use the node SDK to generate a refresh token, however there is only a method to generate the original authorization token. I can use axios to make a post request on my frontend to generate a new token when my endpoints hit a 400 error, however I'd prefer to keep authorization and refresh tokens away from my frontend for security purposes (especially since its every 8 hours). If you could just add a slightly modified generateAccessToken() method to the API which specifies a grant type of refresh_token as opposed to authorization_token I'd greatly appreciate it.