> ## Documentation Index
> Fetch the complete documentation index at: https://docs.polymarket.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Place Orders
> Perps WebSocket order placement.
## AsyncAPI
````yaml asyncapi-perps.json placeOrders
id: placeOrders
title: Create Orders
description: |
Create new orders.
Requires proxy signature, see [proxy signing](/http/signing#2-proxy-signing).
Action Weight: **1 / order**
servers:
- id: production
protocol: wss
host: ws.perpetuals.polymarket.com
bindings: []
variables: []
address: /v1/ws
parameters: []
bindings: []
operations:
- &ref_1
id: PlaceOrdersSend
title: Place orders send
description: Submit new orders
type: receive
messages:
- &ref_3
id: Request
contentType: application/json
payload:
- name: Create Orders Request
description: Client submits a signed order placement request
type: object
properties:
- name: id
type: integer
description: Correlation ID for request-response matching
required: false
- name: req
type: string
description: Request type
enumValues:
- post
- sub
- unsub
required: true
- name: op
type: object
required: true
properties:
- name: type
type: string
enumValues:
- createOrders
required: true
- name: args
type: object
description: Array of orders to create
required: true
properties:
- name: iid
type: integer
description: Instrument ID
required: true
- name: buy
type: boolean
description: Is buy
required: true
- name: p
type: string
description: Price
required: false
- name: qty
type: string
description: Quantity in no. of contracts
required: true
- name: tif
type: string
description: Time in force
enumValues:
- gtc
- ioc
- fok
required: false
- name: po
type: boolean
description: Post only
required: false
- name: ro
type: boolean
description: Reduce only
required: false
- name: c
type: string
description: Client order ID
required: false
- name: tr
type: object
description: Optional trigger attached to this order.
required: false
properties:
- name: market
type: boolean
description: Whether the trigger executes as a market order
required: false
- name: trp
type: string
description: Trigger price
required: false
- name: tpsl
type: string
description: Trigger type
enumValues:
- tp
- sl
required: false
- name: grp
type: string
description: TPSL grouping
enumValues:
- order
- position
required: false
- name: sig
type: string
description: Signature in hex format
required: true
- name: salt
type: integer
description: Salt
required: true
- name: ts
type: integer
description: >-
Request timestamp. Unix milliseconds for most operations; Unix
seconds for withdrawals (must match the on-chain EIP-712
struct verified against block.timestamp).
required: true
- name: exp
type: integer
description: >-
Command-processing deadline in Unix milliseconds, not an order
auto-cancel time; the server caps it at now + 5 s, clamps
larger values to that cap, and uses that 5 s default when
omitted. Values at or before the server's clock are rejected
with HTTP 400 (command expired).
required: false
headers: []
jsonPayloadSchema:
type: object
title: Base Request
properties:
id:
type: integer
description: Correlation ID for request-response matching
x-parser-schema-id:
req:
type: string
description: Request type
enum:
- post
- sub
- unsub
x-parser-schema-id:
op:
type: object
required:
- type
- args
properties:
type:
type: string
enum:
- createOrders
x-parser-schema-id:
args:
description: Array of orders to create
type: object
required:
- iid
- buy
- qty
properties:
iid:
type: integer
description: Instrument ID
example: 1
x-parser-schema-id:
buy:
type: boolean
description: Is buy
example: true
x-parser-schema-id:
p:
type: string
description: Price
example: '100.00'
x-parser-schema-id:
qty:
type: string
description: Quantity in no. of contracts
example: '10.00'
x-parser-schema-id:
tif:
type: string
description: Time in force
enum:
- gtc
- ioc
- fok
x-parser-schema-id:
po:
type: boolean
description: Post only
default: false
example: false
x-parser-schema-id:
ro:
type: boolean
description: Reduce only
example: false
default: false
x-parser-schema-id:
c:
type: string
description: Client order ID
minLength: 32
maxLength: 32
pattern: ^[0-9a-f]{32}$
example: 550e8400e29b41d4a716446655440000
x-parser-schema-id:
tr:
type: object
description: Optional trigger attached to this order.
properties:
market:
type: boolean
description: Whether the trigger executes as a market order
x-parser-schema-id:
trp:
type: string
description: Trigger price
example: '110.00'
x-parser-schema-id:
tpsl:
type: string
description: Trigger type
enum:
- tp
- sl
x-parser-schema-id:
x-parser-schema-id:
x-parser-schema-id:
grp:
type: string
description: TPSL grouping
enum:
- order
- position
x-parser-schema-id:
x-parser-schema-id:
sig:
type: string
description: Signature in hex format
example: 0x1234567890...
x-parser-schema-id:
salt:
type: integer
description: Salt
example: 1234567890
x-parser-schema-id:
ts:
type: integer
description: >-
Request timestamp. Unix milliseconds for most operations; Unix
seconds for withdrawals (must match the on-chain EIP-712 struct
verified against block.timestamp).
example: 1767225600000
x-parser-schema-id:
exp:
type: integer
description: >-
Command-processing deadline in Unix milliseconds, not an order
auto-cancel time; the server caps it at now + 5 s, clamps larger
values to that cap, and uses that 5 s default when omitted.
Values at or before the server's clock are rejected with HTTP
400 (command expired).
example: 1767225600000
x-parser-schema-id:
required:
- req
- op
- sig
- salt
- ts
x-parser-schema-id:
title: Create Orders Request
description: Client submits a signed order placement request
example: |-
{
"req": "post",
"op": {
"type": "createOrders",
"args": [
{
"iid": 1,
"buy": true,
"p": "100.00",
"qty": "10.00",
"tif": "gtc",
"po": false,
"ro": false,
"c": "550e8400e29b41d4a716446655440000",
"tr": {
"trp": "110.00",
"tpsl": "tp"
}
}
],
"grp": "order"
},
"sig": "0x1234567890...",
"salt": 1234567890,
"ts": 1767225600000,
"exp": 1767225600000
}
bindings: []
extensions:
- id: x-parser-unique-object-id
value: Request
bindings: []
extensions: &ref_0
- id: x-parser-unique-object-id
value: placeOrders
- &ref_2
id: PlaceOrdersReceive
title: Place orders receive
description: Order ACK response
type: send
messages:
- &ref_4
id: Response
contentType: application/json
payload:
- name: Create Orders Response
description: Server responds with order ACK for each submitted order
type: object
properties:
- name: id
type: integer
description: Correlation ID for request-response matching
required: false
- name: data
type: object
description: Array of order results
required: true
headers: []
jsonPayloadSchema:
type: object
title: Base Response
properties:
id:
type: integer
description: Correlation ID for request-response matching
x-parser-schema-id:
data:
type: object
description: Array of order results
oneOf:
- type: object
required:
- status
- oid
properties:
status:
type: string
enum:
- ok
x-parser-schema-id:
oid:
type: integer
description: Order ID
example: 1234567890
x-parser-schema-id:
coid:
type: string
description: Client order ID
minLength: 32
maxLength: 32
pattern: ^[0-9a-f]{32}$
example: 550e8400e29b41d4a716446655440000
x-parser-schema-id:
x-parser-schema-id:
- type: object
required:
- status
- error
properties:
status:
type: string
enum:
- err
x-parser-schema-id:
error:
type: string
description: >-
Error identifier. For domain rejections and transport
errors (`401`/`404`/`429`/`500`) this is a stable,
machine-readable snake_case identifier that is part of
the API contract and safe to branch on, e.g.
`insufficient_margin`, `insufficient_balance`,
`order_not_found`, `reduce_only_invalid`,
`price_outside_bounds`, `position_not_found`,
`position_exists`, `open_orders_exist`,
`invalid_margin_mode`, `invalid_margin_amount`,
`margin_below_required_initial`, `account_liquidating`,
`instrument_close_only`, `instrument_settled`,
`settlement_price_unavailable`,
`settlement_insurance_insufficient`,
`settlement_invalid_state`, `unauthorized`, `not_found`.
`instrument_close_only` means user orders must reduce an
existing position; `instrument_settled` is permanent.
Settlement readiness errors leave the instrument and
accounts unchanged. For `400` it is a human-readable
validation detail whose wording may change. See the
Error handling guide for the domain identifiers.
(Post-only / Fill-or-Kill outcomes are order statuses
such as `post_only_rejected`, not rejections.)
example: insufficient_margin
x-parser-schema-id:
oid:
type: integer
description: Order ID
example: 1234567890
x-parser-schema-id:
coid:
type: string
description: Client order ID
minLength: 32
maxLength: 32
pattern: ^[0-9a-f]{32}$
example: 550e8400e29b41d4a716446655440000
x-parser-schema-id:
x-parser-schema-id:
x-parser-schema-id:
required:
- data
x-parser-schema-id:
title: Create Orders Response
description: Server responds with order ACK for each submitted order
example: |-
{
"id": 1,
"data": [
{
"status": "ok",
"oid": 1234567890
}
]
}
bindings: []
extensions:
- id: x-parser-unique-object-id
value: Response
bindings: []
extensions: *ref_0
sendOperations:
- *ref_1
receiveOperations:
- *ref_2
sendMessages:
- *ref_3
receiveMessages:
- *ref_4
extensions:
- id: x-parser-unique-object-id
value: placeOrders
securitySchemes: []
````
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.