Glossary
Event log
An ordered list of events you read with a cursor. Webhooks deliver the same records, so you can pull them where webhooks are off.
Updated November 12, 2026
- Also called
events endpoint
At OneLifeVibe
- Every approved OneLifeVibe Platform client starts on the free Sandbox: one key for the world catalogue, the tool registry, the network directory tool and the event log, 1,000 calls a day at 10 requests a minute, and no webhooks. No card is needed.
- A platform key can call the world catalogue, the tool registry, the network directory tool (olv_list_worlds) and the event log. For a person's own data, connect an assistant to the account connector at https://onelifevibe.com/mcp, where the person signs in. GET /tools marks each tool with callable_with_platform_key.
Related terms
What it means
The event log, also called the events endpoint, is the ordered list of events you can read with a cursor. Each record describes something that happened, and the order reflects when it happened, so you can work through the list and resume from a known position.
You read it in pages. The API returns a set of records and a cursor; you send the cursor back to get the next set. It holds the same records webhooks deliver. A webhook pushes a record to your endpoint as it happens, while the event log lets you pull that record later. Same shape, two delivery methods, so one parser can handle both.
How it works
Request the first page, keep the cursor from the response, then send that cursor back for the next page. Repeat until the response stops returning records. Save the last cursor you processed in durable storage, a database row or a queue message, so a restart does not send you back to the top.
Cursors are opaque. Do not build one yourself, add an offset to it, or change its order. Send back exactly what you received.
Polling fits backfills, local tests and any host that cannot accept inbound HTTP. Webhooks fit production when you want low delay. A workable pattern is webhooks for the normal path and the log to recover what an endpoint missed while it was down. Poll on a timer that matches how fresh your data needs to be.
How OneLifeVibe uses it
Every approved OneLifeVibe Platform client starts on the free Sandbox. One key covers the world catalogue, the tool registry, the network directory tool (olv_list_worlds) and the event log. The Sandbox allows 1,000 calls a day at 10 requests a minute and has no webhooks. No card is needed. With nothing pushing records at you, the event log is how you read events while you build.
That key sets the scope. It can call the world catalogue, the tool registry, olv_list_worlds and the event log. It does not read a person's own data. For that, connect an assistant to the account connector at https://onelifevibe.com/mcp, where the person signs in.
GET /tools marks each tool with callable_with_platform_key, so you can check whether a tool works with the key you hold before you build a request around it.
Common mistakes
Polling too fast. Ten requests a minute and 1,000 calls a day is a small budget, and a one second loop will hit the ceiling quickly.
Waiting for a webhook in the Sandbox. There are none there. Read the event log instead, or feed saved records to your receiver.
Treating the cursor as an offset, or storing it only in memory. Send back the exact value the API returned, and write it down after the page is processed so a crash does not skip records.
Expecting a platform key to return a person's account events. Those reads go through the account connector, where the person signs in.
Questions
What is the difference between the event log and a webhook?
They carry the same records. A webhook pushes each one to your endpoint when it happens; the event log lets you pull them with a cursor, which is what you do in the Sandbox.
Does the OneLifeVibe Sandbox include webhooks?
No. The free Sandbox gives you one key with 1,000 calls a day at 10 requests a minute and no webhooks, so you read the event log with a cursor.
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.