Skip to content
All posts
Blog

Announcing VLRdevAPI v2.0

A new major release with a synchronous client, typed exceptions, and expanded coverage across matches, teams, players, events, and series.

We're excited to announce VLRdevAPI v2.0 — the biggest update to the library since its initial release. This version introduces a redesigned synchronous client and comprehensive coverage across five namespaces.

What's New

Synchronous by Design

v2.0 drops the async API from v1.x. Every method is a plain blocking call that returns a typed model:

import vlrdevapi

matches = vlrdevapi.matches.upcoming()
print(f"{len(matches.matches)} upcoming matches")

For concurrent work, run independent calls in a thread pool. Multi-stage endpoints already fetch their pages in parallel internally.

Five Namespaces

VLRdevAPI v2.0 organizes all data into five clean namespaces:

NamespaceCoverage
matchesUpcoming, live, and completed matches
teamTeam info, rosters, stats, placements
playerProfiles, agents, teams, match history
eventEvents, stages, standings, teams, matches
seriesSeries info, VODs, player stats, economy

(Note: In subsequent releases starting with v2.4, a sixth namespace news was added for news listings and full article content.)

Typed Exception Hierarchy

import vlrdevapi
from vlrdevapi.exceptions import NotFoundError, RateLimitError

try:
    team = vlrdevapi.team(2593).info()
    print(f"Team: {team.name}")
except NotFoundError:
    print("Team not found")
except RateLimitError:
    print("Slow down!")

Curried Access Pattern

Bind an ID once and chain method calls:

team = vlrdevapi.team(2593)
print(team.info().name)
roster = team.roster()
print(f"{len(roster.players)} players on roster")
stats = team.stats(last_days=90)
print(f"{len(stats.maps)} maps in stats")

Upgrading from v1.x

If you're upgrading from v1.x, the main changes are:

  • VLRClient is synchronous and supports the context manager protocol; v1.x's async with pattern is gone
  • Module-level access is still available for quick scripts
  • Exception types have been moved to vlrdevapi.exceptions
  • New namespaces: series and event require no additional setup

What's Next

We're working on rate limit tuning, additional query parameters, and community-requested endpoints. Check the changelog for detailed release notes and the docs for full API reference.

Next step

Ready to build with VLRdevAPI?

Install the Python SDK and start fetching Valorant esports data in minutes. No API key required.

uv add vlrdevapi
Read the docs