Session specification
Agree endpoints, identifiers, heartbeat settings and sequence policies.
03 / CONNECTIVITY
FIX API Integration
Connect trading systems through FIX with agreed session settings, message mapping and recovery rules.
Configuration scope
FIX_API.SRVA FIX integration starts with the counterparty specification. Market data and order handling may use different message flows. TGS Trade defines the required sessions and fields before building and testing the connection.
Message mapping
Map supported messages, instrument identifiers and order events between systems.
Acceptance testing
Check valid messages, rejects, reconnects and sequence recovery.
Start with the counterparty’s actual interface
Request the test and production specifications before committing to message coverage. Record the FIX version, session identifiers, supported workflows and any provider-specific requirements. Treat market-data subscriptions and order routing as separate parts of the scope when both are required. A working connection alone does not demonstrate that the application workflows are correct.
Make recovery part of acceptance
A connection needs a shared policy for session transitions and message sequencing. Agree how each side should behave after a gap or interruption, and retain the order identifiers needed for reconciliation. The project test plan should show the expected outcomes for the supported order states, rather than relying only on successful submissions.
Acceptance evidence
VERIFY.SYSAgree the test examples and expected results before implementation. The final plan follows the selected systems and interfaces.
| Check | Expected evidence |
|---|---|
| Session setup | Test credentials and agreed identifiers produce the expected session state. |
| Message coverage | Required messages and fields are checked against the provider specification. |
| Order identity | Requests and responses remain traceable across the supported order lifecycle. |
| Recovery policy | The agreed reconnect and sequence-recovery scenarios have recorded results. |
Supported FIX versions, messages and certification requirements depend on the counterparty. The final specification defines the connection that will be delivered.
Service questions
README.TXTAre all FIX interfaces interchangeable?
Counterparties can require different fields, workflows and session settings. The integration follows the selected provider’s specification.
What happens after a disconnect?
Recovery follows the agreed sequence and session policy. Reconnect and resend scenarios are included in the test scope.
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 TOPICFIX API Integration
Message on Telegram@whitelabelmetatraderfx[ New tab ]Message on WhatsApp+358 82 371 1153[ New tab ]Choose a messenger to discuss your project.