Skip to main content
No. The API is plain JSON over a standard WebSocket connection, so any client that speaks RFC-6455 works, including Python, Node.js, Go, and a browser tab.
Wait a few seconds, reconnect, and re-subscribe. Last-value replay means you receive the current state again immediately; see Heartbeats & Reconnection.
You’re likely subscribed to both metar.atis.<icao> and metar.obs.<icao> for the same station. Deduplicate using the pair of station and report_time; see D-ATIS Fast Lane.
You can, for internal dashboards and demos. For public-facing products, proxy the stream through your backend instead, since anything shipped to a browser is visible in DevTools.
The account returns to the Sandbox plan. Existing keys keep working, scoped back to the sandbox.demo channel and basic-tier forecasts.
Read the ack frame sent right after connecting. It always reflects your effective plan and limits, which is more reliable than hardcoding the plans table.
Yes. A channel that doesn’t exist yet fails with a channel_format error rather than closing your connection, so probing is safe.

Still need help?