Reevit pushes live account activity over Server-Sent Events (SSE) — the same
stream that powers the dashboard’s live activity feed and the CLI’s
reevit listen. Use it when you want to observe events in real time
(dashboards, local development, ops tooling). For durable, retried delivery to
your backend, use webhooks — the two are complementary, not
alternatives.
The stream
The stream is authenticated like any other API call and scoped to your
organization and mode (test events in test mode, live events in live mode).
Each message is a standard SSE frame:
id — unique event id. SSE clients send it back automatically as
Last-Event-ID on reconnect.event — the event type, e.g. payment.created, payment.success,
payment.failed, payment.canceled. Handle unknown types gracefully —
new ones are added over time.data — the event payload as JSON.
Consuming it
Browsers and most languages have first-class SSE clients:
The fastest way to see the stream working is the CLI:
reevit listen --forward-to http://localhost:3000/webhooks subscribes to
your test-mode events and forwards them to your local endpoint, signed like
production webhooks. Pair it with reevit trigger payment.failed to
generate a real sandbox event.
Reconnection
SSE reconnects automatically. On reconnect the client resends the last seen
event id, and the stream resumes. Treat the stream as at-least-once and
observational: business-critical processing belongs on
webhooks, which are signed, retried, and replayable. 
