ID Handling

The Probabilities API identifies everything with Sportradar URNs (sr: IDs). This page covers the families you will store, how the same IDs work across the Odds Comparison packages, and how the uuids field bridges to the League Specific APIs.

The Identifier Scheme

Every entity carries a typed URN. The families, with values from one MLB event's payload:

Family	Example	Identifies
`sr:sport:`	`sr:sport:3` (Baseball)	A sport
`sr:category:`	`sr:category:16` (USA)	A country or region within a sport
`sr:competition:`	`sr:competition:109` (MLB)	A competition
`sr:season:`	`sr:season:134469` (MLB 2026)	One season of a competition
`sr:sport_event:`	`sr:sport_event:63301085`	One game or match
`sr:competitor:`	`sr:competitor:3627` (Chicago Cubs)	A team
`sr:league:`	`sr:league:99741`	A grouping within a season, such as a division
`sr:venue:`	`sr:venue:8069` (Wrigley Field)	A venue

IDs arrive in context: each event payload's sport_event_context carries the sport, category, competition, season, and groups the event belongs to, so one response supplies every key needed to join it to season-scope data.

One ID Across the Odds APIs

The Probabilities API shares its identifier scheme with the Odds Comparison packages: the same sr:sport_event: ID resolves in Prematch, Player Props, and here, and the same holds for competition and season IDs. One discovery pass can therefore drive odds boards and probability displays together:

GET https://api.sportradar.com/probabilities/trial/v1/en/sport_events/sr:sport_event:63301085/probabilities.json
x-api-key: YOUR_API_KEY

The same event ID in a Prematch or Player Props URL returns that event's markets in those packages.

Linking to the League Specific APIs

Each competition record in the Sport Competitions feed carries a comma-separated uuids field: the competition's GUIDs in the League Specific API family:

{
  "id": "sr:competition:109",
  "name": "MLB",
  "gender": "men",
  "uuids": "2ea6efe7-2e21-4f29-80a2-0a24ad1f5f85,2fa448bc-fc17-4d3d-be03-e60e080fdc26,fbe91704-36df-4e7c-864a-06d236425999",
  "current_season_id": "sr:season:134469",
  "live_coverage": true
}

These are the same GUIDs the Odds Comparison mappings feeds return, so either surface joins probabilities to schedules, stats, and player data in the League Specific APIs. The full join workflow, including entity-level mappings, is on the Odds Comparison guide's ID Handling page.

Storage Guidance

Store URNs whole (sr:sport_event:63301085), not the numeric tail; the prefix disambiguates entity types
Key events by sr:sport_event: and carry the sport_event_context IDs as foreign keys to season and competition scope
Persist uuids and current_season_id from Sport Competitions at discovery time; they are the bridges to the League Specific APIs and the seasonal feeds
Resolve outcome names (home_team_winner) to teams through competitors[].qualifier, not by string-matching team names