Satori Docs

Your definitive guide to subscribing and publishing live data

Subscribe to Live Data Direct link

This article presents the topics on:

  • Exploring and locating the live data in Satori
  • Subscribing to a live data channel
  • Subscribing to filtered live data

Discover Live Data for Your App Direct link

All public live channels are available in the Live Data Portal with the following information:

  • Channel title
  • Description of the channel
  • Integrated Web Console for inspecting live stream in the channel
  • RTM credentials you need to supply when subscribing to the channel
    • Appkey
    • Endpoint
    • Channel Name
  • SDK subscription examples with the corresponding connection credentials

Locate the live channel to feed the live data to your app and explore the channel. You can work out your use cases by inspecting live data, pausing the stream, and applying views in the Web Console.

Subscribe to Live Channel Direct link

Implementation details of subscribing to a live channel is the same as to a regular project channel. See Overview and Subscribing for the core concepts, API and SDK examples.

Your client implementation can subscribe to one or more live channels over the same connection, using these connection credentials available on the channel page in the Live Data Portal:

  • Appkey
    Your permanent Appkey is available on the live channel page when you are signed in to Satori through the Dev Portal. This key can be used to subscribe to all live channels and has no expiration.
    When you are not signed in to the Dev Portal, you see a temporary key guaranteed to work for seven days.
  • Endpoint
  • Channel Name

Each channel page in the Live Data Portal also includes the SDK codes to subscribe to that channel.

Streamviews to Filter Live Data Direct link

Some client implementations may receive and process all messages in a live channel while others may require a selective stream manipulation. For clients working off massive live data, subscribing to a subset of filtered data is recommended and probably even required.

Streamviews enable subscribers to filter messages based on specific user conditions or to sample messages over a time period. A client can request a subscription with a streamview using an SQL expression. The subscriber only receives the messages meeting the streamview criteria. The views can change dynamically.

Streamviews support querying, aggregation, message merging, traffic rate control, and the merged last state from the history.

A streamview is only applied to a specific subscription and does affect other subscribers. A client can have multiple streamviews of the same channel.

See Subscribing with view and Streamviews for details on streamviews.

Related Articles

See the following articles for additional information on the topics discussed above.