Steam Games Scraper

Pricing

Rating

Developer

Actor stats

Categories

Share

Scrape Steam games and store signals for discovery, pricing, release tracking, demos, and game updates. The actor returns normalized dataset rows that are ready for search indexes, watch lists, dashboards, or downstream enrichment pipelines.

What it can scrape

• Steam search results by keyword.
• Latest Steam releases by category, genre, or tag.
• Steam specials and current discounts.
• Steam demos and coming soon titles.
• Steam app news and update announcements by app ID, URL, or title query.

Useful inputs

• mode: search, new_releases, deals, demos, coming_soon, or updates.
• query: game title or search text.
• category: Steam tag, genre, or category filter such as rpg, strategy, or roguelike.
• gameId: Steam app ID for update checks.
• gameUrl: Steam store URL for update checks.
• maxItems: maximum records to return.

Output fields

Each result includes platform, platformGameId, title, url, matchSource, signalTypes, description, developer, publisher, releaseDate, lastUpdatedAt, coverImageUrl, tags, genres, supportedSystems, hasDemo, demoUrl, isComingSoon, isReleased, currentPrice, originalPrice, currency, discountPercent, isFree, sourceFetchedAt, and raw source data.

Rows also include sourceKind, sourceConfidence, and sourceNotes so downstream apps can distinguish official Steam API data from weaker platform fallbacks.

Billing result definition

One result is one normalized Steam game, discount, release, demo, coming-soon, app news, or update row written to the default dataset. The SUMMARY key-value record and optional Firebase cache writes are not dataset results. If you run this actor with Apify pay-per-event monetization, price the result-item event so pricing maps directly to delivered dataset rows.

MCP connector export

Optionally select outputConnectors to send delivered Steam rows to your own MCP-connected tools through Apify's MCP proxy. Auto mode can call common send/post/write/log tools with a markdown or JSON payload. For tools with strict schemas, set connectorToolName and connectorToolArgumentsJson, using template values such as {{markdown}}, {{records}}, {{summary}}, {{datasetId}}, and {{runUrl}}.

Example inputs

{"mode":"new_releases","category":"rpg","maxItems":10}

{"mode":"updates","gameId":"1145360","maxItems":5}