# Steam Scraper — Game Prices, Discounts, Reviews & Deal Alerts (`xqfech/steam-scraper`) Actor

Scrape the Steam store: specials, top sellers, new releases and specific games with prices, discounts, review scores and tags. Also diffs every run against the last one and emits field-level change events — new discounts, price drops and review-score movements.

- **URL**: https://apify.com/xqfech/steam-scraper.md
- **Developed by:** [Emmanuel Obiefule](https://apify.com/xqfech) (community)
- **Categories:** E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 change events

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Steam Monitor — Track Game Discounts, Price Changes & Review Movements

Snapshot scrapers tell you what Steam looks like right now. This Actor tells you **what changed since your last run**: a game you track just went on sale, a price changed in your region, a review score moved, a new title entered the top sellers — as structured change events with field-level before/after diffs.

Built on Steam's public store JSON endpoints. No login, no browser, no proxies — fast and stable.

### What it does

- **Watch store lists** — `specials` (discounts feed), `top_sellers`, `new_releases`, `coming_soon`. Every run diffs the list against the previous run: `new_game` (e.g. a fresh discount appeared), `removed_game` (sale ended), `game_changed` (discount percent moved).
- **Watch specific games** — pass Steam app IDs. Tracks regional price, discount, review score & verdict (e.g. "Very Positive"), review count, positive ratio, and release status. A `game_changed` event with `discountPercent: null → 60` is your wishlist alert.
- **Regional pricing** — set any country code (us, de, pl, ua, ...) and monitor prices in that region.

### Who uses this

- **Deal hunters & communities** — price-drop and new-discount feeds for Discord bots, deal sites, newsletters.
- **Game developers & publishers** — competitor pricing moves, review score trends, top-seller entries in your genre.
- **Market analysts** — top-seller churn and discount depth over time, straight into Sheets or a webhook.

### Output example

```json
{
  "type": "game_changed",
  "source": "watch",
  "appId": 1091500,
  "name": "Cyberpunk 2077",
  "url": "https://store.steampowered.com/app/1091500/",
  "changes": [
    { "field": "discountPercent", "before": null, "after": 70 },
    { "field": "finalPriceCents", "before": 5999, "after": 1799 }
  ],
  "detectedAt": "2026-08-04T10:00:00.000Z"
}
```

### Input

| Field | Description |
| --- | --- |
| `lists` | Store lists watched as sets: specials, top\_sellers, new\_releases, coming\_soon |
| `appIds` | Steam app IDs tracked with field-level diffs |
| `countryCode` | Region for pricing |
| `monitorId` | State namespace shared between runs |

### Reliability

Public JSON endpoints only — the same ones the Steam store frontend uses. Strict schema validation on every item; the run fails loudly rather than storing garbage. Noisy counters (review totals) are banded so you only see meaningful movement. First run stores a baseline; change events start from run two.

### Scheduling

Run every few hours via an Apify Schedule and pipe events to Slack, Discord (webhook), email, or Google Sheets through Apify integrations. Quiet runs cost almost nothing.

# Actor input Schema

## `lists` (type: `array`):

Any of: specials, top\_sellers, new\_releases, coming\_soon. Every run diffs the list against the previous run: games entering (e.g. new discount in specials), leaving, and changing.

## `appIds` (type: `array`):

Numeric Steam app IDs (e.g. 1091500 for Cyberpunk 2077). Tracks price, discount, review score, review count and release status with field-level diffs.

## `countryCode` (type: `string`):

Two-letter country code for regional pricing (us, de, pl, ua, ...).

## `monitorId` (type: `string`):

State namespace. Runs with the same Monitor ID share the previous-run snapshot.

## `emitBaseline` (type: `boolean`):

On the very first run the full initial snapshot is pushed as baseline items so you still get data.

## Actor input object example

```json
{
  "lists": [
    "specials"
  ],
  "appIds": [
    1091500
  ],
  "countryCode": "us",
  "monitorId": "default",
  "emitBaseline": true
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "lists": [
        "specials"
    ],
    "appIds": [
        1091500
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("xqfech/steam-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "lists": ["specials"],
    "appIds": [1091500],
}

# Run the Actor and wait for it to finish
run = client.actor("xqfech/steam-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "lists": [
    "specials"
  ],
  "appIds": [
    1091500
  ]
}' |
apify call xqfech/steam-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,xqfech/steam-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/fwbJiymAv5g67IVt5/builds/okILLQ7wYh5I46G6M/openapi.json