Read Events
API
Output
ts, then id. Two changes committed close together can appear in either order, so an event with an earlier ts can follow one already read. Every event has a unique id. A client that polls for new events therefore reads again from a since a few seconds before the last event it holds, and drops the events whose id it already has.
Event Types
An unknown type, more than 8 types, or a malformed
since or cursor is refused with 400. A sandbox ID of another organization is 404 on the sandbox route and an empty page on the organization route.