List events for your organization.
status, participant_id, external_id, or program_id. Use from and to to scope results by ingestion time (created_at), and event_from / event_to to scope by occurrence time (event_timestamp). Both pairs can be used simultaneously (AND semantics). Use sort_by / sort_dir to control ordering. To sort by when events occurred rather than when they were received, set sort_by=event_timestamp.
Each event includes its processing status (PENDING, PROCESSING, COMPLETED, FAILED), which is useful for monitoring pipeline health or identifying events that need attention.
API key passed in the X-API-Key header.
Maximum number of results (default 50, max 200)
x >= 1Pagination cursor from previous response
Filter by program ID
Filter by event status
PENDING, PROCESSING, COMPLETED, FAILED Filter by event type
EXTERNAL, SYSTEM Filter by participant ID
Filter by external ID
Start of time window (RFC 3339) — filters on system ingestion time
End of time window (RFC 3339) — filters on system ingestion time
Start of event occurrence window (RFC 3339) — filters on event_timestamp
End of event occurrence window (RFC 3339) — filters on event_timestamp
Sort field
created_at, event_timestamp, status Sort direction: asc or desc (default)
asc, desc