The Python FIX connector provides access to Binance Financial Information eXchange (FIX) APIs using the FIX protocol.
This connector is intended for advanced and institutional use cases that require low-latency order entry, execution, and session-based trading workflows. It exposes Binance Spot FIX message types and session flows and allows you to place orders, cancel orders, and track order status using FIX messages.
For source code, issues, and release notes, see the binance-fix-connector-python repository on GitHub.
Supported environments
- Python 3.9 or newer
- Backend services and trading systems
This connector is intended for server-side usage only and requires a persistent FIX session.
Scope and capabilities
The FIX Python connector supports:
- Binance Spot FIX Order Entry
- Order placement and cancellation
- Execution reports and order state updates
- Session-based FIX communication
This connector does not replace REST or WebSocket APIs and is designed for specialized trading workflows.
Authentication
⚠️ Important
Binance FIX APIs only support Ed25519 keys. Other authentication methods (such as HMAC or RSA) are not supported.
Before using the FIX connector, ensure that:
- You have generated an
Ed25519key pair - Your API key has FIX permissions enabled
- You are using the correct FIX endpoint for production or testnet
Refer to the following guides:
Installation
Install the connector using pip:
Code
The package is published on PyPI as
binance-fix-connector. Source code is maintained in the GitHub repository linked above.
Getting started
All FIX messages are created and managed through the create_order_entry_session helper, which
establishes a FIX session and exposes utilities to create and send messages.
The example below demonstrates how to establish a FIX Order Entry session and submit a simple limit order.
Code
Refer to the repository documentation for more examples.
Typical use cases
- Low-latency order entry and execution
- Institutional or professional trading systems
- FIX-based integrations requiring session control
- Advanced trading infrastructure where REST or WebSocket APIs are not sufficient
Notes and best practices
- FIX APIs require a persistent TCP/TLS connection
- Always handle session lifecycle events (logon, heartbeat, logout)
- Use testnet endpoints for development and validation
- Consider implementing reconnect/backoff logic and monitoring session health
- This connector is intended for experienced FIX users
- For general-purpose integrations, prefer REST or WebSocket APIs