New Path-Based API URLs

Cleaner api.sportsapipro.com/v//… endpoints — your existing subdomain URLs keep working forever

Your existing endpoints are NOT going away. Every v1.football.sportsapipro.com, v2.basketball.sportsapipro.com, 1xbet.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:

https://api.sportsapipro.com/v{N}/{sport}/{endpoint}

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, V5 and V6 used to expose, so URLs read naturally.

Side-by-side

Version	Classic (still works forever)	New canonical
V1	v1.football.sportsapipro.com/games/current	api.sportsapipro.com/v1/football/games/current
V2	v2.football.sportsapipro.com/api/events/live	api.sportsapipro.com/v2/football/events/live
V3	v3.tennis.sportsapipro.com/api/v1/events	api.sportsapipro.com/v3/tennis/events
V4	v4.football.sportsapipro.com/api/v1/league/3/standings	api.sportsapipro.com/v4/football/league/3/standings
V5	1xbet.sportsapipro.com/api/v1/sports	api.sportsapipro.com/1xbet/sports (no sport segment)
V6	v6.football.sportsapipro.com/api/v1/matches	api.sportsapipro.com/v6/football/matches

V5 (1xBet) ships as a single sportsbook surface, so the new shape doesn’t include a sport segment. Use api.sportsapipro.com/1xbet/{endpoint} directly. The alias api.sportsapipro.com/v5/{endpoint} resolves to the same surface for callers who prefer version-numbered URLs.

WebSockets

The new host supports the same WebSocket pattern for both V1 and V2:

wss://api.sportsapipro.com/v1/football/ws?x-api-key=YOUR_API_KEY
wss://api.sportsapipro.com/v2/football/ws?x-api-key=YOUR_API_KEY

Identical payloads to wss://v{1|2}.{sport}.sportsapipro.com/ws?x-api-key=….

Authentication is identical

# Classic
curl -H "x-api-key: YOUR_API_KEY" \
  "https://v2.football.sportsapipro.com/api/events/live"

# New canonical — same key, same response
curl -H "x-api-key: YOUR_API_KEY" \
  "https://api.sportsapipro.com/v2/football/events/live"

FAQ

Do I have to migrate?

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.

Are quotas/rate limits shared?

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.

Why hide `/api/v1/` on V3/V4/V5/V6?

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.

Can I pin to subdomain for sport-isolated allow-lists?

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.

What about V5 — why no sport in the path?

V5 is the 1xBet sportsbook surface and was always a single host (1xbet.sportsapipro.com). The new shape mirrors that: api.sportsapipro.com/v5/sports, api.sportsapipro.com/v5/live/event/{id}, etc.

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 [e-mail] with the two curl commands.