Skip to main content
All orders on Polymarket are expressed as limit orders. Market orders are supported by submitting a limit order with a marketable price — your order executes immediately at the best available price on the book.
The SDK handles EIP-712 signing and submission for you. If you prefer the REST API directly, see Authentication for constructing the required headers and the API Reference for full endpoint documentation including the raw order object fields and request/response schemas.

Order Types

  • GTC and GTD are limit order types — they rest on the book at your specified price.
  • FOK and FAK are market order types — they execute against resting liquidity immediately.
    • BUY: specify the dollar amount you want to spend
    • SELL: specify the number of shares you want to sell

Limit Orders

The simplest way to place a limit order — create, sign, and submit in one call:

Two-Step Sign Then Submit

For more control, you can separate signing from submission. This is useful for batch orders or custom submission logic:

GTD Orders

GTD orders auto-expire at a specified time. Useful for quoting around known events.
GTD orders expire one minute before their stated expiration as a security threshold. To set an effective lifetime of N seconds, use now + 60 + N. In addition, the expiration must be at least three minutes in the future — orders expiring sooner are rejected — so the minimum effective lifetime is about two minutes.

Market Orders

Market orders execute immediately against resting liquidity using FOK or FAK types:
  • FOK — fill entirely or cancel the whole order
  • FAK — fill what’s available, cancel the rest
The price field on market orders acts as a worst-price limit (slippage protection), not a target execution price.

One-Step Market Order

For convenience, createAndPostMarketOrder handles creation, signing, and submission in one call:

Post-Only Orders

Post-only orders guarantee you’re always the maker. If the order would match immediately (cross the spread), it’s rejected instead of executed.
  • Only works with GTC and GTD order types
  • Rejected if combined with FOK or FAK

Batch Orders

Place up to 15 orders in a single request:

Order Options

Every order requires two market-specific options: tickSize and negRisk. For details on signature types (0 = EOA, 1 = POLY_PROXY, 2 = GNOSIS_SAFE, 3 = POLY_1271 deposit wallet), see Authentication.

Tick Sizes

Your order price must conform to the market’s tick size, or the order is rejected.
The 0.0025 (0.25¢) tick size applies only to World Cup to advance, moneyline, spreads, and totals markets. Always fetch the market’s tick size before quoting rather than assuming a value.

Negative Risk

Multi-outcome events (3+ outcomes) use the Neg Risk CTF Exchange. Pass negRisk: true for these markets.
Both values are also available on the market object: minimum_tick_size and neg_risk. In Rust, the order builder auto-fetches both — you don’t need to look them up manually.

Prerequisites

Before placing an order, your funder address must have approved the Exchange contract to spend the relevant tokens:
  • BUY orders: pUSD allowance >= spending amount
  • SELL orders: conditional token allowance >= selling amount
Order size is limited by your available balance minus amounts reserved by existing open orders: maxOrderSize=balance(openOrderSizefilledAmount)\text{maxOrderSize} = \text{balance} - \sum(\text{openOrderSize} - \text{filledAmount})
Orders are continuously monitored for validity — balances and allowances are tracked in real time. Any maker caught intentionally abusing these checks will be blacklisted.

Sports Markets

Sports markets have additional behaviors:
  • Outstanding limit orders are automatically cancelled once the game begins, clearing the entire order book at the official start time
  • Marketable orders have a 1-second placement delay before matching
  • Game start times can shift — monitor your orders closely, as they may not be cleared if the start time changes unexpectedly

Response

A successful order placement returns:

Statuses

Selected crypto and finance up/down markets apply a 250 ms taker delay to marketable orders. To check a specific market, call GET https://clob.polymarket.com/clob-markets/{condition_id} or SDK getClobMarketInfo(conditionID) and look for itode: true. The API waits for this short hold and returns the final order result, so these orders usually return matched, live, or unmatched rather than delayed. Orders cannot be canceled while they are pending in the delay window.

Error Messages


Heartbeat

The heartbeat endpoint maintains session liveness. If a valid heartbeat is not received within 10 seconds (with a 5-second buffer), all open orders are cancelled.
  • Include the most recent heartbeat_id in each request. Use an empty string for the first request.
  • If you send an expired ID, the server responds with 400 and the correct ID. Update and retry.

Next Steps

Cancel Orders

Cancel single, multiple, or all open orders

Order Attribution

Attribute orders to your builder account for volume credit