Polymarket
Use this guide when connecting the Polymarket option in HeyTraders.
Automated trading needs a reusable signing key. A browser-wallet session or a one-time wallet signature cannot sign orders after you leave the browser.
Before You Connect
Use a dedicated Polymarket wallet with only the funds you intend to trade through HeyTraders. An exported signing key is sensitive: anyone who obtains it may be able to control the funds associated with that wallet. Do not use a key that protects funds you are unwilling to expose to automated trading.
Create that wallet and Polymarket account through Polymarket's official flow. HeyTraders and its OpenClaw integration do not create or custody the primary wallet and do not define an alternative wallet format.
Provide the reusable signing key and the funder address shown for the account in
Polymarket. The HeyTraders connection form always submits a deposit-wallet
(POLY_1271 / type 3) connection intent. You do not choose a signature type in
the form.
| Account type | Signature type | HeyTraders connection support |
|---|---|---|
| Deposit wallet | 3 / POLY_1271 | Submitted by the form and checked first |
| Gnosis Safe | 2 / GNOSIS_SAFE | Detected automatically as an exact-match fallback |
| EOA | 0 / EOA | Not supported |
| Polymarket proxy | 1 / POLY_PROXY | Not supported |
During connection, HeyTraders derives the wallet candidates for the submitted signing key locally. It first checks the supplied funder address against both supported type-3 deposit-wallet constructions: the legacy UUPS address and the current BeaconProxy address. If neither matches, it checks the exact deterministic Gnosis Safe/type-2 address. A matching Safe is stored with a complete canonical type-2 credential profile; the form is not resubmitted and does not expose a type-2 selector. If none of those addresses match, the connection is rejected.
The funder address is the account address that holds the trading collateral or outcome tokens. For type 2 and type 3 it differs from the signing EOA address.
Connect
- In Polymarket, find the wallet/funder address that holds the account's trading balance.
- Export or otherwise obtain the reusable signing key for that account. Do not enter a CLOB API secret in the private-key field.
- In Settings → Exchanges → Add Exchange, choose Polymarket, enter the signing key, and enter the funder address. There is no signature-type selection.
- Submit the connection. HeyTraders validates the signing-key and funder-address pairing as type 3 first, then as the exact type-2 Safe fallback, and prepares the trading credentials once for the resolved account type.
For email or Magic.Link accounts, Polymarket documents its key export flow at:
https://reveal.magic.link/polymarket
Verify Before Automation
A successful connection does not verify balances, approvals, market eligibility, or live order acceptance. Confirm the displayed funder address and available balance, then place the smallest permitted test order before enabling automation.
Fees
- HeyTraders applies a 50 basis point (0.50%) builder fee to Polymarket trading routed through a connected HeyTraders account.
- Polymarket controls this rate through the HeyTraders builder profile. The broker associates eligible orders with that profile using its builder code.
- This builder fee is separate from any fees charged directly by Polymarket.
Remove Or Revoke Access
Removing the connection from HeyTraders deletes the stored connection and stops future use by HeyTraders. It does not invalidate an exported private key or revoke credentials at Polymarket. Revoke or rotate credentials through the relevant wallet or Polymarket controls where available. If a signing key may be exposed, stop using the old key and move funds to a new wallet.
Trading Notes
- Use
polymarketas the exchange id in API requests. - Polymarket symbols are token IDs, not market slugs or Polymarket URLs. Fetch
supported symbols from
GET /v1/exchanges/polymarket/tickers. - Polymarket prices represent probability and usually range from
0.0to1.0. - Market BUY orders are quote/USDC-denominated and require
quote_amount. Market SELL orders are share-denominated and useorder.qty. - Market orders support
IOCorFOKwhen the capability response reports them. - Plain Limit orders support
GTC,GTT, orIOCwhen the capability response reports them; LimitFOKis rejected. Stop-loss-limit and take-profit-limit orders supportGTCorGTT.GTTrequires a timezone-qualifiedexecution.expires_at; no expiry is added automatically. - Use
GET /v1/order-capabilities?account_id=...&exchange=polymarket&symbol=...before submitting an order. It reports availability, routing, time-in-force, and precision for the connected account and token; it does not define the request payload schema. - Polymarket does not hold HeyTraders Stop, Take Profit, OCO trigger legs, or Trailing Stop instructions natively. HeyTraders monitors the last traded outcome-token price and submits the configured Polymarket action after a managed trigger fires. See How Managed Triggers Work for trigger sources, service dependencies, and fill risks.
Fill And Settlement Status
A Polymarket trade can progress through MATCHED, MINED, and CONFIRMED, or
end as FAILED. MATCHED is a provisional fill projection; bought outcome
tokens are credited only at CONFIRMED. Do not treat MATCHED as final,
settled, or wallet-available.
For a matched close awaiting confirmation, HeyTraders can display a
pending_settlement position and removes that projection after CONFIRMED.
Market resolution can update local PnL and position displays, but HeyTraders
does not provide proof of token redemption, venue payout, or withdrawal.
Confirm balances and settlement with Polymarket.