Overview & Features
The SteamID.com API provides a comprehensive and highly compatible interface for accessing Steam community data. It is designed to serve as both a drop-in replacement for existing Steam APIs and a modern, feature-rich alternative for developers who need historical tracking and enhanced data structures.
Core Features
Section titled “Core Features”1. Steam Web API Compatibility
Section titled “1. Steam Web API Compatibility”The API implements key interfaces from the official Steam Web API, allowing you to migrate existing applications with minimal code changes. Supported interfaces include:
- ISteamUser:
GetPlayerSummaries,GetPlayerBans - IPlayerService:
GetOwnedGames,GetSteamLevel,GetBadges
2. Legacy XML Drop-in
Section titled “2. Legacy XML Drop-in”Steam’s legacy XML profile data is still widely used by many tools. We provide a compatible endpoint that mimics the structure and behavior of Steam’s XML profiles.
- Support for:
https://steamcommunity.com/id/{customUrl}/?xml=1andhttps://steamcommunity.com/profiles/{steamId64}/?xml=1.
3. Modern V1 REST API
Section titled “3. Modern V1 REST API”For new projects, our V1 API offers a clean, RESTful structure with enhanced data not available in the standard Steam API:
- Rich Player Data: Combined profile information, ban status, and friend/group counts in a single request.
- Historical Tracking: Access historical changes to names, avatars, and ban statuses.
- Advanced Pagination: Efficiently browse large friend lists, group memberships, and game libraries.
4. High Availability & Caching
Section titled “4. High Availability & Caching”We serve as a proxy and caching layer that ensures fast response times and protects against Steam API downtime or rate limiting issues. Look up Steam profiles 7 days a week, including Tuesdays.
Why use this API?
Section titled “Why use this API?”- No more 429s: Documented rate and request limits. Let us worry about Steam rate limits, queuing and batching requests, and unexpected responses.
- Historical Insights: See how a player’s profile has changed over time.
- Simplified Integration: One API for both modern JSON and legacy XML needs.
- Enhanced Performance: Aggregated data reduces the number of round-trips to Steam.