"Webhooks are set up for a HubSpot app, not individual portals. Any portals that install your app (by going through the OAuth flow) will be subscribed to any webhook subscriptions set up for the app."
Once you create your app , however, you will only need to go through the OAuth flowonce to connect the integration, provided you have infrastructure to refresh access tokens every six hours.
Plenty of customers use OAuth apps for their in-house integrations.
Once you create your app , however, you will only need to go through the OAuth flowonce to connect the integration, provided you have infrastructure to refresh access tokens every six hours.
Plenty of customers use OAuth apps for their in-house integrations.
Just to clarify your last statement about "infrastructure to refresh access tokens".
Do you mean that unless an access token is refreshed before expiry, the webhooks are not going to fire? I was planning on only refreshing when a webhook is received in order to get more data.
Thanks for bringing this up — I should have been clearer.
Webhook notifications will continue to fire as long as your app is connected. You do not need up-to-date access tokens to receive these requests. Thus, if your app passively listens for notifications, you could complete the OAuth flow once and never refresh your access tokens.
If you wish to request or manipulate any data, however, you will need to refresh access tokens.