Intro to Push
Betting Splits Push feeds deliver real-time JSON payloads over a persistent HTTP connection, reducing the need for repeated REST API calls.
These feeds use a publish/subscribe model:
- You subscribe via a single HTTP request
- The server continuously streams updates as they occur
- A heartbeat message is sent every 5 seconds when no new data is available
Push feeds mirror the structure of their corresponding REST endpoints, making them easy to integrate into existing workflows.
Quick Start
- Open a streaming HTTP connection to the endpoint
- Provide your API key
- Optionally filter results using query parameters
- Continuously process incoming JSON messages
Example
curl -N \
--request GET \
--url "https://api.sportradar.com/betting-splits/production/stream/mlb/subscribe" \
--header "x-api-key: YOUR_API_KEY"How It Works
- The connection remains open and streams data continuously
- Updates are sent as soon as new data is available
- When idle, heartbeat messages are sent every 5 seconds
- No historical data is replayed upon reconnect
Technical Requirements
To accept data from our Push feeds, ensure that your application can:
- Can follow a HTTP redirect or use the location provided in the feeds header within one minute of your initial request.
- Can accept HTTP data transfer encoded as chunked.
Access
Each Betting Splits Push feed is available when subscribed to Sportradar Betting Splits.
Refer to your Marketplace account to confirm access.
Disconnections
Our Push service does not provide a "stateful session", there is no memory of what data has been sent previously.
Should you cease to receive heartbeat messages, or are disconnected from the Push service for any reason, re-connect using your same initial request.
Endpoint
https://api.sportradar.com/betting-splits/production/stream/{splits_product}/subscribe
Path Parameters
| Parameter | Description |
|---|---|
splits_product | mlb, nba, ncaafb, ncaamb, ncaawb, nfl, nhl, soccer, wnba |
Response Samples
Response samples will be added soon.
Notes
Push feeds remain open until explicitly closed.
Ensure your client properly handles long-lived HTTP connections and reconnection logic.
Make note of your subscriptions to ensure access to the provider and league.
