Hyperliquid Conditional Orders Guide — OCO, Bracket & Reduce-Only Explained

Why Conditional Orders Matter on Hyperliquid

Perpetual futures trading moves fast. On a high-throughput DEX like Hyperliquid, where block times are under one second, the difference between a manual exit and an automated one can be thousands of dollars. Conditional orders let you define precise entry and exit rules before price reaches them — no staring at charts required.

Hyperliquid supports three primary conditional order types: OCO (One-Cancels-the-Other), bracket orders, and reduce-only orders. Each serves a different purpose, and combining them is how professional traders manage risk on the platform.

Before diving in, make sure you have an account. New users who sign up with referral code HOLYGRAIL get access to the full trading suite immediately — no KYC, no waiting.

Understanding OCO Orders (One-Cancels-the-Other)

An OCO order links two orders together: when one executes, the other is automatically cancelled. This is the bread-and-butter tool for range-bound trading and breakout strategies.

How it works: You place a take-profit limit above current price and a stop-loss below. If price rises and hits your take-profit, the stop-loss cancels. If price drops and triggers your stop, the take-profit cancels. You never risk having both orders fill accidentally.

Practical example: You enter a long position on ETH-PERP at $2,000. You set an OCO with a take-profit limit at $2,100 and a stop-loss at $1,950. Your risk is capped at $50 per ETH, and your reward target is $100. The moment either triggers, the other disappears. No manual intervention needed.

Hyperliquid's OCO implementation is native — not a client-side hack. This means the OCO logic runs on the exchange itself, so it works even if you close your browser or lose connection. For traders using the API, OCO orders are submitted as a single message with both legs specified.

Bracket Orders: TP and SL in One Trade

A bracket order is the simplest conditional setup: you place a market or limit entry order, and attached to it are a take-profit and a stop-loss. Think of it as "enter here, take profit there, stop out there" — all defined before you submit.

Three components of a bracket order:

• Entry order: A limit or market order to open the position
• Take-profit: A limit order to close at a profit target
• Stop-loss: A trigger order to close at a loss limit

The key advantage over placing three separate orders is atomicity. The TP and SL only exist if the entry fills. If your limit entry never triggers, the attached orders never activate. This prevents the classic mistake of having a standalone stop-loss sitting in the order book without the corresponding position.

Hyperliquid-specific note: Bracket orders on Hyperliquid use the same underlying mechanism as OCO but are presented as a single trade entry. On the trading UI, look for the "TP/SL" toggle when placing an order — enabling it exposes the take-profit and stop-loss fields.

Reduce-Only Orders: Protect Your Position Size

Reduce-only is a modifier you attach to any order, not a separate order type. When enabled, the order can only reduce your position — it can never increase it or flip you to the opposite side.

Why this matters: Imagine you have a 10 ETH long position. You place a stop-loss at $1,900. Without reduce-only, if that stop triggers during extreme volatility and your position somehow reverses mid-fill, you could end up with a short position instead of flat. Reduce-only guarantees the order closes your position and nothing more.

On Hyperliquid, the reduce-only checkbox is available on every order form. For API traders, it is a boolean flag in the order payload. Professional traders enable reduce-only on every stop-loss and take-profit they place — it is a zero-cost safety net.

Combining Conditional Orders: A Complete Strategy

Experienced Hyperliquid traders layer multiple conditional orders to build robust trading systems. Here is a real workflow:

Step 1: Place a bracket order to enter long on BTC-PERP at $74,000, with TP at $75,500 and SL at $73,200.
Step 2: Once the position is open, add a trailing stop (set to reduce-only) that follows price upward with a 1.5% trail.
Step 3: Place a separate OCO above the current price: a limit to add to the position at $74,500 if momentum continues, cancelled by a second SL at $73,800.

This layered approach gives you a risk-defined entry, a moving profit-protection mechanism, and a conditional add-on if the trade works in your favor — all automated.

Common Mistakes to Avoid

• Forgetting reduce-only on stop-losses: Always check the box. If your stop-loss fires in a fast-moving market, reduce-only prevents unwanted position flips.
• Setting TP and SL too tight: Hyperliquid's low fees are a double-edged sword. Tight stops get hunted by high-frequency traders. Give your trades breathing room — at least 0.5% on BTC and 1% on altcoins.
• Not accounting for funding rate: If you hold a position through funding payment windows, the funding rate can eat into your bracket's profitability. Check the current funding rate before placing multi-hour bracket orders.
• Overlapping conditional orders: Avoid having two active reduce-only orders that could conflict. If you place a new bracket, cancel any old TP/SL orders first.

API Access for Automated Conditional Trading

Hyperliquid's REST and WebSocket APIs expose every conditional order type programmatically. The exchange uses a typed order system where each order includes an orderType field and optional reduceOnly boolean flag. For OCO submissions, you send an array of two orders with a shared group ID.

Python traders can use the official Hyperliquid SDK, which wraps the order types in clean methods. TypeScript/Node.js users have community-maintained libraries that mirror the same functionality. The key advantage of API-based conditional orders is speed: you can respond to market signals in under 100ms from detection to submission.

Related Reading

• Hyperliquid Stop-Loss Strategies
• Hyperliquid Order Types — Complete Reference
• Hyperliquid API Trading Bot Guide