Reduce-Only Orders — Guide and Record Resources
Check the intended position change and exact venue flag without treating reduce-only, close-all and trigger-close settings as interchangeable. Find the guide, blank records and documented resource comparison.
Reduce-Only Orders: What They Can Close
Check the intended position change and exact venue flag without treating reduce-only, close-all and trigger-close settings as interchangeable.
Read the guide10 Resources for Closing-Order Flags
Explore the exact venue references and record tools behind this task. The first entry is the Telegram offer promoted by this publisher; the others are documentation or record-management references.
Read the comparisonStart with the question
Why was my closing order refused or handled differently from an ordinary sell?
Hypothetical existing long position: 5 units. A reduce-only sell of 2, if executed under the applicable rule, reduces it to 3. The flag describes permitted intent; it does not guarantee an execution or a universal oversized-order outcome.
Read the explanation and use the blank record alongside evidence you already have. The example is hypothetical. Missing information stays unknown; this page performs no live market or account check.
Keep your own record
The CSV contains column headings only. The TXT contains the review questions and blank note spaces. Keep original evidence separately, preserve identifiers as text and leave missing facts unknown. Neither file sends data or performs an account check.
Official references
- Kraken REST — Add Order
Documents time-in-force and reduce-only parameters.
Reference checked 2 October 2026. Apply the named venue and product scope. - Binance USDⓈ-M Futures — Trade
Documents reduceOnly and Close-All parameter restrictions.
Reference checked 2 October 2026. Apply the named venue and product scope. - Bybit V5 — Place Order
Documents PostOnly, reduceOnly and trigger-price fields.
Reference checked 2 October 2026. Apply the named venue and product scope.