Incompatibility Between Legacy and New Private App Authentication in HubSpot #523
Description
We are migrating an app built with this SDK to HubSpot’s new Private App authentication flow. However, we’ve encountered an issue during this transition.
Previously, we used a Legacy App, which provided an Access Token and Client Secret for authentication. In contrast, the new Private App setup only provides a Client ID and Client Secret, but does not return an access token directly. What am I missing?
We are unsure how to proceed with the new authentication method, as our existing implementation relies on the having an access token. Any clarification or guidance on how to authenticate using the new Private App credentials would be greatly appreciated.