Steam API. Apps, reviews, charts and market.

Yes. Social Fetch has nineteen Steam routes under /v1/steam: app details, a batch app lookup, store search, catalogue browse, suggestions, reviews, review totals, review history, player counts, news, achievements, community hubs, charts, tags, featured items, market search, market price, groups and the hardware survey. Authenticate with your Social Fetch API key in x-api-key.

The app id is the number in the store URL: 570 for Dota 2, 620 for Portal 2, 730 for Counter-Strike 2. Pass the number, a numeric string, or the full store URL. For discovery, use apps/search with a query such as portal, then read the id of each result.

On found, data.app carries the app fields: name, type, url, developers, publishers, genres, categories, tags, languages, platforms and device ratings, release date, price, screenshots, trailers, purchase options, review summaries, anti-cheat, the AI disclosure and the developer's links. Trailer entries carry HLS and DASH stream URLs for the full videos and MP4 and WebM URLs for the short silent previews. Review summaries count Steam purchases only; use the review summary route with purchase=all for every purchase type. data.incomplete lists any group that is temporarily unavailable.

A country can restrict an app that exists elsewhere. The response then has lookupStatus not_found, unavailableInCountry true and the app's name in data.name, with data.app null. The app's reviews, news and community routes do not depend on the country, so they can still return data.

GET /v1/steam/apps/{appId}/reviews returns up to 100 reviews per page with the author, language, text, recommendation, playtime, helpful and funny votes, reactions, shared hardware and any developer reply. Filter by language, sentiment, purchase type, minimum or maximum playtime, and a date range. Follow page.nextCursor with the same filters for the next page. With sentiment=positive or sentiment=negative, data.summary is null because no totals are available for a filtered list.

Yes. GET /v1/steam/apps/{appId}/reviews/summary returns totalReviews, positive, negative, score, scoreLabel and percentPositive for one language or all languages. Use purchase=all for every review, or purchase=steam for Steam purchases only, which is the count on an app record. GET /v1/steam/apps/{appId}/reviews/histogram returns periods of positive and negative counts by week or month, plus roughly the last 30 days in recentDays.

GET /v1/steam/charts takes chart=most_played, daily_peak or top_sellers. Entries carry rank, appId, name, url, price, currentPlayers, peakPlayers, lastWeekRank and consecutiveWeeks where they apply. Top sellers also take a country and any date in the week you want; dates after today are refused.

Each completed request charges the amount shown on its endpoint page, and each page of a list is a separate request. The batch app lookup charges per requested app id, found or not. Check meta.creditsCharged on every response. Failed requests are free.

found means the app, group or market item was returned. not_found means the id or name does not exist, or the app exists but is not sold in the requested country; in that second case unavailableInCountry is true and data.name carries the app's name. HTTP 200 only means the request finished, so always branch on data.lookupStatus before writing a row.

Some parts of an app record can be missing on their own, such as tag names or the extra app fields. data.incomplete names the affected group, for example store_item or tag_names, while the rest of the record is still usable. An empty incomplete array means the record is complete.

Yes. Every Steam route is a typed MCP tool and is reachable through Ask (POST /v1/ask) in plain English. Use the typed routes for production jobs, where the parameters and response shape are fixed.