We have a WordPress site and associated mailing list that we're porting to Constant Contact. We'll be using the OAuth2 flow, and we've registered our application, and authenticated to get an authorization code, but it sounds like that code will expire unless we generate a token and keep refreshing it if it's not used, perhaps once per hour, according to some documentation (https://developer.constantcontact.com/api_guide/faqs_manage_applications.html under "Make access tokens last longer?"), or perhaps once every two hours. It seems unwieldy to have to refresh tokens every hour (or two), but is there a better solution than adding a cron script on the server that runs once every hour to refresh tokens? This seems cumbersome (almost 9,000 executions per year) and fragile...if something goes wrong with that script, the API will fail. Are we missing a more reliable / elegant solution for using the Constant Contact API with OAuth2 while needing to avoid constant user logins for authentication? Thank you.
... View more
