Polymarket US
Polymarket US prediction market platform for orders, batches, market positions, and CFTC-compliant trading workflows.
Tailored to verified US traders that submit single or batch orders to Polymarket US, cancel individual or all open orders, and close existing positions.
Sign in to connect Polymarket US
Sign in to connect an account and start using Polymarket US in your apps.
Example Use Cases
These are example ways Snow can use Polymarket US when building apps with you. This list is meant to show examples, not document every possible capability. Connecting an account does not make Snow run these automatically on its own.
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 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 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.
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.
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.
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.
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 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 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 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.