Steam Reviews Scraper

What does Steam Reviews Scraper do?

Steam Reviews Scraper collects public Steam Community discussion topics from a game's discussion hub. Provide a Steam app ID or a Steam Community discussions URL, and receive structured records with topic titles, authors, reply counts, awards, activity timestamps, topic status, and the complete opening post when available.

The dataset is useful for monitoring player feedback after launches and updates, researching recurring issues, triaging support topics, and comparing community activity across Steam games.

Why use Steam Reviews Scraper?

• Collect discussion data in bulk - Gather many topics without manually opening individual Steam Community pages.
• Capture the full opening post - Preserve the original discussion context for feedback analysis and issue classification.
• Track community activity - Use reply counts, awards, pinned or locked status, and last activity fields to identify important topics.
• Support repeatable research - Run the Actor on demand or schedule recurring collections through Apify.
• Use structured exports - Download results as JSON, CSV, Excel, XML, or connect the dataset to another workflow.

What data can you extract from Steam Community discussions?

Each dataset item represents one discussion topic. Fields that Steam does not provide for a topic are omitted from the saved item.

Field	Type	Description
app_id	String	Steam app ID for the discussion hub.
app_name	String	Game name shown on the discussion page.
forum_id	Integer	Steam forum ID used for the collection.
forum_name	String	Human-readable forum name when available.
forum_gid	String	Steam forum identifier when available.
page_number	Integer	Discussion listing page where the topic was found.
position	Integer	Topic position on its listing page.
forum_total_topics	Integer	Total active topic count reported for the forum.
topic_id	String	Unique Steam topic identifier.
title	String	Discussion topic title.
url	String	Direct Steam Community topic URL.
author_name	String	Topic author name.
author_url	String	Author profile URL when available.
reply_count	Integer	Number of replies shown for the topic.
award_count	Integer	Number of awards shown for the topic.
preview	String	Preview text shown in the discussion listing.
created_by	String	Author name from topic metadata.
created_at_text	String	Human-readable topic creation time.
last_poster_name	String	Author of the latest post shown in the listing.
last_posted_at	String	ISO timestamp for the latest activity when available.
last_posted_at_text	String	Human-readable latest activity timestamp.
last_posted_text	String	Relative latest activity text from Steam.
is_pinned	Boolean	Whether the topic is pinned.
is_locked	Boolean	Whether the topic is locked.
is_answered	Boolean	Whether Steam marks the topic as answered.
opening_posted_at_text	String	Human-readable opening post timestamp.
opening_post_body	String	Plain-text opening post content.
opening_post_body_html	String	Original opening post markup when available.
opening_post_last_edited_text	String	Last edited information shown on the topic page.
is_developer_post	Boolean	Whether the opening post is marked as a developer post.

How to scrape Steam discussion data

1. Open Steam Reviews Scraper in Apify Console.
2. Enter a Steam app ID or a public Steam Community discussions URL.
3. Set the maximum number of topics and listing pages to collect.
4. Start the run and review the dataset preview.
5. Download the results or connect the dataset to your research, support, or analytics workflow.

The startUrl value takes priority when both appId and startUrl are provided. A Steam Store app URL can also be used because the app ID is detected from the URL.

Input Parameters

Parameter	Type	Required	Default	Description
appId	String	No	2868840	Steam app ID used to build the discussions URL when startUrl is not provided.
startUrl	String	No	https://steamcommunity.com/app/2868840/discussions/	Steam Community discussions URL or Steam Store app URL. This takes priority over appId.
results_wanted	Integer	No	20	Maximum number of discussion topics to save.
max_pages	Integer	No	3	Maximum number of discussion listing pages to request.

Usage Examples

Basic App ID Run

Collect up to 20 topics from the discussion hub for a Steam game.

{
  "appId": "2868840",
  "results_wanted": 20
}

Collect From a Discussions URL

Use a specific Steam Community discussions URL as the collection starting point.

{
  "startUrl": "https://steamcommunity.com/app/2868840/discussions/",
  "results_wanted": 50,
  "max_pages": 5
}

Larger Feedback Dataset

Request more topics and listing pages for launch monitoring or a broader research dataset.

