Migration
Dome API Alternative for Polymarket Historical Data
Status
What happened to Dome API?
According to official Dome documentation, Polymarket acquired Dome in February 2026. All Dome APIs reached end of life on April 28, 2026. Dome directs developers to Polymarket's native APIs. See the acquisition announcement for subscription and support details during the transition.
What Dome users may need to replace
Based on Dome's public docs and SDK examples, teams typically used Dome for:
- Unified Polymarket + Kalshi market data with one API key
- Historical candlestick / price series
- Real-time market prices and order tracking
- Wallet analytics and cross-platform market matching
- Python (
dome-api-sdk) and TypeScript (@dome-api/sdk) clients
Dome documented historical Polymarket order-book snapshots via GET /v1/polymarket/orderbooks. Plan replacements per workflow — not one vendor for everything.
Dome → PolyOrderbooks migration
| Dome workflow | PolyOrderbooks equivalent | Notes |
|---|---|---|
| Historical prices / candlesticks | GET /markets/{slug}/prices with aligned metrics | PolyOrderbooks stores prices from our archive, not live Polymarket pulls. |
| Historical L2 order books | GET /markets/{slug}/books — full bid/ask ladders | Dome documented historical Polymarket order-book snapshots; PolyOrderbooks uses a different API and archive, so migration is not drop-in. |
| Market discovery (Polymarket) | GET /markets, /events, /series, /tags | PolyOrderbooks covers Polymarket crypto markets, not every Polymarket category. |
| Python SDK (dome-api-sdk) | Official polyorderbooks Python SDK on PyPI | Different client — plan a migration, not a drop-in rename. |
| Multi-platform (Kalshi + Polymarket) | Polymarket crypto focus only | Not equivalent — use Kalshi-native or multi-venue providers for cross-venue. |
| Wallet analytics & order tracking | Not equivalent | Predexon or other wallet-intelligence APIs may be a better fit. |
| Cross-platform market matching | Not equivalent | Was a Dome-specific workflow. |
Python migration sketch
# Dome (historical — service EOL April 28, 2026)
# from dome_api_sdk import DomeClient
# dome = DomeClient({"api_key": "..."})
# price = dome.polymarket.markets.get_market_price({"token_id": "..."})
# PolyOrderbooks — historical books from our archive
from polyorderbooks import PolyOrderbooksClient
client = PolyOrderbooksClient(api_key="...")
books = client.get_market_books(
"btc-updown-5m-...",
start_ts="2026-01-01T00:00:00Z",
end_ts="2026-01-01T01:00:00Z",
resolution="1s", # plan-dependent
)Download a free 1-second L2 sample to validate schema before rewriting pipelines.
Is PolyOrderbooks a drop-in replacement?
No. PolyOrderbooks is for historical Polymarket crypto market-data — not Kalshi, wallet analytics, or cross-venue matching. For the full landscape after Dome, see the provider matrix.
FAQ
Is Dome API shutting down?
Yes. According to official Dome documentation, all Dome APIs reached end of life on April 28, 2026, after Polymarket acquired Dome in February 2026.
What is a Dome API alternative?
For Polymarket-native workflows Polymarket directs developers to its official APIs. For historical L2 archives, third-party providers such as PolyOrderbooks, PolymarketData, Telonex, DepthFeed, Predexon, or polyReplay may fit depending on resolution, venue scope, and delivery model.
Can PolyOrderbooks replace Dome API?
Partially — for historical Polymarket crypto market data (prices, metrics, L2 books) via REST. It does not replace Dome’s multi-venue unified API, wallet analytics, or cross-platform matching.
Where can I get historical Polymarket order books after Dome?
Several archives document historical L2 — compare providers on our best-apis guide. Inspect a free 1-second L2 sample on PolyOrderbooks before committing to an API contract.