Skip to main content
Your existing endpoints are NOT going away. Every v1.football.sportsapipro.com, v2.basketball.sportsapipro.com, etc. URL keeps working forever. This page is about a new, optional, cleaner URL shape that points to the same data.

​
What changed

You can now call every version through a single host:
Same API key (x-api-key), same data, same rate limit — just a cleaner shape. We also hid the legacy /api/v1/ segment that V3, V4 and V6 used to expose, so URLs read naturally.

​
Side-by-side

​
WebSockets

The new host supports the same WebSocket pattern for both V1 and V2:
Identical payloads to wss://v{1|2}.{sport}.sportsapipro.com/ws?x-api-key=….

​
Authentication is identical

​
FAQ

No, never. Per our versioning policy, every published URL is permanent. We will not deprecate the subdomain shape. Migrate only if you want cleaner URLs.
Yes — both shapes resolve to the same API key, the same daily quota, and the same rate-limit bucket. Mixing them in one app is fine.
Those segments came from internal upstream paths and added no value for callers. The new shape uses /v{N}/ for our version and lets the endpoint speak for itself.
Yes. If your infrastructure prefers per-sport hostnames (separate firewall rules, separate CDN caches, etc.), keep using v{N}.{sport}.sportsapipro.com. Both shapes are first-class.

​
Rollout status

  • Subdomain hosts — production, permanent.
  • api.sportsapipro.com/v{N}/... — rolling out. If you hit any difference in payload between the two shapes, that’s a bug; please email [email protected] with the two curl commands.
Last modified on September 20, 2026