← Data APIs

Data API

Oddpool: separate research coverage from subscription access

Oddpool combines public research dashboards with REST and WebSocket data for Polymarket and Kalshi. Free accounts and existing subscriptions continue, but the provider has closed new paid subscriptions.

Explore Oddpooloddpool.com
Available on
Web · API
Availability: restricted

Screenshots and interface

What is Oddpool?

The self-service interface connects event search to historical order books, trade records and normalized probability streams. Public macro, sports and market-difference views offer a way to explore the data before designing an integration. Keep the original venue and versioned references with your research so that a normalized observation can still be traced to its contract.

Larger archive work is described separately: institutional delivery can involve tick history, book reconstruction and Parquet. Those capabilities are not implied by entry-tier API access. Closed paid signups also affect planning: listed legacy prices describe existing plans, rather than an upgrade a new user can purchase.

Who it is for

  • Developers researching events across prediction venues.
  • Trading desks evaluating historical depth and trade records.
  • Macro researchers studying distributions implied by event outcomes.

Features and coverage

  • Event lookup

    Search the normalized market catalog using an API key.

  • Historical order books

    Retrieve recorded book snapshots for a specific venue.

  • Trade tape

    Read executed trades with price, size and taker-side context.

  • Probability streams

    Receive supported normalized outcome probabilities through WebSocket.

  • Versioned references

    Retain market-reference versions so saved research remains identifiable later.

  • Institutional archives

    Discuss tick history, book reconstruction and Parquet delivery with the provider for larger ingestion workflows.

  • Public research dashboards

    Explore macro, sports, market differences and other public research views.

Workflows with Oddpool

Monitor an event distribution

Find the event, save its reference IDs and stream the supported outcome probabilities. Examine the distribution across outcomes; a single headline percentage does not describe the entire event.

Scope an archive integration

Begin with a bounded historical-book and trade query. For an institutional pipeline, inspect an actual archive sample and its schema before estimating ingestion needs.

Compare venue prices

Establish matching event definitions and contract rules, then account for fees and spread when interpreting the quoted difference.

Pricing and total cost

New paid subscriptions are closed. Free accounts and existing subscriptions continue. The listed legacy Pro and Premium prices are $30/month and $100/month; neither is available for a new purchase.

Free

$0

  • Public dashboards
  • 1,000 API requests/month
  • 1 WebSocket distribution connection

Existing Pro subscriptions

$30/month — closed to new subscriptions

  • Existing paid access continues

Existing Premium subscriptions

$100/month — closed to new subscriptions

  • Existing paid access continues

Access: Closed paid signup does not mean the entire service has stopped. Confirm existing subscriber terms and any institutional delivery agreement separately.

Getting started

Before you start: New paid subscriptions are unavailable; do not design a new integration around purchasing a listed legacy upgrade.

  1. Create an API key.
  2. Send X-API-Key with an event search limited to the scope you need.
  3. Save venue and reference IDs with the returned market.
  4. Choose historical book/trade endpoints or the WebSocket stream.
  5. Check account quotas and the delivery format required by your application.

Institutional tick archives and bulk delivery require separate scoping from the entry API tier.

Read Oddpool API documentation

Useful links

What to check

  • New paid subscriptions are unavailable; do not design a new integration around purchasing a listed legacy upgrade.
  • A normalized probability does not establish the size available for execution.
  • Contract rules at each venue determine whether outcomes are comparable.
  • Institutional archive coverage and delivery must be agreed separately from self-service API access.

A closer look

Ratings & reviews

Editorial rating
3.0/ 5
0 user reviews

Our take on Oddpool

Public research views and documented data interfaces remain useful. Closed new paid subscriptions materially constrain upgrades and new production integrations, while existing-account and institutional terms need separate confirmation.

Based on documented features, setup and access terms. How we rate

User reviews 0

The main score switches to user ratings after 5 published reviews.

Be the first to share your experience

A specific example helps the next person choose the right tool.

Related tools

Browse category

Frequently asked questions about Oddpool

Can I start without an institutional contract?

Yes. The free self-service tier includes 1,000 API requests per month, public dashboards and 1 WebSocket distribution connection.

Can I subscribe to Pro or Premium now?

The provider has closed new paid subscriptions. Free accounts and existing subscriptions continue; the listed legacy paid prices are not new-purchase offers.

Does the historical API include trades?

Yes. It documents trade endpoints as well as historical order-book data.

How are large archives delivered?

The institutional offering describes Parquet-oriented workflows. Agree coverage, delivery and terms with the provider rather than assuming the entry API tier includes them.