PY Polymarket CLOB Client V2
Python client for the Polymarket CLOB (v2)
Usage
# pip install py_clob_client_v2
import os
from py_clob_client_v2 import ApiCreds, ClobClient, OrderArgs, OrderType, PartialCreateOrderOptions, Side
host = "<polymarket-clob-host>"
chain_id = 137 # or 80002 for Amoy testnet
# Step 1: obtain API credentials using your wallet (L1 auth)
client = ClobClient(host=host, chain_id=chain_id, key=os.environ["PK"])
creds = client.create_or_derive_api_key()
# Step 2: initialize a fully-authenticated client (L1 + L2)
client = ClobClient(host=host, chain_id=chain_id, key=os.environ["PK"], creds=creds)
# Place a resting limit buy (GTC)
resp = client.create_and_post_order(
order_args=OrderArgs(
token_id="", # token ID of the market outcome — get from https://docs.polymarket.com
price=0.4,
side=Side.BUY,
size=100,
),
options=PartialCreateOrderOptions(tick_size="0.01"),
order_type=OrderType.GTC,
)
print(resp)
For Polymarket V2 outcomes, pass position_id instead of token_id:
resp = client.create_and_post_order(
OrderArgs(position_id="456", price=0.4, size=100, side=Side.BUY),
options=PartialCreateOrderOptions(tick_size="0.01"),
order_type=OrderType.GTC,
)
Provide exactly one identifier. position_id automatically selects Exchange V3
signing, including when using OrderBuilder directly, and ignores neg_risk and
any requested exchange version. Existing token_id orders retain server-selected
version routing; PartialCreateOrderOptions(version=1) or version=2 can override
it. Signed orders and HTTP payloads still use the protocol field tokenId for
both kinds of identifier.
See examples for more information.
Market Orders
from py_clob_client_v2 import MarketOrderArgs
# Market buy — amount is in USDC
# OrderType.FOK: entire order must fill immediately or it is cancelled
# OrderType.FAK: fills as much as possible, remainder is cancelled
resp = client.create_and_post_market_order(
order_args=MarketOrderArgs(
token_id="",
amount=100, # USDC
side=Side.BUY,
order_type=OrderType.FOK,
),
options=PartialCreateOrderOptions(tick_size="0.01"),
order_type=OrderType.FOK,
)
print(resp)
Position-backed market orders use the same workflow and amount units:
resp = client.create_and_post_market_order(
MarketOrderArgs(position_id="456", amount=100, side=Side.BUY),
options=PartialCreateOrderOptions(tick_size="0.01"),
order_type=OrderType.FOK,
)
Authentication
The client has two authentication levels:
L1 — wallet signature (EIP-712). Required to create or derive API keys.
client = ClobClient(host=host, chain_id=chain_id, key=os.environ["PK"])
creds = client.create_or_derive_api_key()
L2 — HMAC with API credentials. Required for order placement, cancellation, and account data.
creds = ApiCreds(
api_key=os.environ["CLOB_API_KEY"],
api_secret=os.environ["CLOB_SECRET"],
api_passphrase=os.environ["CLOB_PASS_PHRASE"],
)
client = ClobClient(host=host, chain_id=chain_id, key=os.environ["PK"], creds=creds)
Release files for py-clob-client-v2 1.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 | |
|---|---|---|---|
| py_clob_client_v2-1.2.0.tar.gz | 53.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| py_clob_client_v2-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 105.1 kB
Release files / py_clob_client_v2-1.2.0.tar.gz
| Download URL | py_clob_client_v2-1.2.0.tar.gz |
|---|---|
| Size | 53.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9781fd3655d1d8c90b7fcd666f05d4facc48b588b5d53f70a35992839634db2
|
|
BLAKE2b-256 checksum How to use checksums |
4ac480c7d75615bb82dfd2600d0fdda5829c64c231e09f38ff9a99db2c7f2dc1
|
| 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 Sep 25, 2026.
Transparency logRelease files / py_clob_client_v2-1.2.0-py3-none-any.whl
| Download URL | py_clob_client_v2-1.2.0-py3-none-any.whl |
|---|---|
| Size | 51.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c549a801ae39af47e57c8c04546d3d365b3dc2fd5638e22b563e875a44814043
|
|
BLAKE2b-256 checksum How to use checksums |
f5ee53c1582dbb19fdee3cafa1a5ba6815d67b14a337cd543eb5bfd648397d14
|
| 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 Sep 25, 2026.
Transparency log