Live data

Overlays that keep themselves up to date

Point an overlay at public data on the web, such as match results, the weather or prices, and it updates itself while you're live. Nobody has to type a thing. You build it in the studio's Data tab, or let your AI build it.

  • No programming
  • Tested before you go live
  • Source always credited
How data gets there

From the web to the picture, left to right

The Data tab draws an overlay's data as a flow. This is the Weather corner from the library: the host types a town, two sources fetch the weather for it, and one step picks the next hours.

Sources

Where the data comes from

A source reads a public address on the web. BeamBubble's servers do the fetching, not your phone, and only while a bubble that uses the overlay is live.

JSON link

Any public link that answers with JSON, the language most data services speak. Fetched again as often as every 10 seconds.

Web page

A page read as text, as often as once a minute. Pick values out of it with a meta tag or a pattern.

WebSocket

A live connection: every message comes through the moment it's sent. The overlay can say what it wants when it connects.

Event stream

Server-sent events: a steady stream of updates over one connection, picked up again where it left off after a break.

Pusher socket

Many live results services push updates through Pusher. The overlay listens to the channels you choose.

The host's settings

A link, a team or a town the host fills in before the live, so one overlay works for every match or place.

Steps

Shape it with steps

Data rarely arrives the way you want to show it. Steps take what a source gives and turn it into exactly what viewers need, one step after another.

Today each source and step is set up in a small box of JSON in the Data tab: a few named settings, no programming. Rather not write it? Your AI knows every step and can write the whole flow.

  • List: keep the items you want, sort them, take the first few, reshape each.
  • Latest value: hold the newest value from any of several sources.
  • Rows by id: keep a live table, filled from a list and changed by updates.
  • Table to rows: turn a table of cells into rows with named values.
  • Flatten: join the lists inside a list into one.
  • Newest items: the latest events, newest first, without duplicates.
  • Count per minute: how many events came in the last minute, or the time you set.
  • History: a number over time, one point per interval.
  • Pick from text: a value out of a web page.
Test

See the data before you go live

  1. Press Test

    The overlay runs in a sandbox for up to five minutes, with test values for the host's settings. The stage shows the real data.

  2. Look inside every step

    Each source and step shows what it holds right now, and the log says what happened, so a typo in a link is found in seconds.

  3. Click a value to use it

    Click a value in a step's sample, and it's added to what viewers get. Then put it in any text in Layout.

Your own data

Connect a data source of your own

Any public link that answers with data can feed an overlay. Here is the whole way, with a real example: the temperature at your pitch, from Open-Meteo's free weather service.

  1. Find the link

    Look for a link that shows data when you open it in a browser, without signing in. For the weather at your pitch, put its coordinates into Open-Meteo's link.

  2. Credit it, then add it

    With nothing selected, write the Data credit in the Overlay settings ("Weather data by Open-Meteo.com"): an overlay that fetches data needs one. Then, in the Data tab, choose + Add a source or step, and JSON link.

  3. Paste your link and test

    In the source's Settings (JSON), change "url" to your link and "every" to how often to fetch it, and Apply. Press Test, then click temperature_2m under current: it's added to what viewers get.

  4. Put it in the picture

    In Layout, add a text, pick temperature_2m under Value and whole numbers under Format, and Insert. Choose Use in bubbles, then open Overlay in your bubble and pick it: the temperature is in your next live.

The link
https://api.open-meteo.com/v1/forecast?latitude=57.71&longitude=11.97&current=temperature_2m
What it answers (shortened)
{
  "current": {
    "time": "2026-11-19T11:15",
    "temperature_2m": 0.9
  }
}
The source's settings, after your changes
{
  "id": "json",
  "type": "http.json",
  "url": "https://api.open-meteo.com/v1/forecast?latitude=57.71&longitude=11.97&current=temperature_2m",
  "every": "15m"
}

Keep "id" and "type" as the studio wrote them. Open-Meteo updates the weather now every 15 minutes, so fetching more often gains nothing.

The text in Layout
{temperature_2m|int}°

Viewers see 1°, and it changes by itself.

Can't find the link, or does the data need shaping? Tell your AI what you want to show and where it comes from, and it writes the whole flow. Build it with your AI.

Before you start

Which data sources work

The quick test: open the link in a private browser window. If you see the data without signing in, an overlay can read it.

Works

  • Public links that answer with JSON, text or a web page, over http or https.
  • Live feeds over a WebSocket, server-sent events or Pusher that are open to the public.
  • Links a web page couldn't read by itself (blocked by CORS): BeamBubble's servers fetch the data, not your viewers' browsers.
  • Your own data at a public address, such as a JSON file on your club's website.

Doesn't work today

  • Services that need an API key, a token or a sign-in: an overlay can't send one.
  • Addresses on a private network, such as a scoreboard computer on the hall's own wifi.
  • Ports other than the standard ones (80 and 443).
  • Answers over 2 MB, or a link fetched more often than every 10 seconds (a web page: every minute). For faster data, use a live feed.

Never put a key or a password in a link. An overlay keeps its links, and they go with it when you publish it to the library, export it as a file, or someone remixes it.

Use data you're allowed to show. Many free services ask for a credit, which the overlay always draws, and some allow only non-commercial use: check the service's terms.

Safe and fair

Built to be kind to viewers and data sources

The flow runs on BeamBubble's servers, never on your viewers' screens, and within limits that keep it fast and polite.

  • Only while it's needed. The flow runs while a bubble using it is live, and through a short break, then stops.
  • One run, many bubbles. Bubbles with the same overlay and settings share one run, so a data source isn't asked twice.
  • Public addresses only. No sign-ins and no private networks. Sources are fetched at most every 10 seconds (a web page every minute).
  • Values, not code. Only typed text and numbers come out of the flow, checked again before they're drawn.
  • Credit where it's due. An overlay that fetches data must name its source, and the credit is always drawn on it.
In the library

Live data overlays you can use today

FAQ

Live data questions

What data can an overlay show?

Anything public on the web that answers with JSON or text, or streams updates over a WebSocket, server-sent events or Pusher: results, weather, prices, earthquakes, space weather. Addresses that need a sign-in or an API key can't be read today.

How fast does it update?

A JSON link can be fetched every 10 seconds, a web page every minute, and live connections come through as they arrive. A change reaches the picture within a second.

Does it use my phone's data or battery?

No. BeamBubble's servers fetch and shape the data. Your phone only streams the picture, as always.

What happens if the data source stops answering?

The overlay keeps showing the last values, the host sees that the data is delayed, and the live goes on as usual. The flow tries again by itself.

Do I need to understand JSON?

Today the Data tab's settings are written in JSON, so it helps. If you'd rather not, start from an overlay in the library, or describe what you want to your AI and let it write the flow. Build it with your AI.

Free to use today

Your people are waiting for the link.

Make a bubble in a minute, send the link, and go live from the phone in your pocket. Viewers watch in their browser, no app needed.