These docs are for Python developers who want a typed, cached client for the public Valorant API. Start here if you want the reader path; use the reference pages when you already know what you want to look up.
- New to the wrapper: read Getting Started.
- Looking for common workflows and tradeoffs: read Usage Patterns.
- Want the notebook walkthrough: open Tutorials.
- Need signatures, fields, or enum values: use the Reference.
- A single
ValorantAPIclient for the main public/v1endpoints. - Typed Python models instead of raw response dictionaries.
- Built-in caching through
pypercache, which is useful for mostly-static game metadata. - Convenience helpers for common lookup patterns such as playable agents, name-based search, active events, and current season data.
Narrative pages explain when to use the wrapper, how to move through the API, and what tradeoffs matter in normal use. Reference pages are generated from source and are for fast lookup, not onboarding. If a generated summary is too thin for an important API, improve the code docstring or the narrative guide instead of editing generated reference by hand.