Is it a known issue that all webhook events for tickets are broken or at the very least not logged at all?
I have an integration with webhooks on contact and company events and they all fire as expected and log accordingly. I created subscriptions on all ticket lifecycle events and none of them are logged when creating, updating or deleting tickets in the CMS.
Hi @dneustadt
A couple quick checks usually explain “silent” ticket webhooks. First, make sure your app’s subscriptions include the ticket events themselves (ticket.creation, ticket.propertyChange, ticket.deletion), the app is installed on the target portal, and the scopes cover tickets, then confirm deliveries in the app’s Webhook logs; HubSpot logs every attempt with response codes and bodies (Accounts Dashboard | HubSpot )
One subtlety: if you’re testing via bulk edits or imports, only property-change events that actually modify a value will fire; no-op updates won’t log.
If you need to validate end-to-end quickly, enroll a ticket-based workflow that flips a throwaway ticket property, which will emit a propertyChange event you can see in the logs; or temporarily use the workflow Webhook action to hit your endpoint to rule out networking issues (How to Trigger Webhooks in HubSpot Contact-Based Workflows )
Are your subscriptions on a private app or a public app in the developer account? That detail helps pinpoint scope and install mismatches. Where native events aren’t consistent enough, Stacksync can mirror ticket changes in near real time so downstream systems never miss an update.
No really sure why this answer was already marked as accepted 
We have an unpublished app and the webhooks subsequently show up as being considered legacy. As already noted the webhooks for the objects company and contact work. I create either one in the CRM and subsequently a log entry shows up and I can also register the request on our end. I did the exact same for the creation of tickets and neither is anything being logged nor can I register an incoming request. I tried the conversation events as one should be created by the ticket creation via form, but the webhook for creation of a conversation isn’t fired either. I’m now using a flow action in the support pipeline to dispatch a webhook request. For the moment, that is suffice. Still I’m sorry to say, at the very least the legacy type webhooks clearly don’t function for all the objects they claim to do.
Hi, @dneustadt 
Thank you. If you have a moment, adding your honest, clear, and direct feedback (just like above) to the HubSpot Developer Feedback form is appreciated. — Jaycee