* version retirement

Deprecated, no dateSubscribe to Sportradar APIShare

Sportradar deprecated the /nhl/production/v3/* API endpoints without an announced shutdown date. This deprecation affects all requests sent to these version 3 paths. Once the retirement takes full effect, requests targeting these endpoints will fail.

Calls it hits

/nhl/production/v3/*
/nhl/trial/v3/*

What to use instead of these calls

Move to the current NHL API version at /nhl/production/v7/..., noting that Sportradar supports one current and two previous versions.

In Sportradar API's words

As part of our ongoing efforts to simplify and modernize our delivery infrastructure, we will be deprecating the following API versions within the next 90 days.

Sportradar API, Announcement

Facts

API: Sportradar API api.sportradar.com
Kind: Version retirement
Takes effect: No date given yet
Calls after that day: Fail
Source: Announcement
Last updated: October 25, 2026
Verified: November 6, 2026, against Sportradar API's own pages

Questions

When does this change take effect?

Sportradar API deprecated /nhl/production/v3/*, /nhl/trial/v3/* without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Sportradar API has not given a shutdown date yet.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub