GuidePlatformv1
Unary Protocol Thread Webhook
For apps that send every webhook for every customer to a single URL — the platform splits the firehose by customer and event type.
Some apps — HubSpot, Zoom, Mindbody — send every webhook event for every one of their customers to a single endpoint URL. There's no per-customer, per-event subscription; one URL receives the whole firehose.
A Unary Protocol Thread webhook handles that case. APIANT runs a single receiver per app at a fixed URL; each automation that wants events filters on the customer ID and event name it cares about. The platform splits the firehose so each automation only sees its own events.
When to use
- The vendor exposes only one webhook URL for the whole system.
- Each event is tagged with a customer ID and an event type in the payload.
- You want webhook-level latency for an app that won't issue per-account URLs.
Examples
- HubSpot — events route by
portalId+subscriptionType. - Zoom — events route by
account_id+event. - Mindbody — events route by
siteId+eventId.
This is an advanced trigger. For most apps, Self-Registering Webhook or Service Webhook is the right choice.
Last updated May 4, 2026