Polymarket US
Polymarket US prediction market for CFTC-compliant orders, batch cancellations, position closing, and live trade management.
Built for US prediction-market traders that preview, place, and cancel orders in markets, batch up to 20 orders per request, and close positions cleanly.
Use Polymarket US with Snow
Snow is a personal AI assistant that builds real apps for you, and they can put Polymarket US to work.
What Snow can do with Polymarket US
These are the Polymarket US operations Snow and the apps you build with it can run. Sign in to choose which ones Snow may run without asking.
Reads36
Look at your data without changing it.
- Get Account Balances
Get the authenticated user's Polymarket US account balances. Use this read-only action to inspect buying power, balances, pending credits, and funds reserved by open orders before previewing or placing orders. Requires Polymarket US signed authentication and returns only the signed-in account's balances.
- Get Activities
Get authenticated Polymarket US portfolio activities such as trades, resolutions, deposits, withdrawals, referral bonuses, and transfers. Requires Polymarket US signed authentication and returns activity only for that account. Use type filters and sortOrder carefully when paging through history.
- Get Event By ID
Get one Polymarket US event by numeric ID from the public gateway API. Use this after discovery when the caller already has the integer event ID and needs full event details or associated market references. Do not pass slugs here; use Get Event By Slug for slugs. This read-only action does not require API key authentication.
- Get Event By Slug
Get one Polymarket US event by slug from the public gateway API. Use this after search/list discovery or when parsing a Polymarket event URL. Do not pass numeric IDs here; use Get Event By ID for integer IDs. This read-only action does not require API key authentication.
- Get League By Slug
Get a current Polymarket US v2 league by slug. Use List Leagues or Get Sport By Slug first if the slug is unknown. This is useful for confirming league metadata before listing events for a league such as "nba" or "nfl". This action does not require API key authentication.
- Get Market BBO
Get the best bid and offer for one Polymarket US market by slug. Use this lightweight top-of-book read before quoting, previewing, or explaining an order. If the agent needs depth or slippage context, use Get Market Book instead. The response is market data, not an order placement or order preview. This endpoint requires the market slug, not the numeric market ID, and does not require API key authentication.
- Get Market Book
Get the public order book for one Polymarket US market by slug. Use this before quoting, previewing, or explaining an order when the agent needs depth beyond the top of book. The response is market data, not an order placement or order preview. This endpoint requires the market slug, not the numeric market ID, and does not require API key authentication.
- Get Market By ID
Get one Polymarket US market by numeric ID from the public gateway API. Use this after market discovery when the caller already has the integer market ID and needs full market metadata. Do not pass slugs here; use Get Market By Slug for slugs. For current pricing before an order, follow with Get Market BBO or Get Market Book. This read-only action does not require API key authentication.
- Get Market By Slug
Get one Polymarket US market by slug from the public gateway API. Use this after search/list discovery or when parsing a Polymarket market URL. Do not pass numeric IDs here; use Get Market By ID for integer IDs. For current pricing before quoting, previewing, or placing an order, follow with Get Market BBO or Get Market Book. This read-only action does not require API key authentication.
- Get Market Settlement
Get settlement information for one Polymarket US market by slug. Use this only for resolved, closed, or historical market workflows where the caller needs public resolution or settlement details. It is not useful for discovering current markets or preparing trades on active markets. This endpoint requires the market slug, not the numeric market ID, and does not require API key authentication.
Creates3
Add something new to your account.
- Close Position Order
Create a live Polymarket US order intended to close an existing position in one market. Use only when the user explicitly asks to close that position. This can trade immediately, leave residual exposure if not fully filled, or be rejected for market, liquidity, risk, or funding checks; inspect the returned order state before confirming the position is closed.
- Create Multiple Orders
Submit up to 20 live Polymarket US orders in one request. Use only after the user explicitly asks to place the batch and, when practical, after previewing the same orders. This mutating action can consume buying power and create exposure across multiple markets; read per-order statuses because a batch can contain accepted, filled, and rejected orders.
- Create Order
Submit one live Polymarket US order. Use Preview Order first unless the user has already reviewed the exact order details. This mutating action can reserve buying power, fill immediately, or create real market exposure; the API may also reject the order for funding, price, market, or risk checks, so inspect the returned status before confirming placement.
Updates2
Change something that is already there.
- Modify Multiple Orders
Modify up to 20 Polymarket US open orders in one request. Use only when the user explicitly asks to change the batch. These live cancel-replace style mutations can change funding requirements, exposure, maker-only behavior, queue priority, and fill risk; the response can be partial, so confirm per-order state after modification when accuracy matters.
- Modify Order
Modify one existing Polymarket US open order. This is a live cancel-replace style mutation and should only be used when the user explicitly asks to change an order. It can alter exposure, required funds, queue priority, and fill behavior; verify the updated order state after the request when confirmation matters.
Deletes3
Remove something. This often cannot be undone.
- Cancel All Open Orders
Cancel all authenticated Polymarket US open orders, optionally scoped to specific market slugs. This is broad and destructive for remaining open quantities; omit slugs only when the user clearly asks to cancel every open order. Already executed fills and positions remain, so verify open orders afterward when confirmation matters.
- Cancel Multiple Orders
Cancel up to 20 Polymarket US open orders in one request. Use only when the user explicitly asks to cancel the batch. Cancellation removes remaining open quantity but does not undo fills or positions, and batch responses can require per-order follow-up reads to verify final state.
- Cancel Order
Cancel one Polymarket US open order by exchange-assigned order ID. This is a destructive mutation of the remaining open quantity and should only be used when the user explicitly asks to cancel. Already executed fills and resulting positions remain; confirm order state afterward when precision matters.
Related integrations
Ready to put Polymarket US to work?
Sign up free, build an app by chatting, and connect Polymarket US in minutes. No credit card required.