Polymarket CLOB execution toolkit — PRO (fix 401 / invalid signature, cancel, fills, py-clob-client)
The Polymarket CLOB execution layer that doesn't silently lose orders or double-fill: correct cancel, correct fill reconciliation from /data/trades, timeout-idempotency, and an async dual-leg posting layer — built for py-clob-client. If you've been stuck on this, you're not alone You get a 401 that "should work". You get invalid signature with no hint why. Your cancel returns 404 and the order just… stays open. Your fill size comes back wrong and your bot loops. None of it is clearly documented. The free companion fixes the first three; this PRO build is the production execution layer on top. Is this what you've been searching for? "polymarket 401" / "polymarket 401 unauthorized" "polymarket invalid signature" / "polymarket signature type" "polymarket cancel order api" / "polymarket cancel all orders" "py-clob-client" / "polymarket /data/trades" / "polymarket duplicated order" You came up empty because the auth, cancel, and trade-reconciliation rules aren't spelled out — that gap is why this exists. What's inside polymarket_clob_exec_pro.py — trades reconciliation, timeout-idempotency, async dual-leg posting, signature self-check. test_polymarket_clob_exec_pro.py — 11 offline tests (mocked). EN + 中文 README, commercial license. What PRO handles that bites everyone /data/trades done right — it's a paged object {"data":[...]} (not a list), the field is match_time (not timestamp), filter by asset_id only (a FOK is the taker — a maker-address filter finds nothing), and the Indexer lags ~20s. Timeout-idempotency — on an aiohttp timeout, never blind-resubmit; the original may be on-chain and a resubmit double-fills. Confirm against trades first. Async dual-leg posting — pre-sign both legs and post over one shared keep-alive session so they land <5ms apart (vs 10–100ms with fresh TCP/TLS). signature_selfcheck — catches SignatureType/funder mismatches before they become invalid signature. Free vs PRO A free, MIT-licensed companion fixes the three classic errors (401, invalid signature, the silent-404 cancel) and side-aware fill reading. This PRO build adds the reconciliation + idempotency + async execution layer you need to run unattended. What it is, and what it isn't It builds requests and parses responses. It does not hold keys, sign, place orders, move funds, predict prices, or guarantee any fill or profit. The async layer is a reference you wire to your own signer and session. Polymarket's API can change; if an endpoint or field changes, a fix is in scope. FAQ Why does my cancel 404? It's DELETE /order with body {"orderID": "0x.."}, not DELETE /order/{id}; the body is signed. Why can't I find my trade in /data/trades? You're filtering by maker/taker address — a FOK is the taker. Filter by asset_id and read match_time. Why did a timeout cause a double position? A blind resubmit on timeout. Confirm via trades first; this kit does that. Refund — 14-day fix-or-refund Downloadable source can't be "returned." If within 14 days it doesn't work as described, send a reproduction; we fix it, or refund fully if it still can't be made to work. No refunds for changed-mind or buyer-side environment issues. Open-source companion (free): https://github.com/BlueWhale-Quant-Lab/polymarket-401-invalid-signature-cancel-order
Get it → bluewhalequantlab.gumroad.com