Polymarket Python CLOB Client
Python client for the Polymarket Central Limit Order Book (CLOB).
Documentation
Installation
# install from PyPI (Python 3.9>)
pip install py-clob-client
Usage
The examples below are short and copy‑pasteable.
- What you need:
- Python 3.9+
- Private key that owns funds on Polymarket
- Optional: a proxy/funder address if you use an email or smart‑contract wallet
- Tip: store secrets in environment variables (e.g., with
.env)
Quickstart (read‑only)
from py_clob_client.client import ClobClient
client = ClobClient("https://clob.polymarket.com") # Level 0 (no auth)
ok = client.get_ok()
time = client.get_server_time()
print(ok, time)
Start trading (EOA)
Note: If using MetaMask or hardware wallet, you must first set token allowances. See Token Allowances section below.
from py_clob_client.client import ClobClient
HOST = "https://clob.polymarket.com"
CHAIN_ID = 137
PRIVATE_KEY = "<your-private-key>"
FUNDER = "<your-funder-address>"
client = ClobClient(
HOST, # The CLOB API endpoint
key=PRIVATE_KEY, # Your wallet's private key
chain_id=CHAIN_ID, # Polygon chain ID (137)
signature_type=1, # 1 for email/Magic wallet signatures
funder=FUNDER # Address that holds your funds
)
client.set_api_creds(client.create_or_derive_api_creds())
Start trading (proxy wallet)
For email/Magic or browser wallet proxies, you need to specify two additional parameters:
Funder Address
The funder address is the actual address that holds your funds on Polymarket. When using proxy wallets (email wallets like Magic or browser extension wallets), the signing key differs from the address holding the funds. The funder address ensures orders are properly attributed to your funded account.
Signature Types
The signature_type parameter tells the system how to verify your signatures:
signature_type=0(default): Standard EOA (Externally Owned Account) signatures - includes MetaMask, hardware wallets, and any wallet where you control the private key directlysignature_type=1: Email/Magic wallet signatures (delegated signing)signature_type=2: Browser wallet proxy signatures (when using a proxy contract, not direct wallet connections)
from py_clob_client.client import ClobClient
HOST = "https://clob.polymarket.com"
CHAIN_ID = 137
PRIVATE_KEY = "<your-private-key>"
PROXY_FUNDER = "<your-proxy-or-smart-wallet-address>" # Address that holds your funds
client = ClobClient(
HOST, # The CLOB API endpoint
key=PRIVATE_KEY, # Your wallet's private key
chain_id=CHAIN_ID, # Polygon chain ID (137)
signature_type=1, # 1 for email/Magic wallet signatures
funder=PROXY_FUNDER # Address that holds your funds
)
client.set_api_creds(client.create_or_derive_api_creds())
Find markets, prices, and orderbooks
from py_clob_client.client import ClobClient
from py_clob_client.clob_types import BookParams
client = ClobClient("https://clob.polymarket.com") # read-only
token_id = "<token-id>" # Get a token ID: https://docs.polymarket.com/developers/gamma-markets-api/get-markets
mid = client.get_midpoint(token_id)
price = client.get_price(token_id, side="BUY")
book = client.get_order_book(token_id)
books = client.get_order_books([BookParams(token_id=token_id)])
print(mid, price, book.market, len(books))
Place a market order (buy by $ amount)
Note: EOA/MetaMask users must set token allowances before trading. See Token Allowances section below.
from py_clob_client.client import ClobClient
from py_clob_client.clob_types import MarketOrderArgs, OrderType
from py_clob_client.order_builder.constants import BUY
HOST = "https://clob.polymarket.com"
CHAIN_ID = 137
PRIVATE_KEY = "<your-private-key>"
FUNDER = "<your-funder-address>"
client = ClobClient(
HOST, # The CLOB API endpoint
key=PRIVATE_KEY, # Your wallet's private key
chain_id=CHAIN_ID, # Polygon chain ID (137)
signature_type=1, # 1 for email/Magic wallet signatures
funder=FUNDER # Address that holds your funds
)
client.set_api_creds(client.create_or_derive_api_creds())
mo = MarketOrderArgs(token_id="<token-id>", amount=25.0, side=BUY, order_type=OrderType.FOK) # Get a token ID: https://docs.polymarket.com/developers/gamma-markets-api/get-markets
signed = client.create_market_order(mo)
resp = client.post_order(signed, OrderType.FOK)
print(resp)
Place a limit order (shares at a price)
Note: EOA/MetaMask users must set token allowances before trading. See Token Allowances section below.
from py_clob_client.client import ClobClient
from py_clob_client.clob_types import OrderArgs, OrderType
from py_clob_client.order_builder.constants import BUY
HOST = "https://clob.polymarket.com"
CHAIN_ID = 137
PRIVATE_KEY = "<your-private-key>"
FUNDER = "<your-funder-address>"
client = ClobClient(
HOST, # The CLOB API endpoint
key=PRIVATE_KEY, # Your wallet's private key
chain_id=CHAIN_ID, # Polygon chain ID (137)
signature_type=1, # 1 for email/Magic wallet signatures
funder=FUNDER # Address that holds your funds
)
client.set_api_creds(client.create_or_derive_api_creds())
order = OrderArgs(token_id="<token-id>", price=0.01, size=5.0, side=BUY) # Get a token ID: https://docs.polymarket.com/developers/gamma-markets-api/get-markets
signed = client.create_order(order)
resp = client.post_order(signed, OrderType.GTC)
print(resp)
Manage orders
Note: EOA/MetaMask users must set token allowances before trading. See Token Allowances section below.
from py_clob_client.client import ClobClient
from py_clob_client.clob_types import OpenOrderParams
HOST = "https://clob.polymarket.com"
CHAIN_ID = 137
PRIVATE_KEY = "<your-private-key>"
FUNDER = "<your-funder-address>"
client = ClobClient(
HOST, # The CLOB API endpoint
key=PRIVATE_KEY, # Your wallet's private key
chain_id=CHAIN_ID, # Polygon chain ID (137)
signature_type=1, # 1 for email/Magic wallet signatures
funder=FUNDER # Address that holds your funds
)
client.set_api_creds(client.create_or_derive_api_creds())
open_orders = client.get_orders(OpenOrderParams())
order_id = open_orders[0]["id"] if open_orders else None
if order_id:
client.cancel(order_id)
client.cancel_all()
Markets (read‑only)
from py_clob_client.client import ClobClient
client = ClobClient("https://clob.polymarket.com")
markets = client.get_simplified_markets()
print(markets["data"][:1])
User trades (requires auth)
Note: EOA/MetaMask users must set token allowances before trading. See Token Allowances section below.
from py_clob_client.client import ClobClient
HOST = "https://clob.polymarket.com"
CHAIN_ID = 137
PRIVATE_KEY = "<your-private-key>"
FUNDER = "<your-funder-address>"
client = ClobClient(
HOST, # The CLOB API endpoint
key=PRIVATE_KEY, # Your wallet's private key
chain_id=CHAIN_ID, # Polygon chain ID (137)
signature_type=1, # 1 for email/Magic wallet signatures
funder=FUNDER # Address that holds your funds
)
client.set_api_creds(client.create_or_derive_api_creds())
last = client.get_last_trade_price("<token-id>")
trades = client.get_trades()
print(last, len(trades))
Important: Token Allowances for MetaMask/EOA Users
Do I need to set allowances?
- Using email/Magic wallet? No action needed - allowances are set automatically.
- Using MetaMask or hardware wallet? You need to set allowances before trading.
What are allowances?
Think of allowances as permissions. Before Polymarket can move your funds to execute trades, you need to give the exchange contracts permission to access your USDC and conditional tokens.
Quick Setup
You need to approve two types of tokens:
- USDC (for deposits and trading)
- Conditional Tokens (the outcome tokens you trade)
Each needs approval for the exchange contracts to work properly.
Setting Allowances
Here's a simple breakdown of what needs to be approved:
For USDC (your trading currency):
- Token:
0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174 - Approve for these contracts:
0x4bFb41d5B3570DeFd03C39a9A4D8dE6Bd8B8982E(Main exchange)0xC5d563A36AE78145C45a50134d48A1215220f80a(Neg risk markets)0xd91E80cF2E7be2e162c6513ceD06f1dD0dA35296(Neg risk adapter)
For Conditional Tokens (your outcome tokens):
- Token:
0x4D97DCd97eC945f40cF65F87097ACe5EA0476045 - Approve for the same three contracts above
Example Code
See this Python example for setting allowances programmatically.
Pro tip: You only need to set these once per wallet. After that, you can trade freely.
Notes
- To discover token IDs, use the Markets API Explorer: Get Markets.
- Prices are in dollars from 0.00 to 1.00. Shares are whole or fractional units of the outcome token.
See /example for more.
2 maintainers
Metadata
2 maintainers
Release files for py-clob-client 0.34.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| py_clob_client-0.34.6.tar.gz | 38.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| py_clob_client-0.34.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 82.7 kB
Release files / py_clob_client-0.34.6.tar.gz
| Download URL | py_clob_client-0.34.6.tar.gz |
|---|---|
| Size | 38.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
09c6b96e7296f6cc22466018af9ab74bcaab661a697432025e7257252c660af4
|
|
BLAKE2b-256 checksum How to use checksums |
e44d00896d81210ffae5b2e9b33b9d1e6b247d1b017c1ac98038d2a638a3ecc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 19, 2026.
Transparency logRelease files / py_clob_client-0.34.6-py3-none-any.whl
| Download URL | py_clob_client-0.34.6-py3-none-any.whl |
|---|---|
| Size | 44.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
29c39002b76f3918f2312c963db0b31941cd455bd6c6acdc1519d8ffcd70842d
|
|
BLAKE2b-256 checksum How to use checksums |
8f93cd8aa728b3ff66162be5f91002dfd7eab9defd5d8200cddf14f119e32c04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 19, 2026.
Transparency log
