Glossary

Sequence cursor

A sequence cursor is the number marking how far you have read the event log. OneLifeVibe returns it as cursor and you send it back as after.

Updated November 13, 2026

Also called
after, cursor value

At OneLifeVibe

Related terms

What it means

A sequence cursor is a position in an ordered log of events. Each event has a number, and the cursor is the number of the last event you have processed. It is not an ID you look things up by and it is not a timestamp. It just says where to resume reading.

The point is that the log keeps growing at the front while you are reading it. Page offsets break in that situation: events arrive, everything shifts, and you either see something twice or skip past it. A cursor that points at a position rather than a count stays stable. You remember one number, and next time you ask for what came after it.

How it works

The usual pattern is a loop. You make a request without a cursor, get back a batch of events plus a cursor value, process the batch, then make the same request again with the cursor as the starting point. Repeat until a response comes back with nothing new, then pause and try again later or wait for a signal.

Reliability comes from ordering. If you store the cursor only after you have finished handling the events in that batch, a crash means you re-read the batch rather than lose it. That makes handlers need to tolerate seeing the same event twice, which is normally handled with an idempotency key or a check on the event ID. Storing the cursor before processing is the common mistake: it is faster and it quietly drops events when something fails.

Keep the cursor as an opaque value. It happens to be a number on many APIs, but treat it as something you store and hand back, not something you do arithmetic on.

How OneLifeVibe uses it

The events endpoint is GET /api/platform/v1/events, and it requires the events:read scope. The query parameters are after, limit, world and type. after takes the sequence cursor, and you leave it out to start from the beginning. limit takes 1 to 100 and defaults to 25. world and type narrow the results.

The response gives you events and a cursor. Store that cursor, then pass it as after on your next call to pick up where you stopped. Use limit to control batch size: a low value keeps each round trip short, a higher one, up to 100, means fewer requests when you are catching up on a large backlog.

If you filter with world or type, keep the filters the same between calls. Changes to the filter while you hold a cursor change what the cursor means for that stream.

Common mistakes

Saving the cursor before the work is done. Write it after the batch has been handled, even if that means handling an event twice on a retry.

Assuming a cursor is a total count or an offset you can decrement. It marks a position in the log. Do not add to it or subtract from it to move around.

Dropping the cursor value from the response. If you only keep the events, your next run has no idea where it stopped and starts over from the beginning. Keep the cursor alongside whatever state your integration already stores.

Questions

What is the difference between a sequence cursor and cursor pagination?

Cursor pagination is the general technique of remembering a position instead of an offset. A sequence cursor is the concrete value: here, the number OneLifeVibe returns as cursor and accepts back as after.

What happens if I leave out the after parameter on the events endpoint?

You get the log from the beginning, subject to the limit you set. That is useful for a first run or a full backfill, and the wrong choice once you already have a saved position.

See it working. The OneLifeVibe connector and Platform API put these pieces together.

Get a free key Read the docs

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.