Record the underlying index family, source identifier, calculation variant and instrument type. A consumer should be able to determine whether it sees an index value, a futures quote or a broker CFD without guessing from a short symbol.
Different calendars
Plan session and holiday metadata per market. Do not forward-fill one index indiscriminately when another is open; expose closed status and observation age so applications can interpret cross-market screens correctly.
Requirements to confirm
Index family and series metadata
Reference and derivative mapping
Per-market calendars
Closed-market display behavior
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.
Integration brief
Stock Index Price Feed: what to agree before connecting
Instrument scope
Identify the exact underlying, source identifier, quote currency and intended use.
Consumer workflow
List trading platforms, charts, risk tools and applications that need the output.
Delivery contract
Agree protocol, quote fields, timestamps, source status and recovery behaviour.
Production review
Confirm source rights, integration ownership, test evidence and commercial scope.
Begin with a consumer and instrument inventory
For index instruments, define who consumes the prices and what each system needs to reconstruct a usable quote. An application dashboard, broker platform and historical process can require different delivery rules even when they share one normalized instrument model.
What to test
Compare instrument definitions before combining or substituting sources.
Exercise disconnects and confirm the status presented to each consumer.
Review results with the source, adapter and consuming application owners.