Authentication & Rate Limits
Access to the SteamID.com API is governed by a key-based authentication system and usage quotas to ensure fair access and system stability.
Authentication
Section titled “Authentication”All requests to the API must include a valid API key.
Using an API Key
Section titled “Using an API Key”You should pass your API key as a key query parameter in every request.
Example Request:
GET /api/v1/players/76561197960435530?key=YOUR_API_KEYRate Limits & Quotas
Section titled “Rate Limits & Quotas”To protect the service and ensure reliable performance, we implement both rate limits and token quotas. These are determined by your subscription plan.
Rate Limits
Section titled “Rate Limits”Your rate limit is set in requests per minute. Every request counts as 1 against your rate limit. If you go over your rate limit you will be unable to make requests until the following minute.
Tokens
Section titled “Tokens”Most requests count as 1 token. If you trigger an update by using the maxAgeSeconds parameter you
will be charged an extra 4 tokens (5 total for the request). If the data already recent enough to
satisfy your maxAgeSeconds parameter you won’t be charged the 4 tokens. If we are unable to complete
your request for whatever reason (Steam is down, too slow, etc.) you won’t be charged any tokens.
The one exception to the 1 token per request rule is the “Get Player Summaries” endpoint. This is the endpoint that mimics the Steam API and can return up to 100 profiles at once. This is billed at a rate of 0.5 (half a token) rounded up. One profile is 1 token, two profiles is 1 token, three profiles is 2 tokens, 43 profiles is 22 tokens.
Pricing
Section titled “Pricing”Basic
Ideal for small projects and individual developers.
- Historical Data Access
- REST & XML Support
- Aggregated Data Views
Plus
Great for growing applications and small teams.
- Historical Data Access
- REST & XML Support
- Aggregated Data Views
Advanced
Built for high-traffic applications.
- Historical Data Access
- REST & XML Support
- Aggregated Data Views
Best Practices
Section titled “Best Practices”- Cache Locally: Whenever possible, cache API responses locally to reduce the number of requests and stay within your quota.
- Use Modern Endpoints: Our V1 API often provides aggregated data that would require multiple calls to the official Steam API, helping you save on your total request count.
Getting a Key
Section titled “Getting a Key”To obtain an API key, visit the SteamID.com Dashboard. You can sign up for a free account and choose a pricing plan to receive your key immediately.