Webhooks: the trigger for every integration
Every adapter in this section is triggered the same way: by signed webhook events. When an entitlement, session or usage counter changes, Oclavex signs an event and POSTs it to an endpoint you choose — your own receiver, or a Webhooks by Zapier catch hook. Your side verifies and reacts; nothing has to poll. That event is the trigger behind any Zap, relay or connector here, so read the two reference pages before you wire one up:
- Receiving webhooks — how to build the endpoint:
verify the HMAC signature, answer the one-time registration challenge, and stay
correct through retries and secret rotation. Deliveries are signed and
at-least-once, so verify every one and deduplicate on the
webhook-idheader. - Webhook events — the contract: the full catalog of events you can subscribe to, the envelope and headers, and the signing scheme to check against.
Subscribe an endpoint under Settings → Webhooks, pick the event patterns you care
about — for example Entitlement.* or MeteredUsage.OverageStatusChanged — and you
have the trigger side of everything else in this section.