Separate fixtures, scores, prices, market status and settlement data. Establish which source is authoritative for each decision.
Make coverage figures comparable
| Comparison field | Why it matters |
|---|---|
| Object counted | One fixture can contain many priced markets and selections |
| Pre-match or live | The same headline total may describe different parts of the book |
| Observation period | Monthly and annual totals need a common basis |
| Priority competitions | Broad coverage may omit the events your audience needs |
| Data and media rights | Access to odds does not automatically include every use or stream |
Use the actual launch catalog to compare offers. Request the relevant coverage and conditions for your operator rather than extrapolating from a supplier-wide number.
Define update and recovery behavior
Specify event and market identifiers, update ordering, timestamps and what happens after a connection gap. Establish how the receiving system obtains the current state and distinguishes it from an older update.
A secondary feed needs compatible mapping and an agreed handoff process. Define which markets can switch, which suspend and how existing positions will settle. A second data connection is not proof that a whole book can fail over safely.
Replay an event with exceptions
Test delayed prices, an out-of-order update, reconnect and a corrected result. Inspect the market state, acceptance decision and settlement record. Measure the behavior under the agreed conditions instead of borrowing a latency claim from a different environment.
Assign the investigation boundary between feed supplier, platform and trading operations. The team needs to know who can suspend a market and how it is reopened after unreliable data.
Compare the complete commitment
Include permitted use, coverage, minimum charges, term, termination and support. Distinguish raw data from managed services and identify any dependencies for cash-out, bet builder or other products.
Send your priority competitions and trading hours, current feed and required events. Include the recovery problem you need to solve so the integration can be demonstrated against it.