Reconnecting To An Event

Establishing appropriate reconnection logic is an integral element when integrating with our APIs. Our streaming endpoint issues a heartbeat every ten seconds to validate that the connection to an event is healthy.

Disconnection from an event can happen without warning; if the connection to the WebSocket is closed or a heartbeat is not received for ten seconds, we recommend a mechanism to automatically reconnect. If a heartbeat is not received for ten seconds, an automatic attempt to reconnect to the event should be made after eleven seconds.

Possessing the correct reconnection methodology within your integration will prevent a select number of issues arising in the future. Please see Event Disconnections - this defines what alarm packets are and why these should not be mistaken for a disconnection.