Glossary
Event types
Event types are the five kinds of record in the OneLifeVibe log: tool.invoked, client.approved, client.suspended, subscription.changed and world.event.
Updated November 13, 2026
- Also called
type filter,event type
At OneLifeVibe
- Event types: tool.invoked, client.approved, client.suspended, subscription.changed, world.event.
What it means
An event type is the label on a log record that says what happened. Logs and webhook feeds mix many kinds of activity, and the type is what lets you sort them before you read the payload. You check the type first, then decide whether to act on the record or ignore it.
OneLifeVibe's log has five: tool.invoked, client.approved, client.suspended, subscription.changed and world.event. Each names a different thing that can happen across the network of sites, the assistant connector and the developer platform.
How it works
Every record carries a type alongside its data. Consumers read the type to route the record: one branch handles tool.invoked, another handles subscription.changed, and anything unmatched goes down a default path that records the record and does nothing else. That default matters. A handler that throws on an unfamiliar type will break the day a label it doesn't know arrives.
Webhook delivery and log reads use the same labels. When a payload arrives, verify the HMAC signature before you parse it, then read the type and branch. Keep the record's identifier so a repeated delivery doesn't run your handler twice.
The type filter is the other half of this. Instead of pulling everything and discarding most of it, ask for the types you actually handle and let the rest stay in the log.
How OneLifeVibe uses it
tool.invoked covers tool calls made through the assistant connector. client.approved and client.suspended track a client's state through the OAuth flow. subscription.changed covers plan changes on the developer platform. world.event covers activity on the websites themselves.
All five land in one log, so a single reader can follow a client from approval through a subscription change without stitching sources together. Which type you care about depends on what you're building: connector and tooling work leans on tool.invoked, billing and plan handling on subscription.changed.
Write your handler so a label outside the five is recorded and skipped rather than treated as a failure.
Common mistakes
Branching on the payload shape instead of the type. Fields across records can look alike, and you end up misrouting them.
Skipping signature verification because the handler only reads a log. Verify first, parse second, then route on the type.
Dropping unhandled types with no log line, which leaves you unable to tell a quiet week from a filter that stopped matching.
Assuming order. Two records sitting next to each other in the log is not a promise that everything between them reached your endpoint in that sequence.
Questions
What are the event types in the OneLifeVibe log?
There are five: tool.invoked, client.approved, client.suspended, subscription.changed and world.event. Every record in the log carries one of them.
Should my webhook handler treat every event type the same?
No. Verify the HMAC signature, read the type, then route to the handler written for that type. Send anything you don't recognize to a default path that records it and stops.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.