Steam Game Scraper - Reviews, Players & Owners avatar

Steam Game Scraper - Reviews, Players & Owners

Pricing

from $5.00 / 1,000 results

Go to Apify Store
Steam Game Scraper - Reviews, Players & Owners

Steam Game Scraper - Reviews, Players & Owners

Steam game scraper with no API key: merge store details, reviews, live player counts, and SteamSpy owner estimates into one row per game. Export CSV or JSON.

Pricing

from $5.00 / 1,000 results

Rating

0.0

(0)

Developer

Brandt May

Brandt May

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

20 hours ago

Last modified

Share

Steam Game Scraper - Reviews, Players & Ownership in One Dataset

The only Steam game scraper that merges store details, reviews, live concurrent players, and SteamSpy ownership estimates into a single row per game - no API key required.

What it does

This Steam game scraper pulls a complete market-intelligence snapshot for any Steam title and returns it as one clean row per game. Instead of a single-purpose price-and-reviews export, it merges four public Steam data sources - store details, user reviews, live concurrent player counts, and SteamSpy ownership estimates - so you get pricing, ratings, player activity, and owner estimates together in one dataset. Run it with no API key, query by Steam app ID or by search term, and export everything to CSV or JSON for market research, competitor analysis, or investment due diligence.

Use it as a Steam data API alternative: it returns game details, reviews, player counts, and ownership figures in one call, ready to drop into a spreadsheet, BI tool, or dashboard.

Who it's for

  • Indie game developers benchmarking competitors, genres, and pricing before launch
  • Publishers tracking portfolio performance and rival titles
  • Game-market analysts building genre, pricing, and player-trend datasets
  • Investors and VCs running due diligence on studios and titles
  • Marketing and UA teams sizing audiences and monitoring review sentiment
  • Competitive-research teams watching what similar games do on discounts, tags, and player retention

What you get (output)

Each game returns one merged row with the fields below. Review rows are returned separately when review enrichment is enabled.

FieldDescription
nameGame title
gameTypeType of app (game, DLC, etc.)
isFreeWhether the title is free-to-play
priceCurrent price
discountPercentActive discount percentage
releaseDateStore release date
developersDeveloper(s)
publishersPublisher(s)
genresSteam genres
categoriesSteam categories (e.g., multiplayer, controller support)
shortDescriptionStore short description
metacriticScoreMetacritic score
reviewScoreDescSteam review summary label (e.g., "Very Positive")
totalPositiveCount of positive reviews
totalNegativeCount of negative reviews
currentPlayersLive concurrent player count
ownersEstimateSteamSpy owner estimate
ownersEstimateMinLower bound of the owner estimate
ownersEstimateMaxUpper bound of the owner estimate
steamSpyCcuSteamSpy concurrent-user figure
topTagsTop community tags
headerImageStore header image URL
storeUrlSteam store page URL

Review rows (when reviews are enabled): individual review records tied to each game, so you can export Steam reviews to CSV or JSON for sentiment work.

Input / how to query

Two ways to select games, plus optional enrichment toggles:

Modes

  • By app ID - pass one or more Steam app IDs to scrape exactly the titles you want
  • By search term - pass search terms to discover matching games, then scrape them

Filters and options

  • app IDs - target specific Steam titles directly
  • search terms - discovery mode for finding games by keyword
  • include reviews - add per-game review rows and review counts
  • include SteamSpy - add owner estimates and SteamSpy CCU
  • include player count - add live concurrent player counts
  • country - set the country/region for pricing

Enable only the enrichment you need. Turn everything on for a full market-intelligence snapshot; keep it minimal for a fast price-and-rating pull.

