Pull any Steam store page into structured JSON: title, current and historical price, discount, review score, tags, system requirements, and concurrent player counts.
Steam is the largest PC gaming marketplace, where prices swing through seasonal sales and player interest spikes around launches and updates. The Steam Scraper API resolves store pages, price history, review breakdowns, and live concurrent-player figures into validated JSON keyed to app ID.
It powers price-tracking sites, games-market analysts, and publishers watching how a title performs after a sale or patch. Discounts and player counts are read at request time, and the positive-versus-negative review split is returned alongside recent and all-time scores.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.steam.com/",
"type": "app",
"geo": "us"
}'
// ← response
{
"status": "ok",
"data": {
"title": "...",
"developer": "...",
"rating": 4.7,
"ratings_count": 184220,
"price": "Free",
"category": "Productivity",
"rank": 12
}
} "type": "app",
"geo": "us"Steam data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
Game price-history and sale tracking
Concurrent-player and engagement monitoring
Review-score and sentiment analysis
Tag, genre, and wishlist market research
Yes. Each game response includes the current concurrent-player figure and the 24-hour peak, so you can chart engagement around launches, patches, and sales.
We return the current price, active discount, and base price at request time; collected on a schedule, those snapshots build a full price-history series per region.
Structured JSON straight from the API, or pushed to your stack natively — S3, BigQuery, Snowflake, Postgres, Kafka, or any HTTPS webhook. Call it from Python, Node, Go, Rust, or any HTTP client. The data lands where your pipeline already lives.
No. You pay for valid, schema-passing rows only. Retries, blocks, CAPTCHAs, and 5xxs are on us. If a run doesn't return data that conforms to the schema, it isn't billed.
Every request routes through the same engine behind our Web Unblocker API: compliant residential IPs, real browser fingerprints, TLS-level evasion, behaviour modelling, and built-in CAPTCHA solving. Hard targets become routine.
Yes. We respect robots policies, rate budgets, and ToS-aware allow/deny lists. We deliver and move on — no row-level retention beyond your replay window. GDPR DPA, PII redaction, and custom data residency available on request.