Mappings · SportsStack

Mappings

One ID per player, team and event.

SportsStack matches them across your providers and publicly available sources, and keeps each provider's original ID attached.

Sold on its own. Keep the integrations you have. The Unified API is optional.

Illustrative. One player, four source IDs, one SportsStack ID.

01What it does

Mapped once. Kept matched.

Each source names the same player, team and game differently. SportsStack matches them across your sources and maintains the mappings.

One ID per entity
A player, team or event has the same ID across your sources.
Original IDs kept
Each record keeps the provider's own ID. A wrong match puts the wrong stat against the wrong player, so a questioned match can be checked against the source record.
Kept current
Trades, call-ups and rescheduled games change the picture. SportsStack maintains the mappings, not your engineers.

02How it works

One record. Each provider's ID.

Ask for a player by SportsStack ID. The record carries the ID each of your sources uses for the same player.

GET /api/v1/players/:id?return_source_id_format=sportradar200 OK
{
  "data": {
    "common_model_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "full_name": "Patrick Mahomes",
    "source_mappings": {
      "sportradar": {
        "player": {
          "a1b2c3d4-e5f6-7890-abcd-ef1234567890": "sr:player:1234"
        }
      }
    }
  }
}
Illustrative response.

03On its own

Keep your integrations. Add the IDs.

Mappings is sold on its own. You do not need the Unified API to use it. Your systems keep calling your providers. Mappings tells them which records are the same player, team or event across your sources.

On its own
For teams with integrations already in place. Keep them, and stop matching IDs by hand.
With the Unified API
The same IDs arrive attached to each record, in one schema.
With Settlement
Results can only be compared once the sources are matched. Mappings is that step.

Start with your hardest mapping.

Tell us which feeds you match by hand today.

Next: compare results across matched sources with Settlement