B2CONNECT October Update: Connecting Multiple Liquidity Aggregator Instances and Adaptive FIX Sessions

B2CONNECT’s October updates introduce multiple connections to the same liquidity aggregator, along with per-taker FIX specifications, clearer order rejection reasons, and improvements to order handling and recovery.

For brokers, this means individual liquidity aggregator instances can connect through one B2CONNECT instance, while a single FIX server can accommodate takers with different specifications. Here’s how the update supports these workflows.

Connect Multi-instance Liquidity Aggregators Through B2CONNECT Hub

B2CONNECT hubs have always supported multiple maker connectors, and now, we’ve taken it a step further by removing the one-per-type limit. This way, brokers can run duplicate connections to the same liquidity aggregator simultaneously on a single hub.

Every connection remains fully autonomous, retaining its own dedicated trading and quoting sessions, and mapping symbols and orders to that specific instance.

Add and Configure Each Connection

Each liquidity aggregator instance is added as its own connector. Give the connector a name, select its adapter, and configure it as a distinct connection. The Incoming Connectors list keeps the connections visible together within the same hub.

Adapt FIX Sessions to Each Taker

Each taker’s FIX credentials can now carry their own FIX specification. A single hub endpoint can therefore serve takers whose platforms expect different specifications.

Rejected orders provide clearer account-related reasons, such as insufficient funds or an account not found, instead of a generic internal error. If a taker’s credentials are deleted during an active session, the taker receives a Logout message before the connection closes.

Improve Order Handling After Inactivity and Rate Limits

The first order after a quiet period now reaches the venue with less delay, reducing the wait when trading resumes after inactivity.

When a venue imposes a rate limit, orders now wait for available capacity within their time-to-live, reducing delays associated with the hub’s previous fixed retry schedule.

Additional Connectivity & Configuration Fixes

The update addresses stale order books and funding data on a futures venue, as well as lost order-placement confirmations when supported crypto-maker connections stop mid-order. It also improves connection shutdown during reconnection.

Older taker credentials can again be opened and edited, and their passwords can be changed in the Web UI. Symbol configuration uploads with Depth 0 are rejected instead of clearing the order book.