Skip to main content
An official Python SDK is coming soon. In the meantime, this guide shows how to use TheRundown API directly with the requests library for REST calls and websockets for real-time streaming.

Installation

Configuration

Getting Sports

Getting Events with Odds

Filtering by Affiliate

Getting Player Props

Stats: sample first, then one completed event

The fixed sample is a zero-data-point schema check. For production stats, request one known completed event with a small stats_ids filter, cache the response, and fetch again only when your product needs a correction. Do not turn this into a per-team polling loop.
The production call requires access to that event’s current season. It becomes archive access after the season changes. The IDs shown are examples only: for your own request, get the event ID from the current events route and discover current supported IDs from GET /stats?sport_id=3 before filtering. Production routes depend on effective stats access. See Stats Access.

Historical Odds

WebSocket Streaming

WebSocket with Reconnection

Error Handling

Next Steps

Getting Live Odds

Detailed guide on fetching odds

WebSocket Streaming

Real-time data streaming guide

Authentication

All authentication methods

Rate Limits

Rate limit details and best practices