{
  "appId": "2868840",
  "results_wanted": 200,
  "max_pages": 15
}

Sample Output

The following example shows one discussion record with listing metadata and opening post details.

{
  "app_id": "2868840",
  "app_name": "Slay the Spire 2",
  "forum_id": 0,
  "forum_name": "General Discussions",
  "forum_gid": "123456789",
  "page_number": 1,
  "position": 1,
  "forum_total_topics": 124,
  "topic_id": "4355620416676744549",
  "title": "Slay the Spire 2 FAQ",
  "url": "https://steamcommunity.com/app/2868840/discussions/0/4355620416676744549/",
  "author_name": "demileaf",
  "author_url": "https://steamcommunity.com/id/demileaf",
  "reply_count": 0,
  "award_count": 0,
  "preview": "Frequently asked questions and useful information.",
  "created_by": "demileaf",
  "created_at_text": "Posted by demileaf",
  "last_poster_name": "demileaf",
  "last_posted_at": "2026-03-12T11:43:00.000Z",
  "last_posted_at_text": "1 May, 2024 @ 1:43pm",
  "last_posted_text": "Last post by demileaf",
  "is_pinned": true,
  "is_locked": true,
  "is_answered": false,
  "opening_posted_at_text": "1 May, 2024 @ 1:43pm",
  "opening_post_body": "Hi everyone, welcome to Slay the Spire 2's Steam Forums!",
  "opening_post_body_html": "<div>Hi everyone, welcome to Slay the Spire 2's Steam Forums!</div>",
  "opening_post_last_edited_text": "Last edited by demileaf; 2 Mar @ 12:39pm",
  "is_developer_post": true
}

Tips for Best Results

• Start with results_wanted: 20 to confirm the fields and discussion scope you need.
• Use the main app discussions URL when you want the default forum, or provide a forum-specific URL when targeting a particular discussion area.
• Increase max_pages together with results_wanted when collecting older or less active topics.
• Keep scheduled runs consistent when comparing reply counts, awards, and recent activity over time.
• Review the dataset preview because Steam may omit author, timestamp, award, or opening-post fields for individual topics.

Integrations and Export Formats

• Google Sheets - Review topics, activity, and feedback with a team.
• Airtable - Build a searchable discussion library for support or research.
• Make and Zapier - Trigger notifications, tagging, or database updates after a run.
• Webhooks - Send completed run events and dataset links to your own service.
• Apify API - Start runs and retrieve dataset items programmatically.

Apify datasets can be downloaded as JSON, CSV, Excel, XML, and other supported formats.

Frequently Asked Questions

Does this Actor collect Steam Store reviews?

No. It collects Steam Community discussion topics and opening posts from a game's discussion hub. It does not return the review scores or recommendation text from the Steam Store review system.

Can I collect more than one discussion page?

Yes. Increase max_pages to request more listing pages, and increase results_wanted if you want the larger result set saved.

Can I use a Steam Store app URL?

Yes. Provide a public Steam Store app URL in startUrl, and the app ID is detected before the discussion URL is collected.

Are opening post details included?

Yes. The Actor requests opening post details for each topic and falls back to the topic listing data when the detail page does not provide them.

Why are some fields missing?

Steam does not expose every field for every topic. Empty values are removed from each dataset item instead of being saved as null values.

Can I run this Actor on a schedule?

Yes. Create an Apify schedule for hourly, daily, weekly, or custom recurring collections, depending on how often you need to monitor community feedback.

Is it legal to collect Steam Community data?

You are responsible for complying with Steam policies, applicable laws, privacy requirements, and any restrictions that apply to your intended use of the data.

Related Actors

• Steam Store Scraper 🎮 - Collect Steam game listings, prices, release details, platforms, and catalog metadata.
• Playstation Store Scraper - Collect comparable game catalog, pricing, sale, platform, and store data from PlayStation.

Support

For issues, feature requests, or reports about changed Steam discussion pages, use the Issues or support section on the Actor page in Apify Console.

Legal Notice

This Actor is intended for legitimate collection and analysis of publicly available Steam Community data. You are responsible for complying with Steam terms, applicable laws, privacy requirements, and any permissions required for your use of the collected data.