Glossary
world.event
world.event is the event type a website publishes through ingest; subscribers receive it on their endpoints.
Updated November 12, 2026
At OneLifeVibe
- The OneLifeVibe platform pushes the same events you can read from GET /api/platform/v1/events: tool.invoked, client.approved, client.suspended, subscription.changed and world.event. Endpoints must be https on port 443 on a public hostname.
- topic must look like order.placed and data is capped at 32 KB. The answer is 202 with the event id and how many endpoints it was queued for; subscribers receive it as world.event.
- Body: {"id":"evt_…","type":"world.event","world":"soclasica","subject":…,"origin":"ingest","created_at":"…","data":{…},"delivery":{"endpoint_id":"whe_…","attempts":1}}.
- Event types: tool.invoked, client.approved, client.suspended, subscription.changed, world.event.
- A subscription names a topic that is not a real event type or a namespace wildcard that covers one (tool.invoked, client.approved, client.suspended, subscription.changed, world.event, or tool.*, client.*, world.*, *).
Related terms
What it means
An event type is the label a publisher puts on something that happened, and subscribers use it to decide what to handle. world.event is the label for events that originate from a website through ingest. The platform also emits tool.invoked, client.approved, client.suspended and subscription.changed, which are the other event types. world.event is how work from a site reaches the same delivery path.
The publisher supplies a topic when sending the event. That topic must look like order.placed. The topic names the thing that happened, and world.event is the type subscribers see. A subscription can name world.event directly, or a wildcard that covers it, such as world.*.
How it works
You send an event to ingest with a topic and a data payload. The topic must look like order.placed, and data is capped at 32 KB. A successful call returns 202 with the event id and the number of endpoints it was queued for. A 202 means the platform accepted and queued the event; it does not prove an endpoint has received it.
The delivery a subscriber gets carries id which starts with evt_, type set to world.event, world (for example soclasica), subject, origin set to ingest, created_at, data, and a delivery record with endpoint_id which starts with whe_ and attempts. Endpoints must be https on port 443 on a public hostname.
Subscriptions route by topic. Accepted values are tool.invoked, client.approved, client.suspended, subscription.changed, world.event, or the wildcards tool.*, client.*, world.* and *. A subscription that names anything else is not a real event type and does not cover one.
How OneLifeVibe uses it
OneLifeVibe treats world.event as one of the event types it pushes to subscribers, alongside tool.invoked, client.approved, client.suspended and subscription.changed. The same events are readable from GET /api/platform/v1/events. When a website sends an event through ingest, subscribers on world.event or world.* receive it with origin ingest, the site name in world, and the publisher's data.
Use it when your integration needs to react to something that happened on a website rather than to platform activity such as a client approval or a subscription change. Register an https endpoint on port 443 on a public hostname, then subscribe to world.event or a wildcard that covers it. The 202 response gives you the event id and how many endpoints the event was queued for, which is useful for tracing the handoff from ingest to delivery.
Common mistakes
Treating 202 as proof of delivery. It confirms the platform accepted the event and queued it for a number of endpoints. The delivery record exposes attempts, so check what actually arrived at your endpoint.
Sending a topic in the wrong shape or sending data over 32 KB. The topic must look like order.placed, and data has a 32 KB cap. Keep the payload inside that limit before you send.
Subscribing to a topic that is not on the accepted list. Valid event types are tool.invoked, client.approved, client.suspended, subscription.changed and world.event; valid wildcards are tool.*, client.*, world.* and *. A subscription needs one of those values; a typo or an invented namespace is not a real event type. Also check that the endpoint is https on port 443 and on a public hostname, since those are the endpoint requirements.
Questions
What is the difference between topic and world.event?
The topic is supplied at ingest and must look like order.placed. Subscribers receive the event as type world.event.
Which subscription values cover world.event?
Subscribe to world.event directly, or to world.*, which is one of the accepted wildcards. The full accepted set is tool.invoked, client.approved, client.suspended, subscription.changed, world.event, tool.*, client.*, world.* and *.
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.