Sports data feed · Buyer guide

A sports data feed for live books, joined games, and signed alerts

Use REST to discover games and reconstruct history, WebSocket delivery to follow eligible live prediction books, and HMAC-signed webhooks to react to supported injury changes. Every channel refers back to the same game, market, participant, and source identifiers.

Test the API free Read the docs

sports data feed

primary buyer intent

90 US searches/month · $12.49 CPC

fresh DataForSEO evidence

Explicit

coverage and product limits

Direct answer

ScoreTape is a multi-channel sports data feed for prediction-market applications. It combines queryable REST records with plan-limited live book subscriptions and signed injury alerts, reducing the identifier drift that appears when batch, streaming, and event data come from separate vendors.

Live market dashboardsTrading and alerting systemsData platforms maintaining a sports event spineAgent applications combining current state with history

What you can buy

Coverage that answers a product question.

REST discovery and history

List games, open one joined record, page through eligible history, and recover state after a disconnect.

Live order-book delivery

Subscribe to eligible prediction books on paid plans while retaining venue and market identity.

Signed injury webhooks

Receive supported status changes with an HMAC signature and filters instead of polling every team page.

One identifier model

Connect streaming updates, historical queries, scores, odds, and settlements to the same normalized game document.

Integration surface

WSS /v1/ws

Start with a bounded real request. Confirm authentication, response shape, source coverage, pagination, rate limits, and missing-data behavior before planning a migration.

wscat -c "wss://api.scoretape.com/v1/ws?token=$SCORETAPE_API_KEY"

Bootstrap

Use REST to discover coverage and current game/market identifiers.

Open only the live books your plan and application require.

React

Verify webhook signatures and handle event IDs idempotently.

Recover

Re-fetch current state after reconnect and store cursors, timestamps, and source state.

Buyer evaluation

Verify the feed before you commit.

Criterion	ScoreTape approach	Acceptance test
Channels	REST, WebSocket, and signed webhooks	Test each required workflow
Reconnect	REST state supports recovery	Simulate dropped connections
Identity	Shared game and market model	Trace one event across channels
Capacity	Plan-based live-book limits	Size peak simultaneous subscriptions
Cadence	Venue/source behavior disclosed	Measure live target markets

Product boundaries to retain in the decision

Prediction-market depth is forward-captured and cannot be reconstructed after a market closes.
Sportsbook history differs by league: NFL closing lines reach 1999 and the five major European domestic soccer leagues reach 2000/01; other competitions have shorter or forward-growing coverage.
Live WebSocket capacity and retained history depend on plan. REST discovery is available on every tier, but buyers should verify current limits before production sizing.
ScoreTape is independent and is not an exchange, sportsbook, league, or source of betting recommendations.

Questions buyers ask

Clear answers before checkout.

Which delivery methods are available?

REST is used for discovery and historical/current state, eligible paid plans add live prediction-book WebSocket capacity, and supported injury changes can be delivered through signed webhooks.

How many live books can I subscribe to?

Capacity depends on the active plan. Verify current limits and peak concurrency against the pricing and account surfaces before production deployment.

Are webhook messages signed?

Yes. Injury status-change webhooks use HMAC signing. Consumers should verify signatures, enforce idempotency, and avoid logging secrets.

Can I recover after a disconnect?

Use REST to reload current state and identifiers, then resubscribe. Applications should retain their own receipt times and treat venue-specific capture behavior explicitly.

Pricing

Choose capacity, not venues

One account and one API for the complete ScoreTape lineup. Polymarket and Kalshi sports coverage ships together; tiers change history, throughput, and live-book concurrency.

Explorer

$0free, no card

A limited sample of the complete ScoreTape API.

Start free

7-day unified history
Sports REST: Polymarket + Kalshi
Read-only API, 1 req/sec
Sub-second event-driven snapshots
BTC markets (latest, capped)
Live WebSocket stream: 1 BTC subscription
Backtest Lab + 1 paper-trading strategy

Quant

Desk Lite

$79per month

3× the history, 2× the throughput of Quant.

Get Desk Lite

90-day unified history (3× Quant)
API 50 req/sec, 3,000 req/min
Everything in Quant
Every supported venue — no add-ons
Sports REST + 2 live sports books
Live WebSocket: 25 subscriptions, 2 connections
15 paper-trading strategies

Desk

Full archive

$200per month

Dedicated capacity for systematic desks.

Get Desk

Full historical archive — our deepest window
Sports full archive across every supported league
Dedicated capacity, 100 req/sec
6,000 req/min sustained
Everything in Desk Lite
Priority backfill requests
Live WebSocket: 100 subscriptions, 5 connections, wildcards + 3 sports books
7-day production-latency evaluation available on request
40 paper-trading strategies

Continue evaluating

Test your real league and workflow.

Create a free key, inspect current coverage, and run representative requests before choosing capacity.