ON THIS PAGE
Connect the selected liquidity counterparties
Liquidity connectivity is the work of integrating a broker environment with chosen external pricing or execution endpoints. It does not by itself establish a liquidity agreement. Start with the counterparties and their supported interfaces, then document whether the connection delivers prices, accepts orders or performs both roles.
Build an endpoint inventory
For each endpoint, record the environment, session identifiers, transport requirements, supported instruments and operational contact. Identify test and production endpoints separately. Confirm how credentials are issued, how network access is authorised and which party approves a connection for production use.
Map instruments and order behaviour
Compare instrument names, quantity conventions, decimal precision, trading sessions and permitted order workflows. A matching symbol name does not guarantee matching contract specifications. Differences should be resolved in a controlled mapping rather than silently normalised by individual applications.
Test exceptions as well as successful trades
Acceptance should include rejected orders, unavailable sessions, stale data, reconnects and duplicate or delayed reports where applicable. Preserve correlation identifiers between the broker system and the external endpoint. A connection is operationally useful when teams can trace what happened and determine which party owns an exception.
Separate connectivity from routing policy
Connecting an endpoint does not decide which orders should reach it. Routing rules, exposure controls and fallback behaviour are a separate part of the design. Use the liquidity bridge and routing services when several destinations or conditional execution policies must be coordinated.