Route approved pricing to each consumer with clear entitlements, capacity limits and isolation between delivery paths.
Trading servers, charts and risk systems can require different fields or update rates. Define each consumer's allowed instrument set and delivery contract; a downstream subscriber should not receive a broader universe simply because it shares a connection.
A slow chart client should not stall a risk stream. Plan queue limits, conflation and disconnect behavior per path, and measure delivery lag at the receiving application as well as at the distributor.
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
| Input identity | Record approved sources, instrument definitions and symbol mappings. |
|---|---|
| Selection policy | Agree primary/backup, aggregation or distribution rules for each relevant consumer. |
| Health signals | Define freshness, source status, outlier handling and recovery thresholds. |
| Operational evidence | Retain policy versions, source changes and the reason for fallback or rejection. |
A production workflow for your instrument universe needs explicit rules for admitting, selecting and excluding inputs. Normalize definitions before comparing prices. A source that remains connected can still be stale for an individual instrument; expose that distinction in operations.