Export the whole filtered event set as CSV or JSON
Takes the SAME body as /api/get_all_events_with_count/ and returns every matching event as a downloadable file rather than one page as JSON. It shares that endpoint's request parsing, so the filters, the monthly per-view quota, the suppression bucket and the impact-tag predicate all mean exactly what they mean on the events page: the file covers the rows the screen was showing, never a different set. Any cursor in the body is ignored, because an export is the whole set rather than the page you had scrolled to. Unlike the list, every row carries the heavy fields (page URL and call site, origin, repr_created and trace), since a finding you cannot reproduce is not worth exporting. taint_chain is the forensic chain and is blank for non-admin accounts, matching GET /api/event/{id}; the column is present either way so a non-admin file and an admin file stay diffable. The export is capped at 50000 rows: CSV announces the cap as a final row beginning TRUNCATED, and JSON sets truncated to true, because a silent stop at the cap is indistinguishable from having found exactly that many events.
This is a read: a read-only API key may call it.
Request
- Base URL: https://eyalsec.com
- URL: https://eyalsec.com/api/events_export
- Auth: one of:
- API key in header X-API-Key
- API key in cookie __Host-es2session
Query parameters
csv (the default) or json. Any other value is a 400 naming the two, never a silent fallback.
Request body
Response
OK.
Changes
No recorded changes to this operation across all 1 revision of this API.