API reference
Real-time events
Receive message.received notifications through an authenticated server-sent event stream.
GET /events
Select the inbox first, then send the same cookies. curl -N disables output buffering. Notifications indicate a message arrived; retrieve its content through GET /messages. The stream is scoped to the selected inbox.
curl --fail-with-body -sS -N -b cookies.txt 'https://inboxflick.com/v1/events'Connection handling
Treat the event stream as a short-lived connection. Proxies and server timeouts may close it; reconnect with backoff while the inbox remains active, and perform a message-list request after reconnecting. There is no event replay or Last-Event-ID cursor guarantee. A heartbeat comment may appear about every 20 seconds. Reconnects count toward the request-rate limit. Use polling every 5 seconds as a simple fallback; do not open parallel streams for the same inbox.
Session boundaries
No credentials in URLs. The service validates the cookie before opening a stream and rechecks mailbox access during the stream. Expired or deleted inboxes must be replaced. Extending the mailbox does not make its cookie recoverable. Event metadata is private; avoid logging it in shared build output.