Best practice for tracking deleted submissions via API v2 (external DB sync)

User Support API
1

Hi Kobo team/community,
I’m syncing /api/v2/assets/{asset_uid}/data into an external database (replication-style). I can detect edits using _id + _uuid changes and/or meta/deprecatedID, but I’m struggling to find a reliable way to track deletions without periodically pulling a full index of all submission IDs.

Questions:

  1. Is there any API-supported way to query deleted submissions (or “deleted since timestamp”) for an asset?

  2. If not, is the recommended approach to run a periodic “ID index sweep” (fields=["_id","_uuid"]) and set-diff locally?

  3. Are there any hidden/system fields (e.g., deleted flags, tombstones) exposed in API v2 that indicate deletion status?

Context: upcoming result limits on /api/v2/assets/{uid}/data are fine (we can page), but we want to minimize calls and payload while keeping our downstream DB consistent.
Thanks!

2

Welcome back to the community, @thomastimeandtide! Have you had a chance to go through the /api/v2/docs/ page? All the API exposed in the system has been documented there.