Browser

The native WebSocket API needs the key on the query string, since browsers can’t set custom headers on a WebSocket upgrade request.

<script>
  const ws = new WebSocket(
      "wss://stream.metar.ws/v1/ws?key=mts_live_YOUR_KEY",
    );
  ws.onmessage = (ev) => {
      const msg = JSON.parse(ev.data);
      if (msg.type === "ack") {
            ws.send(JSON.stringify({ action: "subscribe", channels: ["sandbox.demo"] }));
      } else if (msg.type === "publication") {
            console.log(msg.data.station, msg.data.temp_c + "degC");
      }
  };
</script>

Anything shipped to a browser exposes your API key to whoever opens DevTools. Use browser connections for internal dashboards and demos; for public-facing products, proxy the stream through your backend instead.

Python

The same client using websockets

Node.js

The same client using ws

Go

The same client using gorilla/websocket

Next: Best Practices

A checklist of practical tips gathered from across this reference.

Getting Started

Core Concepts

Data Channels

Protocol Reference

Guides & Examples

Resources

Python

Node.js

Go

Next: Best Practices