Order Management

How orders flow through Orderly’s architecture, from placement to execution and settlement.

Order Lifecycle

When a user places an order, it flows through Orderly’s layered architecture:

1. The Broker Front-end Layer forwards the signed order request
2. The Messaging Layer verifies the request signature
3. The Engine Layer matches the order off-chain using price-time priority
4. The user receives order and execution updates
5. On execution, matched trade data is batched and uploaded to the Settlement Layer
6. After L2 inclusion, the matched trade data is publicly observable on Orderly L2
7. Each L2 batch or block publishes its batch data to Ethereum as calldata or blob data, which becomes observable after the L1 publication is available

For the visibility and MEV boundaries at each stage, see Orderly Orderbook Design.

API Reference

Orders are managed through the following APIs:

• Create order: POST /v1/order
• Batch create orders: POST /v1/batch-order batches client order submissions; it is separate from post-match settlement batching.
• Edit order: PUT /v1/order
• Cancel order: DELETE /v1/order
• Cancel all orders: DELETE /v1/orders
• Get order: GET /v1/order/{oid}
• Get orders: GET /v1/orders

For algo orders (STOP, TP/SL, BRACKET), see Algo Order Samples.