How to report a futures trade execution error to Binance support?

Reporting Futures Trade Execution Errors

1. Gather complete execution details before contacting support, including the exact timestamp in UTC, the symbol involved, order ID, client order ID, and the precise API endpoint used.

2. Capture raw request and response payloads, ensuring sensitive fields like signature and API key are redacted using asterisks or omitted entirely.

3. Verify whether the error originated from a ClientError (e.g., -1013 for insufficient margin) or ServerError (e.g., 503 service unavailable), as this determines the appropriate escalation path.

4. Confirm that your system clock is synchronized within ±1 second of NTP time servers, since timestamp skew beyond this threshold causes signature validation failures logged as -1022 errors.

5. Check Binance Status Page and official Telegram channels for ongoing incidents affecting USD-M or COIN-M futures infrastructure before submitting a ticket.

Required Evidence for Valid Ticket Submission

1. A screenshot or log excerpt showing the full exception stack trace, with emphasis on the binance.error.ClientError or binance.error.ServerError class name and its attributes.

2. The corresponding entry from your account’s order history page matching the same order ID and execution time, confirming whether the order appears as filled, partially filled, or canceled.

3. WebSocket message dumps containing executionReport events for the affected order, especially if discrepancies exist between REST and real-time feed states.

4. A curl command replicating the exact request — with all headers, query parameters, and body content — formatted for readability and stripped of credentials.

Support Channel Prioritization

1. Enterprise clients must use the dedicated enterprise-support@binance.com address with subject line prefixed by [ENTERPRISE] and include contract reference number.

2. Futures API developers should submit tickets via the Binance Developer Portal, selecting “Futures API” under product category and attaching code snippets demonstrating the integration flow.

3. Non-English speakers may submit in Chinese, Japanese, Korean, or Arabic; English remains the mandatory language for technical payloads and error codes.

4. Avoid social media platforms for error reporting — tweets or Discord messages lack audit trails and cannot trigger internal engineering triage workflows.

Common Missteps That Delay Resolution

1. Submitting tickets without specifying whether the issue occurred on testnet.binancefuture.com or fapi.binance.com, leading to misrouted diagnostics.

2. Omitting the X-MBX-USED-WEIGHT header value from failed requests, which prevents support from verifying rate limit compliance at the time of failure.

3. Reporting “order disappeared” without checking position status via positionRisk endpoint — some orders execute successfully but do not appear in openOrder list due to immediate fill-and-close behavior.

4. Attaching screenshots of browser-based trading interface instead of API logs when the problem occurs exclusively in automated systems.

Frequently Asked Questions

Q: Can I retrieve an order’s execution report if it was placed more than 7 days ago?A: No. The get_order endpoint only returns historical orders up to 7 days old. For older records, use the get_account_trades endpoint with appropriate time filters.

Q: Does Binance provide timestamps in nanosecond precision for trade executions?A: No. All timestamps returned by futures APIs are in millisecond precision and aligned to UTC. Nanosecond-level logging exists internally but is not exposed externally.

Q: What does error code -2014 mean when calling new_order?A: This indicates an invalid API key. It occurs when the key has been deleted, disabled, or lacks required permissions for futures trading — even if it works for spot endpoints.

Q: Is there a way to confirm whether my order matched against the book or triggered a liquidation event?A: Yes. Cross-reference the tradeId from your execution report with entries in the userUniversalTransfer or income endpoints to identify funding fee settlements or insurance fund payouts associated with forced closures.