Live Events
Tells an open page that something new arrived. Nothing about what.
⛔EVERY SCREEN IN THIS PRODUCT IS A RELOAD BUTTON. Frederick, 2026-09-04: "they don't have to keep hitting a reload button ... maybe you get a little red dot when there's a new transcription."
⛔AND THE STREAM CARRIES NO CONTENT, WHICH IS THE WHOLE SECURITY MODEL. An event says a KIND of work arrived -- 'transcription', 'ticket_message' -- and nothing else: no name, no address, not even a row id. Every page then refetches through the gated route it already had to be allowed to call, so an open stream can never become a way around a permission. Authentication is still required, because who is watching is worth knowing even when what they hear is nothing.
X-Accel-Buffering: no is not decoration: nginx buffers proxied responses by default, and a buffered stream delivers its first event when the buffer fills -- which for events this small is never.
Request
- Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
- URL: https://api.pigeonly.com/api/live/events
- Auth: none declared
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.