Platform
XML Feed
Definition
A data integration format used historically across iGaming B2B integrations, particularly for sports data and odds. Largely supplanted by JSON-based APIs but still present in legacy integrations.
Why it matters
XML feeds have been the workhorse data integration format in iGaming for two decades. Sports data, odds, settlement information, and other structured data has historically flowed between systems as XML feeds, often pulled on schedule or pushed on event triggers. The format's strengths (schema validation, broad tooling support, human-readable) made it the default for B2B integration during the formative years of online gambling.
JSON has largely replaced XML for new integrations because of lower payload size, simpler parsing in modern languages, and better fit with web technology stacks. Modern data feeds tend to be JSON-based REST APIs or websocket streams. XML persists in legacy integrations where the cost of migration outweighs the benefits, and in some specific contexts where XML schema validation is operationally valuable. Operators with long-running integrations typically maintain both XML and JSON capabilities to interface with the spectrum of supplier formats.
Frequently asked questions
Are XML feeds being phased out?
Gradually. New integrations almost always use JSON-based APIs or websocket streams. Legacy XML integrations persist where migration cost doesn't justify replacement. The trend over time is toward complete migration away from XML, but the timeline is long.
Why does the format choice matter?
Mainly engineering efficiency. JSON is more compact, parses faster in modern web stacks, and integrates more naturally with cloud-native architectures. XML is more verbose and requires heavier parsing. For high-volume real-time feeds, the format difference can be operationally significant.