Example use cases

  1. Indie competitor benchmark - feed a list of 50 rival app IDs, enable reviews + SteamSpy + player count, and export a single CSV comparing price, discount, review score, owner estimates, and live players across your genre.
  2. Sales and revenue estimation - combine SteamSpy owner estimates with price and review counts to model a title's approximate sales and revenue for a pitch deck or investment memo.
  3. Genre trend dataset - use search-term discovery to pull every game matching a keyword (e.g., "roguelike deckbuilder"), then build a dataset of tags, pricing, and player activity.
  4. Live player-count monitoring - schedule daily runs on a watchlist of app IDs to track concurrent players over time and spot momentum shifts.
  5. Review sentiment export - enable reviews on a set of titles to export Steam reviews to JSON for sentiment analysis or feature-request mining.

Recurring use and scheduling

For monitoring, run this on a schedule (Apify Schedules) - daily or weekly against a fixed list of app IDs. Live currentPlayers, discountPercent, review counts, and SteamSpy figures all change over time, so recurring runs build a trend history for prices, players, ratings, and ownership.

To keep a single growing table clean, use dataset deduplication by keying on the game (app ID) so each scheduled run updates rather than duplicates rows, or append timestamped snapshots when you want a time series. Point the output at your storage, BI tool, or webhook to feed dashboards automatically.

FAQ

How do I scrape Steam game data without an API key?

Run this actor - it reads public Steam storefront and SteamSpy data directly, so no Steam API key is required. Just provide app IDs or search terms and it returns the merged dataset.

How can I export Steam reviews to CSV or JSON?

Enable the include reviews option. The actor returns individual review rows alongside each game, and every Apify dataset exports to CSV, JSON, Excel, and other formats.

How do I estimate a Steam game's sales and revenue from reviews?

Enable include SteamSpy to get ownersEstimate (with min/max bounds). Combine those owner estimates with price and the positive/negative review counts to model approximate sales and revenue in your own spreadsheet.

How do I get SteamSpy owner estimates in bulk?

Pass a list of app IDs (or discover them with search terms), enable include SteamSpy, and each row returns ownersEstimate, ownersEstimateMin, ownersEstimateMax, and steamSpyCcu.

How can I track live concurrent player counts for Steam games?

Enable include player count to get currentPlayers per title, then schedule the run daily or hourly on a watchlist to track concurrent players over time.

What is the best tool to research Steam competitors for my indie game?

Use search-term discovery to find rival titles in your genre, then enable reviews, SteamSpy, and player count to compare pricing, discounts, ratings, owner estimates, and live players side by side in one export.

How do I pull Steam price, discount, and Metacritic data for many games at once?

Pass multiple app IDs (or search terms) in a single run. Each row returns price, discountPercent, and metacriticScore along with the rest of the store details - no per-game API calls to manage.

How do I get Steam store, reviews, players, and ownership data in one dataset?

That is exactly what this scraper is built for. Enable all three enrichments and each game row merges store details, review counts, live currentPlayers, and SteamSpy ownership estimates together.

Is there a Steam API alternative that returns game details, reviews, and player counts together?

Yes - this actor merges Steam store details, review data, live player counts, and SteamSpy ownership into one row per game, without requiring a Steam API key, so it works as a drop-in data source for research pipelines.

How do I collect Steam data for market analysis or investment research?

Query the titles or genres you care about, enable SteamSpy and player-count enrichment, and export the merged dataset. The owner estimates, pricing, review scores, and player counts give you the inputs for market sizing and due diligence.

Data source and notes

  • Sources: Public Steam storefront endpoints (appdetails, appreviews, and current-players data) plus SteamSpy for ownership estimates. No Steam API key is used.
  • Public data: All fields come from publicly accessible Steam and SteamSpy data.
  • Estimates are estimates: ownersEstimate, ownersEstimateMin/Max, and steamSpyCcu are SteamSpy's modeled figures, not official Steam sales numbers. Treat them as directional, not exact.
  • Live values change: currentPlayers, price, discountPercent, and review counts are point-in-time; schedule recurring runs to build history.
  • Regional pricing: set the country option to control the currency/region of price fields.