Steam Web API documentation.
This page documents the Steam Web API, a reference for the interfaces and methods exposed by Valve's Steam platform. The documentation is auto-generated from GetSupportedAPIList combined with public and publisher keys, and supplemented with service methods parsed from the Steam client's protobuf files. It covers a large number of interfaces spanning account management, store and catalog data, user statistics, inventory, matchmaking, workshop content, broadcasting, and game-specific APIs for titles including Counter-Strike 2, Dota 2, Team Fortress 2, Deadlock, Portal 2, Dota Underlords, and Artifact.
Access to the API operates at three levels: public methods requiring no authentication, methods requiring a user Web API key available to any Steam account holder, and protected methods requiring a publisher Web API key for sensitive data or actions. Requests can supply a key via a query parameter or an x-webapi-key header, or use access tokens (used by Steam's own Store and Community pages) via an access_token parameter, though not all methods support both. The API also supports Steam as an OpenID provider for third-party authentication.
The public API is hosted at api.steampowered.com or community.steam-api.com and sits behind Akamai's edge cache, with IPs that can change. A partner-only host at partner.steam-api.com is available for higher availability from secure servers, is HTTPS-only, is not behind Akamai's cache, and requires a publisher key on every request. Publisher keys must be stored securely server-side, never distributed with game clients, and used only over HTTPS; many methods have undocumented rate limits that return HTTP 429 or specific eresult codes when exceeded. The site includes an interactive interface for entering a key or access token, selecting an output format (JSON, VDF, or XML), and executing requests directly in the browser. This resource is intended for developers building tools or integrations against Steam's platform data and services.
Public methods require no authentication, while others require a free user Web API key obtainable by any Steam account holder; protected methods need a publisher Web API key.
The API supports JSON, VDF, and XML, with XML noted as not recommended.
Requests use either a Web API key (via a key query parameter or x-webapi-key header) or an access token sent as the access_token parameter, though not all APIs support both methods.
It's for developers building tools or games that integrate with Steam services like store data, community features, and specific games such as Dota 2, CS2, and Team Fortress 2.
Yes, many methods have undocumented rate limits that vary by method, returning HTTP 429 or specific eresult codes when exceeded.
Show your product to thousands of developers
· 100k monthly pageviews
· 7k newsletter subscribers
Sakura CardCaptor Cards Information.
Magic: The Gathering database.
A playable inter-galactic space trading MMOAPI.
Internal Steam Web API documentation.
Trading card game prices and historical data across 89+ games.
Multi languages Pokémon TCG Information.