What it is
The same XML envelope contract as the rest of the platform, served over the football hierarchy. One sport per feed instance (Soccer, id1); every body is wrapped in its envelope so an XML-only client never has to parse JSON.
All paths are locale-scoped (en | ru) and authenticate with X-API-Key.
Endpoints
Shape notes
- Competitors carry the home/away
qualifierand anid— resolve name/logo via/competitors/{id}/profile. - Tournament travels as a nested
<tournament id=…>with its<sport>(the country/category) — never a flat attribute. <extra_info>carriessport_formaton both fixture and summary.- Not-found is the in-body marker on the matching envelope with HTTP
404— not a JSON{detail}body.
The match-status dictionary (
/descriptions/{locale}/match_status) enumerates exactly the codes the football feed publishes. Build your status map from it — see Match status & lifecycle.