Other APIs / Server-Sent Events
Server-Sent Events
Browser and server clients that need one-way event streams
Connect
Endpoint: GET https://adsbiq.com/api/v2/stream?lat=26.68&lon=-80.10&radius_nm=50
curl -N "https://adsbiq.com/api/v2/stream?lat=26.68&lon=-80.10&radius_nm=50" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Accept: text/event-stream"Events and state
The first full event contains an authoritative ac array. Later delta events contain complete new objects, sparse update patches, and hex identifiers in remove. Comment frames are keepalives. Merge updates by hex exactly as for WebSocket.
Geographic and lifecycle bounds
Latitude and longitude are required. Radius defaults to 50 nautical miles and cannot exceed 250. Results are capped at 100 aircraft, cadence is five seconds, only one stream is allowed per feeder, and service-wide concurrency is capped to preserve ordinary API capacity. Each connection rolls over after approximately 55 seconds with an end event. Reconnect to receive a fresh full snapshot.
Authentication and efficiency
Use a bearer header or connect from the registered feeder IP. Native browser EventSource cannot set bearer headers; use authenticated fetch() streaming instead. API keys are not accepted in the URL, preventing proxy and browser-history leakage. Use WebSocket when you need one-second updates or long-lived high-efficiency transport.
Troubleshooting
400: coordinates or radius are missing/out of range.401: feeder authentication failed.429: that feeder already has an active SSE stream.503: bounded stream capacity or coordination is temporarily unavailable; retry with backoff.- Proxy buffering: verify the response retains
X-Accel-Buffering: no.