> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/order-types/burst-orders.md). # Burst orders Burst order type in Proliquid trade form

Burst order form for splitting aggressive execution into repeated batches.

Burst orders split a market-style order into repeated child batches, waiting between batches so the orderbook can refill. Use Burst when you want faster execution than TWAP but do not want one large market order to consume too much depth at once. ## Controls

Control	Meaning
Batch	Number of child orders to split the total size into.
Delay	Waiting time between child orders.
Empty max	Stops the Burst after this number of child attempts fail to fill.
Timeout	Hard time limit for the full Burst.
Max slippage	Slippage cap applied to child execution.

## Execution model Each child batch attempts to execute with the configured slippage guard. If the orderbook is thin, the delay gives liquidity time to refill before the next child order. Empty-batch and timeout controls prevent the Burst from continuing indefinitely when conditions are poor. ## Example flow 1. Choose Burst in the [Trade form](/terminal-sections/trade-form.md). 2. Enter total quantity or notional. 3. Set batch count, delay, empty max, timeout, and slippage. 4. Submit and monitor fills in [Trade history](/terminal-sections/trade-history.md) and [Order history](/terminal-sections/order-history.md). > Burst is still aggressive execution. For slow accumulation or distribution, compare it with [TWAP orders](/order-types/twap-orders.md). For maker-only intent, use [Chase orders](/order-types/chase-orders.md) or [Limit orders](/order-types/limit-orders.md) with ALO. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.proliquid.xyz/order-types/burst-orders.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.