A library has a state and events: what is in it now, and the individual changes that led there.
The changes feed gives the state. The events feed gives individual changes for a set of event types. Today those are adding and removing series, and changes to reading state, rating and progress.
Warning
The events feed is internal. Everything below describes it as it works today, not a promise.
Event types#↑
event_type |
When | old |
new |
|---|---|---|---|
entry_added |
A series is added | null |
The entry as added |
entry_removed |
A series is removed | The entry as it was | null |
state_change |
Reading state changes | state before |
state after |
rating_change |
Rating changes | rating before |
rating after |
progress_update |
Chapter or volume changes | Progress before | Progress after |
- New event types will be added. Skip types you don't know, or filter by
event_typeto get only the ones you handle. - Every event has
oldandnew, so you can show "chapter 10 to 14" from one event, even when filters or paging hide the events around it. - One save can produce several events, such as a progress update and a state change, with the same
created_at. - Events are keyed by series. Removing a series and adding it again later gives one timeline with both runs in it.
is_privatein an added or removed entry is the value at that moment. The current value is in the library itself.
What has no events#↑
- Changes to notes, start and finish dates, reread count, read link, priority or privacy. Only their current value exists, in the changes feed.
- Lists: creating, renaming or deleting one, and adding or removing a series from one.
- Moving an entry to another series. Its events move with it (see Corrections), but no event says it happened.
- Anything outside the library, and anything before 18 August 2025.
Older events#↑
Events before March 2026 were rebuilt from an older audit log. Their times are exact, but some fields, such as is_private, can be missing.
Corrections#↑
Events are never deleted through the feed.
- When a user moves an entry to another series, its events move with it and are sent again with the new
series_id. A poll filtered to the old series does not see them leave. - When two entries are combined after a series merge, each keeps its own events. The removed entry's events, including its progress history, stay on the series it was on; the kept series only gets an event for the combined values. The removed entry also gets an
entry_removedevent. - Rare data repairs can remove events. Your copy keeps them until you read the events again from the start.