The Mapping Feeds in this API serve two specific purposes:

Linking IDs between APIs — If you are using both the NBA API and the Global Basketball API, these feeds allow you to cross-reference entity IDs between the two products, so that teams, competitors, and players can be consistently identified across both.
Resolving merged IDs — In cases where duplicate competitor or player records have been consolidated into a single unique ID, these feeds surface that relationship so you can update any stored references accordingly.

🔗
Tip:
For broader entity ID mapping across Sportradar products — including competitions, sport events, seasons, and players — the Mapping API offers a more scalable, dedicated solution. If your use case extends beyond NBA and Global Basketball ID linking, we recommend starting there.

What’s Next

What’s Next