Data normalization
Align symbol names, timestamp handling, precision and trading sessions.
05 / DATA
Market Data & Price Feeds
Bring price feeds into a consistent format for your trading platform and connected services.
Configuration scope
MARKET_DATA.SRVA connected feed is useful when its instruments, timestamps and precision match the consuming system. TGS Trade scopes normalization, source selection and distribution so operators can track the price path from source to platform.
Source rules
Define source selection or aggregation and the expected consumer interfaces.
Feed health
Check update freshness, missing prices and recovery after a source interruption.
Specify what each consumer needs
List the trading platforms, bridges and internal services that will receive prices. Record their symbol definitions, precision and delivery expectations. A consistent normalization layer helps consumers interpret the same instrument data, while the distribution plan identifies where an unavailable or slow consumer should be isolated.
Measure freshness in the context of the instrument
A quiet instrument and a stalled feed are different operational states. Agree how timestamps, market sessions and expected update behaviour inform feed-health checks. Record the source-selection or aggregation rules so changes can be reviewed against a known pricing baseline. Acceptance should follow the data through to the consuming system.
Acceptance evidence
VERIFY.SYSAgree the test examples and expected results before implementation. The final plan follows the selected systems and interfaces.
| Check | Expected evidence |
|---|---|
| Normalized fields | Sample symbols, precision and timestamps match the agreed internal definitions. |
| Consumer delivery | Each required consumer receives the expected instrument stream. |
| Source interruption | The agreed stale-feed or failover behaviour can be observed in a test. |
| Health visibility | Operators can distinguish a source problem from a downstream delivery problem. |
Technical distribution does not supply market-data rights. Source licenses and permitted consumers must be identified as part of the project requirements.
Service questions
README.TXTCan several systems use one feed?
A distribution layer can serve the platform and other consumers, with the interfaces and capacity agreed during scoping.
Are market-data rights included?
Data licensing depends on the selected sources and permitted uses. These arrangements are identified separately from technical integration.
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 TOPICMarket Data & Price Feeds
Message on Telegram@whitelabelmetatraderfx[ New tab ]Message on WhatsApp+358 82 371 1153[ New tab ]Choose a messenger to discuss your project.