SODA: Sports On Demand API >> Technical Details
Learn More

SODA is built atop open standards and open protocols. Its technical objective is to make our content as easy as possible to integrate into websites, applications, databases and editorial systems:

Photos, it should be noted, are currently only available via a manual downloading process. Clients interested in a hands-free photo feed should contact XML Team sales.

Supported Formats

Our platform supports multiple formats for the free listings and for the documents themselves. The most common combination is RSS for listings, and SportsML for documents.

RSS, commonly known as "Rich Site Syndication" or "Really Simple Syndication," is employed by millions of users worldwide. It comes in many flavors, several of which we support. We recommend RSS 1.0. If you're new to RSS, then here are some technical resources:

SportsML is the open XML vocabulary for sports data, and is the only international standard designed for scores, standings, schedules, and statistics designed to accommodate every sport, country and language. For more information on SportsML, visit our Why XML? page or

Formats We Support
For Listings For Data
RSS 1.0
RSS 0.92
RSS 2.0
(cleanly formatted
and permeated with
CSS properties)

How to Request Listings

Listings are requested by making a standard, authenticated http request. You can manually request listings by just typing the appropriate URL into a web browser. Use our Query Builder tool to determine the parameters within the URL, or read our API Specification for details. Broken down and documented for clarity, one sample URL for Listings might look like this:

league-keys = &
// Metadata code for the NHL

fixture-keys = event-stats &
// Metadata code for a Box Score

max-result-count = 10 &
// List only the most recent 10

date-window = 24:00 &
// List content published in past 24 hours

stylesheet = sportsml-set2rss-1.0
// Display Listings in RSS 1.0 format

SODA uses standard http authentication. When using a web browser to display Listings, this means that a small popup window appears asking for your username and password. Login information can also be included in the URL itself, as in: Please note that Microsoft's Internet Explorer has dropped support for this type of URL. Microsoft cites security issues, and current updates of Internet Explorer no longer support adding the "username:password@" string to the start of a URL. See Microsoft's support page on this issue for more details.

How to Request Documents

Depending upon which format you've chosen for the Listings, you'll be able to determine what URL to use to retrieve the actual documents themselves.

If you've selected RSS, then the final-form URLs for the various documents are included in the <link> elements. Broken down and documented for clarity, one sample URL for Document might look like this:

// The Document ID of a file.

Other parts of the RSS Listing give you the title of the document, its publication date, and other useful pieces of metadata.

Like with the Listings URL, document retrieval uses standard http authentication.

Key Practices When Automating Listing Requests and Doc Retrieval

XML Team currently does not provide software for querying the webservice, but the mechanics are not difficult for an experienced programmer. Here are some key requirements for any such software: