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.
Three ways a feed's payloads arrive.
A data feed is one kind of unit with three transports. Add one from Units → Add a unit (Data feed · HTTP poll, WebSocket or Webhook), or switch transport at the top of an existing feed. Every transport shares the same field mappings, guards, fresh flag, stale timer and Binder integration.
| Transport | How payloads arrive | Use it for |
|---|---|---|
| HTTP poll | Glider calls a URL on an interval. | REST APIs and JSON/XML endpoints that answer on request. |
| WebSocket | Glider keeps a ws:// or wss:// connection open and maps every message. It sends a subscribe text after each connect and reconnects on its own, backing off after repeated failures. | Push-style live APIs, tournament HUD managers, sockets a data provider exposes. |
| Webhook | Another system POSTs its raw body to the page's feed URL. | CS2 / Dota 2 game-state integration, scoreboard controllers, provider webhooks, your own scripts. |