Overview

The Mapping API resolves identifiers across Sportradar's ID systems. Give it a Sportradar URN (an sr: ID) and it returns that entity's IDs in other systems: Sportradar UUIDs and select external provider IDs. It exists so you can join data across products with a targeted, entity-level lookup instead of downloading and filtering bulk mapping catalogs.

The API answers questions like:

• What is this sport event's UUID in the League Specific APIs?
• What are the external IDs for every player in this season?
• Which seasons does this competition map to, and under which IDs?

How It Differs from the Mappings Feeds

The Odds Comparison packages each carry bulk /mappings feeds: full catalogs, paginated at 1000 rows, best fetched daily and cached (see ID Handling). The Mapping API is the complement: query-scoped lookups by sport, competition, season, or sport event, returning only that entity's mappings with server-side filtering. Use the bulk feeds to seed a warehouse; use the Mapping API to resolve entities on demand.

Two Rules That Shape Every Integration

• Forward lookup only. Lookups run from Sportradar URN to external ID. There is no reverse endpoint, so if you need to resolve external IDs back to URNs, store the forward results in your own lookup table as you retrieve them.
• Providers are configured per key. Responses contain mappings only for the providers configured for your API key; with no providers configured, the feeds return well-formed, empty lists. Contact Sportradar to configure the mapping providers your integration needs.

How the Guides Are Organized

The map below shows the two tiers; each pill links to its guide.

A 60-Second Look at the Data

A lookup takes the URN in the path and returns the entity with its mappings. This response is from a key with no mapping providers configured yet, so the mappings list is absent; each mapping row carries a provider ID and the entity's ID in that provider's system once providers are enabled:

GET https://api.sportradar.com/mapping/trial/v2/en/sport_events/sr:sport_event:63301085/mappings.json
x-api-key: YOUR_API_KEY

{
  "generated_at": "2026-07-21T13:28:00+00:00",
  "sport_event": {
    "id": "63301085"
  }
}

The request pattern, pagination, and errors are covered in API Basics; the workflows are in Resolving IDs Across Products.