Download

Data Feeds

Bring live data in over an HTTP poll, a WebSocket or a webhook push — JSON, XML or text — and fold it into the store.

How a payload's text becomes fields.

Format sits next to the transport. Auto picks by the content type, then by the first character of the body. JSON, XML and Plain text force one; a body that does not parse with a forced format degrades the feed instead of painting garbage.

XML is turned into an object, so the Binder tree and field paths work the same as JSON:

xml
<match id="7">
  <home score="2">Ajax</home>
  <away score="1">PSV</away>
</match>

$.match.@id          → 7
$.match.home.@score  → 2
$.match.home.#text   → "Ajax"
  • Attributes are @name; the text of an element that also has attributes is #text.
  • An element with only text is its value: <name>Ajax</name> reads as name → “Ajax”.
  • Repeated elements become a list. A path like $.table.row[0].team also reads a single row, because some feeds send one row as an element rather than a list of one.
  • Values that look like numbers become numbers, except ones with a leading zero (“007” stays text).