Heavy fields of one event (trace, origin, detail, your note; source admin-only)

Returns the large per-event fields that /api/get_all_events_with_count/ deliberately omits: trace, source, origin, repr_created, detail, source_code and sink_code, plus comment (the text of your note on the event, empty when there is none), extension ({id, name, version, label} of the browser extension an es-chromium event is attributed to, all empty otherwise) and runs (the programs that produced the event, newest first, at most 50: {run_uid, cmdline, env, count, first_seen, last_seen}, with values that look like secrets masked; env is empty unless the machine sends it, and the list is empty for an event reported without run context), and requests (the web requests an es-python event happened in, newest first, at most 50: {ip, peer, method, path, host, count, first_seen, last_seen}; ip is the client address web protection attributed the request to, peer the connection address when it differs, and query values whose names look like secrets are masked; empty outside a web request). source_code and sink_code are listings of the program's own source around the line that created the tainted value and the line that consumed it, each beginning with a "<path>:<line>" header line; both are empty unless that machine is set to send them. The id is element 7 of an events-list row. source is the forensic taint chain and is blank for non-admin accounts. Ownership is a predicate in the lookup, not a check after it, so an event belonging to another account 404s exactly like a missing one, and so does an event of a product your account no longer holds. rule_source is the value a rule's source field takes to match this event's taint source: a built-in source name, a number for one of your own sources, or any when the source is unknown.

This is a read: a read-only API key may call it.