get
https://api.sportradar.com///v2//players/merge_mappings.
Global Baseball Player Merge Mappings provides valid ids for players who have had their profiles merged. While Sportradar always strives to provide one unique player id, it is a possibility for two ids to be created. This feed provides the correct id once profiles have been merged.
Entries are retained in this endpoint for one week.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Update FrequencyTTL / Cache: 5 minutes
Data Updates: Occasional; merges only when duplicates are resolved
Recommended polling cadences for every feed are on the Update Frequencies chart of the Global Baseball Integration Guide.
Resolving IDs Across ProductsLearn how to use the Player Merge Mappings feed to find player IDs that were merged into another record in our ID Handling integration scenario.
Data Points
Mapping
| Attribute | Parent Element | Type | Description |
|---|---|---|---|
merged_id | mapping | String | Player ID for a merged profile. This ID will be removed from the API database. ex. sr:player:2650847 |
name | mapping | String | Player name of a merged profile ex. Viernes, Jeff |
retained_id | mapping | String | Player ID for a retained profile ex. sr:player:2613623 |