No I didn't do this. I do not understand why I need a full OAuth 2 flow here. My reason: since I am not calling hubspot APIs (on the contrary, I need hubspot to call my webhook endpoint), then why do I need the access token for? Where would I use that access token anyway? I would need it if I use it to call into hubspot which again is not what I need to do.
I integrate with other systems like DocuSign, ChargeBee, Yodlee, and webhook APIs are a simple configuration process: 1) configure my endpoint URL, 2) configure my token or auth if needed for that endpoint, 3) set it and it's ready to go. I do not understand the whole app process here for hubspot.
I am sorry if I seem very confused, but I am indeed. Maybe I do not need this app thingy at all? Did I start down the wrong path with hubspot?
To clarify my use case: every time a contact is created in my portal (sanbox is web.brightplan.com and prod is www.brightplan.com), I want to receive a webhook api call with the payload of the newly created contact JSON. We currently have a workflow webhook that is configured to do this but we want to use the webhook API because the workflow webhook has delay that we cannot tolerate.