Authentication for API development requirements
I am starting development of a daily backend service to run the campaign summaries api. I'm having a little trouble following the 4 authentication types and use cases. It sounds like the Client Authentication flow is what is preferred, but it only generates a 12 hour token for us meaning we would have to grab a new token everytime the application runs. We have typically used refresh tokens in the past for longer access tokens and a secondary service to refresh our token on a monthly interval. I am having trouble finding documentation on how to generate the initial refresh token to use with the 4th authentication method "refresh token". If we code the service to pull a new key based on the client id and client secret multiple times a day, will this be a problem? What are the daily key generation limits using the preferred method 1 listed in documentation?
Posted by John B. about 1 year ago