Read, write, delete, and audit event data — the primary data type in AMS.
Events represent the majority of data stored in AMS. They are saved against Event Forms, which define their schema. Event Forms are fully configurable via the AMS UI.
Recommended read pattern: use POST /api/v1/synchronise with caching and lastSynchronisationTimeOnServer rather than search or filter endpoints. Only pull the full dataset on first sync — on subsequent calls pass the timestamp returned by the previous response to fetch only new or changed records.
Never hardcode
lastSynchronisationTimeOnServerto0or a fixed value. Doing so forces a full history scan on every run, which causes server-level memory exhaustion under concurrent load.
Learn more: Introduction to Data Entry, Event Forms