> For the complete documentation index, see [llms.txt](https://docs.sidepit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sidepit.com/use-sidepit/beta/trading/beta-orders.md). # Order Types Sidepit supports limit orders, native immediate-or-cancel market orders, cancellations, and cancel/replace. ## Limit A limit order carries an explicit positive integer price in sats per USD. It may execute at that price or better. Any unfilled quantity may rest in the order book. Explicit limit prices at the current price-band edges remain limit orders and can rest. A band-edge price is not a market-order signal. ## Market A native market order omits the price field or sends protobuf default `price=0`. It has **no user-chosen limit price** and may fill anywhere through the available opposite book within the exchange price band. In the next DLOB one-second deterministic auction, it sweeps available liquidity on the opposite side. Any unfilled remainder is canceled atomically and never rests. Terminal outcomes are: * `FILLED` — the full quantity executed; * `PARTIAL FILL` — available quantity executed and the remainder was canceled; or * `CANCELED` — nothing executed because no opposite liquidity was available. The absence of a resting order is not enough to distinguish these outcomes. Read fills and order state. ## Cancel and cancel/replace A cancel references the original complete order ID. Cancel/replace cancels that order and submits the replacement instruction through the signed protocol. Both resolve at auction cadence rather than at button-click time. Stop and trigger orders are not part of the current public order protocol. ## CCXT mapping The in-repository CCXT adapter advertises `createMarketOrder: true`. Market orders omit price and report `timeInForce: IOC`; limit orders use their explicit price. The adapter is maintained in the [Public API repository](https://github.com/sidepit/Public-API/tree/main/integrations/ccxt) and has not yet been submitted upstream to CCXT. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sidepit.com/use-sidepit/beta/trading/beta-orders.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.