Authenticate to Verdocs via client ID / Secret authentication. NOTE: This is only suitable for
NodeJS server-side applications. Never expose your Client Secret in a Web or Mobile app! Also note
that access tokens may be cached by server-side apps (and this is recommended) but do expire after 2
hours. This expiration may change based on future security needs. Application developers are encouraged
to check the exp expiration field in the response accessToken and renew tokens after they expire.
Authenticate to Verdocs via client ID / Secret authentication. NOTE: This is only suitable for NodeJS server-side applications. Never expose your Client Secret in a Web or Mobile app! Also note that access tokens may be cached by server-side apps (and this is recommended) but do expire after 2 hours. This expiration may change based on future security needs. Application developers are encouraged to check the
exp
expiration field in the response accessToken and renew tokens after they expire.