How to Check Whether a MEXC Futures Order Was Executed at the Trigger Price?

Understanding Trigger Price Execution in MEXC Futures

1. MEXC Futures supports conditional orders including stop-market, stop-limit, and trailing-stop types, all of which rely on a user-defined trigger price to activate the order submission logic.

2. The trigger price is not the execution price — it serves only as the activation threshold for the underlying order. Once triggered, the actual fill depends on market liquidity and order type parameters.

3. For stop-market orders, execution occurs at the best available market price immediately after triggering, which may differ significantly from the trigger price during volatile conditions.

4. Stop-limit orders require both the trigger condition and a separate limit price; execution only happens if the market reaches or crosses that limit price after triggering.

5. Trailing-stop orders dynamically adjust the trigger level based on price movement but still follow the same separation between trigger and fill mechanics.

Locating Order Execution Details in MEXC Interface

1. Log into your MEXC account and navigate to Futures → Order History → Conditional Orders tab.

2. Identify the relevant order by its creation timestamp, symbol, and order ID. Each entry displays Trigger Price, Status, and Order Type.

3. Click the order row or the “Details” icon to expand full metadata, including Trigger Time, Activation Time, and Actual Fill Price if executed.

4. If the order was filled, the interface shows Fill Price, Fill Quantity, and Execution Time — all distinct from trigger-related fields.

5. Unfilled conditional orders show Pending status with no fill data, while partially filled ones list cumulative execution metrics alongside remaining quantity.

Analyzing Order Logs via MEXC API

1. Use the /fapi/v1/userTrades endpoint with appropriate symbol and startTime filters to retrieve trade records associated with your conditional order ID.

2. Cross-reference the orderId field in trade responses with the origClientOrderId or clientOrderId used when placing the conditional order.

3. Each trade object contains price, qty, time, and isBuyerMaker — these represent real-time execution data, not trigger values.

4. Compare the earliest trade timestamp with the triggerTime from the /fapi/v1/positionRisk or /fapi/v1/allOrders response to assess time lag between trigger and first fill.

5. Aggregate multiple trades under one conditional order ID to verify whether fills occurred at or near the declared trigger price, especially under low-slippage market conditions.

Common Misinterpretations of Trigger Behavior

1. Assuming the trigger price equals the fill price leads to incorrect PnL calculations — slippage is inherent in stop-market execution and must be accounted for separately.

2. Confusing activation time with execution time causes timing errors when backtesting strategies or reconciling ledger entries.

3. Overlooking the distinction between order placement time and trigger time results in misaligned event sequencing across dashboards or alert systems.

4. Interpreting partial fills as full execution skews position sizing assumptions — each fill must be evaluated individually against its corresponding price and quantity.

5. Relying solely on UI status indicators without verifying raw trade logs increases exposure to interface rendering delays or caching inconsistencies.

Frequently Asked Questions

Q: Does MEXC display the exact moment a conditional order transitions from pending to activated?A: Yes. The Activation Time field appears in the expanded order details view and matches the activateTime value returned by the /fapi/v1/allOrders API endpoint.

Q: Can I retrieve historical trigger events for orders placed more than 90 days ago?A: No. MEXC retains conditional order history for up to 90 days. Older records are purged automatically and cannot be recovered through standard API or web interface methods.

Q: Why does my stop-market order show a fill price far from the trigger price even during moderate volatility?A: Stop-market orders convert to market orders upon trigger, and their execution depends entirely on the current order book depth. Gaps in bid-ask spread or rapid price acceleration cause immediate fills at less favorable levels.

Q: Is there a way to confirm whether a conditional order failed to trigger due to price not reaching the threshold?A: Yes. Check the Status column in Conditional Orders — entries marked Expired or Canceled without any associated trades indicate non-triggering. The cancelReason field in API responses provides further context.