Create order
Submits a new order to Paradex.
Returns an order status object with a unique order id
assigned by Paradex. This
order id
serves as the primary identifier for the order.
The REST API performs basic validation and queues the order for risk checks
(order status
=NEW
).
Once validation and risk checks are successful, the order is sent to the matching
engine. The matching engine processes the order and updates the status to OPEN
if the order is resting. If the order is fully filled or cannot be processed, the
status changes to CLOSED
and a cancel_reason
code is provided (e.g., fully
filled or no liquidity).
Headers
Request
Order Instruction, GTC, IOC or POST_ONLY if empty GTC
Market for which order is created
Order price
Order side
Order Payload signed with STARK Private Key
Timestamp of order creation, used for signature verification
Size of the order
Order type
Unique client assigned ID for the order
Order flags, allow flag: REDUCE_ONLY
ID corresponding to the configured isolated margin account. Only for isolated margin orders
Order will be created if it is received by API within RecvWindow milliseconds from signature timestamp, minimum is 10 milliseconds
Self Trade Prevention, EXPIRE_MAKER, EXPIRE_TAKER or EXPIRE_BOTH, if empty EXPIRE_TAKER
Trigger price for stop order
Response
Created
Paradex Account
Average fill price of the order
Reason for order cancellation if it was closed by cancel
Client order id provided by the client at order creation
Order creation time
Order flags, allow flag: REDUCE_ONLY
Unique order identifier generated by Paradex
Execution instruction for order matching
Order last update time. No changes once status=CLOSED
Market
Order price. 0 for MARKET orders
Timestamp in milliseconds when order was sent to the client
Timestamp in milliseconds when order was received by API service
Remaining size of the order
Additional request information for orders
Unique increasing number (non-sequential) that is assigned to this order update and changes on every order update. Can be used to deduplicate multiple feeds. WebSocket and REST responses use independently generated seq_no per event.
Order side
Order size
Order status
Self Trade Prevention mode
Order signature timestamp
Trigger price for stop order
Order type