Deleted Items

When a record leaves the catalog, your delta sync sees a compact tombstone row on the same dateModifiedFrom loop — one watermark covers both updates and removals.

What a tombstone is

A tombstone is the same envelope as a normal feed row, stripped down to the bare identifying fields plus a removal marker. It tells a long-lived mirror that an identifier it cached has left the catalog — hard-deleted, soft-deleted (“trashed”), or merged into another record — so you can drop or redirect the row. Removals ride the same delta loop you already run for updates: there is no second endpoint and no second watermark.

Do not confuse the two status families: eventStatus describes the schedule of a live event, while deletionStatus appears only on a tombstone after a record has left the catalog.

When they appear

Only on delta polls — never on catalog browsing.

eventStatus values

The scheduling state of a live event. Keep the row and update its presentation.

ValueMeaningRecommended handling
scheduledThe event is expected to happen at its current start date.Show it normally.
postponedThe event is delayed and a replacement date is not yet confirmed.Keep it, label it postponed, and avoid promising the current date.
rescheduledThe event has moved to a confirmed new date. previousStartDate may contain the prior date.Keep it and update users from the old date to the new one.
cancelledThe event will not take place as scheduled, but it remains a live catalog row.Keep it for history and joins; hide it or clearly label it in upcoming views.

All four values arrive on normal rows and can change in later delta polls. Always persist eventStatus on upsert. None of these values is a tombstone discriminator.

deletionStatus values

A single discriminator carries the removal class. Live rows omit the field entirely.

ValueMeaningExtra fieldsWhat to do
deletedHard-deleted upstream. The identifier is gone and will not be re-used.deletedAtDrop the row from your cache.
trashedSoft-deleted upstream. This class is emitted for events only and is not an eventStatus value.deletedAtTreat the same as deleted and drop it. If restored upstream, it can later return as a normal live row.
mergedFolded into another record. This row’s identifier is the loser; mergedInto is the survivor.deletedAt, mergedIntoRepoint cached references to mergedInto.

mergedInto is the next-hop survivor only. If a survivor later merges again, that produces another tombstone pointing at the next survivor — walk merges as they arrive across delta windows.

Wire shape

A single delta page can mix live rows and tombstones.

A page from GET /v3/events?dateModifiedFrom=2026-04-12T00:00:00Z can include live rows and any supported tombstone class together. Tombstone rows carry only @type, identifier, deletionStatus, deletedAt, dateModified, and (on merged) mergedInto — everything else is omitted.

{
"success": { "code": 200 },
"pagination": {
"page": 1,