ID Handling

This guide explains how identifiers work in the Sportradar Golf API: which IDs are primary, how they relate across feeds, and how Golf IDs connect to other Sportradar products. Getting the ID model right is the foundation of a stable integration.

UUIDs Are the Primary Identifiers

Golf feeds identify every entity with a UUID: tours, seasons, tournaments, rounds, players, venues, courses, pairings, teams, and brackets. These UUIDs are consistent across Golf API feeds and are the values you should store and reuse as primary keys.

{
  "tour_id": "b52068af-28e4-4e91-bdbb-037591b0ff84",
  "season_id": "55827590-93f7-4493-9b4f-83ae86116ef6",
  "tournament_id": "459e9ffb-1eb4-422c-9f13-1ba8344c35aa",
  "round_id": "0e387540-a829-4258-b082-53ff9d3b351d",
  "player_id": "6db3e736-d86d-4181-aa3b-651b8c1bfdc1",
  "venue_id": "d555598a-aed0-44fe-b659-4250264c7820",
  "course_id": "7e9462a5-66ea-4205-b37a-81884e3653cf"
}

🆔
SR_IDs in the Golf API
In the REST feeds, UUIDs are the primary identifiers, and Sportradar IDs (SR_IDs) do not appear in REST responses at all: you navigate REST data entirely by UUID.
SR_IDs surface in two other places. Push payloads include sr_id values on tournament, player, and metadata objects (in the form sr:stage:721700 or sr:competitor:46702), and SR_IDs are the join key for cross-product correlation (for example the Images and Editorials APIs or other-sport data).
A common case: the stage IDs that the US widgets need are SR_IDs (sr:stage:...) and are not exposed in the Golf REST feeds. Obtain them through the Mapping API rather than expecting them in a tournament or schedule response.
So the rule is: use UUIDs as primary keys for REST data, and bring in SR_IDs only when you consume Push, drive widgets, or cross-reference other Sportradar products. See Push for where SR_IDs appear in payloads.

Where Each ID Family LivesUUIDs inside the Golf REST feeds; SR_IDs beyond them

UUIDGolf API REST feeds

Every entity is identified by a UUID: tours, seasons, tournaments, players, venues, courses, rounds, pairings, teams, and brackets. Store these as your primary keys.

459e9ffb-1eb4-422c-9f13-1ba8344c35aa

SR_IDPush and the wider Sportradar catalog

SR_IDs appear in Push payloads and are the join key for cross-product work: Images and Editorials, other-sport data, and the widget stage IDs served by the Mapping API. REST responses navigate by UUID alone.

sr:stage:721700sr:competitor:46702

The bridgetournament_uuid,sr:stage:721700Push metadata carries both families comma-separated; split on the comma to recover the UUID you already store and the SR_ID for cross-product joins.

ID Types

Each ID below is a UUID unless noted.

Tour ID: the circuit (for example the PGA Tour). In URLs you use the lowercase tour alias (pga), not the tour UUID.
Season ID: one year of a tour.
Tournament ID (tournament.id): a single event in a season. Use this for all tournament-scoped feed requests and for season-specific storage.
Player ID: a player, stable across seasons and tours.
Venue ID and Course ID: the site and the specific course layout.
Round ID: one round of a tournament.
Pairing ID: a tee-time grouping.
Match ID and Team ID: used in match and team/cup events (see Monitoring Team Events).

Parent Tournament IDs

parent_id is a distinct and easily missed ID type. It links the recurring editions of the same event across seasons, so it powers franchise-style history (every Masters, every Players Championship) independent of the per-season tournament.id.

{
  "id": "459e9ffb-1eb4-422c-9f13-1ba8344c35aa",
  "name": "Masters Tournament",
  "parent_id": "5c8d8f92-8da7-4d5d-860b-e820d57ff640"
}

Use tournament.id for feed requests and season-specific records, and parent_id for cross-season grouping and "tournament history" views.

Bracket IDs

Bracket identifiers surface in two feeds:

brackets.bracket in Tournament Summary defines the bracket groupings for an event.
match.bracket in Tee Times Per Round tags each match with the bracket it belongs to.

The two carry the same identifier. In the 2024 T-Mobile Match Play (LPGA), the Made Cut bracket returns one id in the Tournament Summary brackets array (alongside its eight-player roster) and the same id on every match.bracket in Tee Times Per Round. Read the groupings from Tournament Summary, then correlate each match's match.bracket against them.

IDs in Other Sportradar Products

Golf UUIDs and SR_IDs are the bridge to the rest of the Sportradar catalog:

Images and Editorials: reference golf entities using the same UUID-based identifiers (and SR_IDs where applicable), so you can attach player photos and editorial content to tournaments and players.
Widgets: render golf data keyed off the same IDs.

Best Practices

Store and reuse UUIDs as primary keys for all REST data.
Use the lowercase tour alias in URLs, not the tour UUID.
Keep tournament.id for season-specific data and parent_id for cross-season history.
If you consume Push or cross-reference other Sportradar products, store the sr_id alongside the UUID so you can correlate later.
In bracket events, read bracket groupings from Tournament Summary and match each match.bracket from Tee Times Per Round against them.