Instrument mapping
Align platform symbols, precision and contract definitions with provider instruments.
02 / CONNECTIVITY
Liquidity Bridge
Connect your platform to liquidity sources with explicit price flows, order routes and recovery behaviour.
Configuration scope
LIQUIDITY_BRIDGE.SRVA bridge connects the platform and execution endpoints. The design must cover both arriving prices and outgoing orders. TGS Trade maps these paths separately, then aligns instruments and execution events across the connected systems.
Execution connections
Configure endpoints and order routes with visible rejection handling.
Recovery checks
Test lost connections, stale feeds and the agreed fallback procedures.
Make the price path and order path traceable
Describe where an instrument price originates and how an order reaches its destination. These paths need separate checks: a source can stop producing updates while a connection remains open, and an order can be rejected while prices continue normally. The bridge scope should make both states visible to the operations team.
Agree the behaviour of exceptional orders
Collect the provider’s supported workflows before choosing route rules. Identify how acknowledgement, execution and rejection events are matched to platform requests. For uncertain order state, define an investigation and recovery procedure before enabling any resend behaviour. The acceptance plan follows the interfaces actually selected for the project.
Acceptance evidence
VERIFY.SYSAgree the test examples and expected results before implementation. The final plan follows the selected systems and interfaces.
| Check | Expected evidence |
|---|---|
| Instrument alignment | Sample prices and orders use the agreed symbol and contract mapping. |
| Route selection | Operators can identify the destination and the rule used for a test order. |
| Unavailable endpoint | The test records how requests and session state behave during a disconnection. |
| Operational diagnosis | Logs provide the identifiers needed to investigate a rejected or incomplete order. |
The bridge project covers technical connectivity. Liquidity agreements, available instruments and execution conditions are agreed with the selected providers.
Service questions
README.TXTWhy does symbol mapping matter?
Different instrument names and specifications can create inconsistencies between quoted prices and accepted orders. Mapping aligns these definitions.
What is covered by monitoring?
The agreed scope can include session health, feed freshness, order events, rejection reasons and reconnect behaviour.
Connected modules
RELATED.DIRC:\TGS\CONTACT
DIRECT CONNECTIONDISCUSS YOUR PROJECT
Connect your broker stack.
Tell us which platform you use, which connections you need and what is already in place. We will scope the modules and integration work around your requirements.
Your messenger opens with a draft. Review it and send when ready.
PROJECT TOPICLiquidity Bridge
Message on Telegram@whitelabelmetatraderfx[ New tab ]Message on WhatsApp+358 82 371 1153[ New tab ]Choose a messenger to discuss your project.