How to cancel an order on Bybit? A quick guide.

Accessing the Order Management Interface

1. Log in to your Bybit account using verified credentials and two-factor authentication.

2. Navigate to the trading interface corresponding to the asset pair where the order was placed—this could be Spot, Futures, or Options.

3. Locate the Active Orders tab, typically positioned on the right-hand side of the trading panel or within the “Orders” section of the account dashboard.

4. Confirm that the order status displays as Open, indicating it has not been filled or partially executed.

5. Identify the specific order by checking its order ID, price level, quantity, and time stamp to avoid accidental cancellation of another active instruction.

Initiating the Cancellation Process

1. Click the Cancel button adjacent to the target order entry—this appears as a red “×” icon or labeled text depending on the platform version.

2. A confirmation modal may appear prompting for explicit user consent; this step prevents unintended cancellations during rapid market movements.

3. Some order types, such as Stop-Limit or Trailing Stop orders, require verification that associated triggers are also being removed from the system’s pending queue.

4. After clicking “Confirm”, the interface refreshes automatically, and the order disappears from the Active Orders list within one to three seconds.

5. The system logs the cancellation event in the Order History section with a timestamp and status change marked as “Cancelled”.

Handling Partially Filled Orders

1. If an order has already executed partially, the remaining unfilled portion remains visible in the Active Orders table with updated quantity values.

2. Cancelling at this stage only removes the residual amount—not the executed trades, which are irreversible and reflected in your position or balance immediately.

3. For linear perpetual futures, partial fills affect open interest and margin usage; cancellation does not reverse those adjustments.

4. Users should cross-check their wallet balance and position summary after cancellation to verify no unexpected changes occurred due to slippage or fee deductions.

5. The cancelled portion generates a separate record in Order History with the label Partially Cancelled, distinguishing it from fully open or fully executed entries.

Using API or Mobile App for Cancellation

1. API users can submit a DELETE request to the /private/order/cancel endpoint with valid API key, signature, and order ID parameters.

2. Mobile app users must tap the three-dot menu next to the order row and select “Cancel Order” from the contextual options.

3. Both methods enforce the same rate limits: up to 100 cancellation requests per minute for standard accounts, reduced to 50 for sub-accounts under shared API keys.

4. Network latency may cause brief visual inconsistencies—orders may persist in the UI for up to five seconds post-cancellation before syncing across all devices.

5. Failed cancellation attempts return HTTP status code 400 with error messages like “OrderNotFound” or “OrderAlreadyFilled”, requiring manual verification before retrying.

Frequently Asked Questions

Q: Can I cancel a market order after submission?A: No. Market orders execute instantly upon submission. They do not appear in the Active Orders list and therefore cannot be cancelled.

Q: What happens if I cancel an order during high volatility?A: Cancellation requests are processed in sequence by the matching engine. During extreme latency, the order might fill before the cancellation reaches the system, resulting in an unexpected trade.

Q: Does cancelling an order incur any fees?A: Bybit does not charge fees for order cancellation. However, repeated cancellations may trigger internal monitoring flags if patterns suggest quote stuffing or manipulative behavior.

Q: Why is the Cancel button greyed out for some orders?A: This occurs when the order is in “Pending” status (e.g., awaiting risk engine approval), has already been filled, or belongs to a restricted contract type such as certain inverse perpetuals under maintenance mode.