Skip to main content

​
Orders API

The Orders API provides order entry and management capabilities for trading on markets.
Authentication RequiredAll Orders API endpoints require Ed25519 signature authentication. See the Authentication guide for details on signing requests.

​
Base URL

https://api.polymarket.us

​
Endpoints

​
Order Entry

MethodEndpointDescription
POST/v1/ordersCreate a new order
POST/v1/order/previewPreview order before submission
POST/v1/order/close-positionClose an existing position

​
Order Query

MethodEndpointDescription
GET/v1/orders/openGet all open orders
GET/v1/order/{orderId}Get a specific order by ID

​
Order Management

MethodEndpointDescription
POST/v1/order/{orderId}/modifyModify an existing order
POST/v1/order/{orderId}/cancelCancel a specific order
POST/v1/orders/open/cancelCancel all open orders

​
Order Types

All enum values are passed as strings in the request body:
ValueDescription
ORDER_TYPE_LIMITLimit order at specified price
ORDER_TYPE_MARKETMarket order executed at best available price
Example: 
{
  "type": "ORDER_TYPE_LIMIT"
}

​
Order Intent

Orders require an intent indicating position direction. Pass these as string values:
ValueDescription
ORDER_INTENT_BUY_LONGBuy YES shares (go long on Yes outcome)
ORDER_INTENT_SELL_LONGSell YES shares (close long Yes position)
ORDER_INTENT_BUY_SHORTBuy NO shares (go long on No outcome)
ORDER_INTENT_SELL_SHORTSell NO shares (close long No position)
Example - Buy NO shares: 
{
  "marketSlug": "your-market-slug",
  "type": "ORDER_TYPE_LIMIT",
  "price": { "value": "0.45", "currency": "USD" },
  "quantity": 10,
  "tif": "TIME_IN_FORCE_GOOD_TILL_CANCEL",
  "intent": "ORDER_INTENT_BUY_SHORT"
}

​
Order Side

The order side indicates buy or sell direction:
ValueDescription
ORDER_SIDE_BUYBuy order
ORDER_SIDE_SELLSell order

​
Order States

Orders progress through these states: 
PENDING_NEW → PARTIALLY_FILLED → FILLED
                    ↓
                CANCELED / REJECTED / EXPIRED
ValueDescription
ORDER_STATE_PENDING_NEWOrder received, not yet processed by matching engine
ORDER_STATE_PENDING_REPLACEModify request received, not yet processed
ORDER_STATE_PENDING_CANCELCancel request received, not yet processed
ORDER_STATE_PENDING_RISKOrder pending risk approval
ORDER_STATE_PARTIALLY_FILLEDOrder partially executed
ORDER_STATE_FILLEDOrder fully executed
ORDER_STATE_CANCELEDOrder canceled
ORDER_STATE_REPLACEDOrder replaced via modify
ORDER_STATE_REJECTEDOrder rejected by exchange
ORDER_STATE_EXPIREDOrder expired (GTD orders)

​
Time in Force

ValueDescription
TIME_IN_FORCE_GOOD_TILL_CANCELGTC - Remains active until filled or canceled
TIME_IN_FORCE_GOOD_TILL_DATEGTD - Expires at specified goodTillTime
TIME_IN_FORCE_IMMEDIATE_OR_CANCELIOC - Fills immediately available quantity, cancels rest
TIME_IN_FORCE_FILL_OR_KILLFOK - Must fill entirely or cancel completely

​
Manual Order Indicator

Required to indicate whether the order is placed by a human or automated system:
ValueDescription
MANUAL_ORDER_INDICATOR_MANUALOrder placed manually by a user
MANUAL_ORDER_INDICATOR_AUTOMATICOrder placed by an automated trading system

​
Execution Types

Execution events returned in synchronous order responses:
ValueDescription
EXECUTION_TYPE_PARTIAL_FILLOrder partially filled
EXECUTION_TYPE_FILLOrder fully filled
EXECUTION_TYPE_CANCELEDOrder canceled
EXECUTION_TYPE_REPLACEOrder replaced/modified
EXECUTION_TYPE_REJECTEDOrder rejected
EXECUTION_TYPE_EXPIREDOrder expired
EXECUTION_TYPE_DONE_FOR_DAYOrder done for the trading day

​
Order Reject Reasons

If an order is rejected, the reason will be one of:
ValueDescription
ORD_REJECT_REASON_UNKNOWN_MARKETUnknown or invalid market
ORD_REJECT_REASON_EXCHANGE_CLOSEDExchange/market is closed
ORD_REJECT_REASON_INCORRECT_QUANTITYInvalid quantity
ORD_REJECT_REASON_INVALID_PRICE_INCREMENTPrice not on valid increment
ORD_REJECT_REASON_INCORRECT_ORDER_TYPEInvalid order type for market
ORD_REJECT_REASON_PRICE_OUT_OF_BOUNDSPrice outside valid range
ORD_REJECT_REASON_NO_LIQUIDITYNo liquidity for market order

​
Slippage Tolerance

For market orders or close position orders, you can specify slippage tolerance: 
{
  "slippageTolerance": {
    "currentPrice": { "value": "0.50", "currency": "USD" },
    "ticks": 5
  }
}
FieldTypeDescription
currentPriceAmountReference price for slippage calculation
bipsintegerSlippage tolerance in basis points (1 bip = 0.01%)
ticksintegerSlippage tolerance in price ticks (takes priority over bips)
Real-Time Order UpdatesAfter submitting orders via REST, use the WebSocket Private Stream to receive real-time updates on order status, fills, and cancellations.

​
Complete Create Order Example

{
  "marketSlug": "super-bowl-lix-chiefs-vs-eagles",
  "type": "ORDER_TYPE_LIMIT",
  "price": {
    "value": "0.55",
    "currency": "USD"
  },
  "quantity": 100,
  "tif": "TIME_IN_FORCE_GOOD_TILL_CANCEL",
  "intent": "ORDER_INTENT_BUY_LONG",
  "manualOrderIndicator": "MANUAL_ORDER_INDICATOR_MANUAL",
  "participateDontInitiate": false
}

​
Best Practices

  1. Use string enum values - All enums are passed as strings (e.g., "ORDER_TYPE_LIMIT", not 1)
  2. Use WebSocket for updates - Subscribe to order updates instead of polling
  3. Preview before submit - Use the preview endpoint for order validation
  4. Handle rejects - Implement proper error handling for rejected orders
  5. Use synchronous execution - Set synchronousExecution: true to wait for order acknowledgment
  6. Specify manual order indicator - Required for regulatory compliance