PolyOrderbooks Python SDK
Official Python client for the PolyOrderbooks API — historical Polymarket order books, prices, and liquidity metrics.
What is covered
Polymarket crypto markets: up/down rounds (5m, 15m, 4h), price thresholds, and related event markets. Order books are captured at 1-second resolution and resolved markets are stored alongside their winning outcome.
Every plan queries at 1s, including the free tier. Plans differ on history
window and request volume — see pricing.
Install
pip install polyorderbooks
Or install the latest from GitHub:
pip install git+https://github.com/polyorderbooks/polyorderbooks-python.git
Quickstart
Get an API key from polyorderbooks.com/signup, then:
import os
from datetime import datetime, timedelta, timezone
from polyorderbooks import PolyOrderbooksClient
client = PolyOrderbooksClient(api_key=os.environ["POLYORDERBOOKS_API_KEY"])
# Or rely on POLYORDERBOOKS_API_KEY in the environment:
# client = PolyOrderbooksClient()
markets = client.list_markets(search="bitcoin", limit=5)
slug = markets["data"][0]["slug"]
end = datetime.now(timezone.utc)
start = end - timedelta(hours=6)
books = client.get_market_books(
slug,
start_ts=start.isoformat().replace("+00:00", "Z"),
end_ts=end.isoformat().replace("+00:00", "Z"),
resolution="1s",
limit=100,
)
for outcome, points in books["data"].items():
for point in points[:2]:
bids = point.get("bids") or []
asks = point.get("asks") or []
best_bid = bids[0][0] if bids else None
best_ask = asks[0][0] if asks else None
print(point["t"], outcome, "bid", best_bid, "ask", best_ask)
client.close()
markets["data"] is a list of market objects. Each item includes more fields (public_id, volume, event_slug, …); the essentials look like:
[
{
"slug": "will-bitcoin-hit-150k-in-2026",
"question": "Will Bitcoin hit $150k in 2026?",
"status": "active"
},
{
"slug": "fed-rate-cut-september-2026",
"question": "Will the Fed cut rates in September 2026?",
"status": "active"
}
]
books["data"] is keyed by outcome label ("Yes", "No"), and each snapshot is
{"t", "bids", "asks"}. Ladders are [price, size] pairs, best price first —
bids descend, asks ascend. Depth varies per snapshot, so do not assume a fixed
number of levels:
{
"t": "2026-08-19T02:00:00Z",
"bids": [[0.19, 147.34], [0.18, 63.69], [0.17, 277.77]],
"asks": [[0.20, 13.6], [0.21, 152.17]]
}
A snapshot list can be empty for markets with no captures in the requested
window, so guard before indexing bids[0] / asks[0].
Context manager usage:
with PolyOrderbooksClient() as client:
usage = client.get_usage()
print(usage["plan"], usage["limits"])
Pagination
Use metadata.next_cursor manually, or helpers:
for page in client.iter_market_books(
slug,
start_ts="2026-04-01T00:00:00Z",
end_ts="2026-04-02T00:00:00Z",
resolution="1s",
):
process(page["data"])
API coverage
| Method | Endpoint |
|---|---|
get_usage() |
GET /v1/usage |
list_series(...) |
GET /v1/series |
list_events(...) |
GET /v1/events |
list_markets(...) |
GET /v1/markets |
get_market(id_or_slug) |
GET /v1/markets/{id_or_slug} |
list_tags() |
GET /v1/tags |
get_market_metrics(...) |
GET /v1/markets/{id_or_slug}/metrics |
get_market_prices(...) |
GET /v1/markets/{id_or_slug}/prices |
get_market_books(...) |
GET /v1/markets/{id_or_slug}/books |
get_token_prices(...) |
GET /v1/tokens/{token_id}/prices |
get_token_books(...) |
GET /v1/tokens/{token_id}/books |
Authentication
Send your API key via the client constructor or POLYORDERBOOKS_API_KEY. The SDK sets X-API-Key on every request (the API also accepts Authorization: Bearer pob_…).
Errors
from polyorderbooks import AuthenticationError, NotFoundError, RateLimitError, APIError
AuthenticationError— 401NotFoundError— 404RateLimitError— 429APIError— other HTTP failures
Every error carries status_code, message and the parsed body.
RateLimitError also carries retry_after, the seconds the API asked you to
wait:
import time
from polyorderbooks import RateLimitError
try:
books = client.get_market_books(slug, start_ts=..., end_ts=..., resolution="1s")
except RateLimitError as err:
time.sleep(err.retry_after or 1)
Development
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
pytest
Links
- Product: polyorderbooks.com
- Docs: docs.polyorderbooks.com
- OpenAPI: docs.polyorderbooks.com/openapi.json
License
MIT — see LICENSE.
Release files for polyorderbooks 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| polyorderbooks-0.2.0.tar.gz | 9.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| polyorderbooks-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.3 kB
Release files / polyorderbooks-0.2.0.tar.gz
| Download URL | polyorderbooks-0.2.0.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5289eac60144f78abb39369ea20f7935a25317ed29b508c05624f298c63977d4
|
|
BLAKE2b-256 checksum How to use checksums |
8d1a945213da42e036f1334e515ac3fdce45dd676a66289c44db050cb56943d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency logRelease files / polyorderbooks-0.2.0-py3-none-any.whl
| Download URL | polyorderbooks-0.2.0-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ba4bf3a8cb1cc919043080c5d27de01a2c10298dab920bece3cac1c319449995
|
|
BLAKE2b-256 checksum How to use checksums |
b5453c7c12b9ce56895e47851fde235cd51c4e03c3b2d64321a7e9b013809b36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency log