The Streaming Endpoint

Purpose

Run a compiled filter.

Syntax

An HTTPS request sent to

https://stream.datasift.com/<hash>

Parameter: Description:
hash
required

Pass your CSDL code to /compile first, to generate a hash for your filter.

A successful call to this endpoint returns: 200 OK.

Examples

  1. Here's an example of a call.

https://stream.datasift.com/v1/9fe133a7ee8bd2757f1e26bd78342458

Until data begins to arrive, DataSift returns a series of ticks to keep the connection open:

    {"tick":1311694600,"status":"connected","message":"Waiting for data"}

    {"tick":1311694630,"status":"connected","message":"Waiting for data"}

    {"tick":1311694660,"status":"connected","message":"Waiting for data"}

Notes

  1. All calls to the API must be properly authenticated with a DataSift username and API key.
  2. It does not guarantee to deliver every object from your stream and it cannot handle streams with a high throughput. If a stream delivers more than 20 objects per second, the /v1/stream endpoint will pause for 10 to 15 seconds.
  3. If you have an application where you need your data delivery to be as near to real-time as possible, this endpoint is the one that we recommend. Otherwise, we recommend Push for data delivery because it offers the best guarantees and a wide range of delivery destinations.