i think engineering did a good job designing the functionality, it’s just not clear how to “hack” an individual app and account together.
it seems to me like you probably have a lot of users who are doing exactly this, and b/c of that a streamlined solution is good to have.
i don’t think the “code” thing is standard on other OAuth platforms, though. usually you get the token(s) and then use them for future access.
here, remember, we are calling this an “app” but that’s not really what we (@integrate_hubspot and i) are trying to accomplish. we literally ONLY need the webhooks. we are never using tokens to re-establish inbound contact to the app again. we just want to setup the outbound webhooks from hubspot.
i think that’s where the confusion probably lies. your folks have lumped together the webhook functionality into apps, and i’m not saying it’s bad or wrong, it’s just different. i haven’t seen another system require OAuth to initiate an outbound webhook from an internal system before. usually that’s just a setting in the primary application. like i would expect it to be in my normal hubspot settings->integrations menu. other systems like mailchimp, campaign monitor, unbounce, etc… all allow you to setup webhooks directly in the UI.
again, it is an interesting feature, but i kindof think it belongs in both places really. as a user, i’d like to setup a webhook for my own use in my UI without having to create an app or call a developer. but as a developer, there are also uses to being able to attach webhooks to my app as well.
in this case, i believe both myself and @integrate_hubspot are acting more like end users than developers trying to create scalable solutions for publishing to the broad universe of hubspot users.