canonical: https://jentic.com/apis/steampowered.com/steampowered

# Steampowered Steam Web API

The Steam Web API provides programmatic access to Steam data including player profiles, game stats, achievements, trade offers, news, and more. The API exposes 38 endpoints.

## For AI agents

Programmatically get player profile data, get friend list. Covers 38 operations.

## Scope

Does not handle payments, communications, or crm - use for social media only.

## Capabilities

- Get player profile data
- Resolve vanity URL to Steam ID
- Integrate Steam Web API into automated workflows
- Query and filter Steam Web API records by parameters
- Monitor Steam Web API operational status and events

## Use cases

### Social Media Operations

Use the Steam Web API to perform social media operations programmatically. The API provides 38 endpoints covering core functionality including get player profile data, get friend list, get player ban info.

Example prompt: Call GET /ISteamUser/GetPlayerSummaries/v2 to get player profile data

### Automated Apps Management

Automate apps operations by combining multiple Steam Web API endpoints. Agents can get friend list and then get player ban info in a single workflow.

Example prompt: Call GET /ISteamUser/GetFriendList/v1 to get friend list, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Steam Web API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'get player profile data', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /ISteamUser/GetPlayerSummaries/v2 | Get player profile data |
| GET | /ISteamUser/GetFriendList/v1 | Get friend list |
| GET | /ISteamUser/GetPlayerBans/v1 | Get player ban info |
| GET | /ISteamUser/GetUserGroupList/v1 | Get user group list |
| GET | /ISteamUser/ResolveVanityURL/v1 | Resolve vanity URL to Steam ID |
| GET | /ISteamUserStats/GetGlobalAchievementPercentagesForApp/v2 | Get global achievement percentages |
| GET | /ISteamUserStats/GetGlobalStatsForGame/v1 | Get global stats for game |
| GET | /ISteamUserStats/GetNumberOfCurrentPlayers/v1 | Get current player count |

## Key resources

- **Apps** — Operations related to Apps
- **Auth** — Operations related to Auth
- **CS2** — Operations related to CS2
- **DOTA 2** — Operations related to DOTA 2
- **Economy** — Operations related to Economy

## Why Jentic

- **Setup:** Wiring the Steam Web API by hand means learning its interface-and-method URL style, mapping the user, stats and news calls, and shaping the steamid query parameters yourself. Through Jentic you install once, import the Steam Web API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** You limit the agent to the operations it needs, such as getting player summaries or the friend list, so it only reads the data you intend. Because the steamid travels in the query rather than the URL path, scope the agent by operation rather than by a single account.
- **Credential handling:** Your Steam credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get player profile data' or 'get the current player count for a game', and Jentic returns the matching Steam Web API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Steam Web API use?

The Steam Web API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get player profile data with the Steam Web API?

Yes. Use the GET /ISteamUser/GetPlayerSummaries/v2 endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Steam Web API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get player profile data through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get player profile data'. Jentic returns the matching Steam Web API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Steam Web API have?

The Steam Web API exposes 38 endpoints covering apps, auth, cs2 operations.

### Can I limit what my agent is allowed to do with the Steam Web API?

Yes. Because Jentic One is self-hosted, you decide which Steam Web API operations your agent may call, so you can allow read-only calls like GetPlayerSummaries, GetFriendList, or GetPlayerBans while withholding everything else. Since the steamid travels in the query string rather than the URL path, you scope the agent by operation instead of by a single account, granting only the specific calls a task needs. The Steam credential is held by your own instance and injected only for the operations you have permitted, so the agent never gains broader access than your rules allow.