list_matches

Reads only.

Use this for which events entered the caller's Views, newest first, with their delivery state. Use get_match instead for one Match's full snapshot. List Matches for the caller's Views (which events entered which Views, newest first). Returns a COMPACT row by default: event name/date, the firing View's name, origin ('live' = entered via a market change; 'baseline' = recorded when the View learned its current contents, analysis only, never alerted), and a few headline signal columns (the reason it matched), so a full page fits in context. For the complete frozen analytics snapshot of a firing, call get_match (by match_id) or get_event_analytics (by event_id); or pass include_snapshot=true here to inline it (heavy; avoid on large pages). Filter by view_id, event_id, since (ISO timestamp), or delivery_status. Paginated. DELIVERY TRUTH: read delivery_status, never infer delivery from a timestamp: 'sent' = an alert email actually carried this Match; 'not_sent' = terminally dropped and never sent (see delivery_reason, e.g. muted_view, locked_view, email_digests_off (the owner turned alert emails off), view_disabled); 'pending' = not processed yet, may still be sent; 'not_applicable' = was never eligible for an alert email (a baseline Match, or a View that delivers only to alert destinations). notified_at is non-null ONLY when delivery_status is 'sent'; consumed_at is when the Match was claimed whatever the outcome. NEVER report a Match as delivered unless delivery_status is 'sent'.

Parameters

Example

{ "since": "2026-05-01T00:00:00Z", "limit": 50 }