Epic Games Store Scraper
Pricing
Pay per usage
Epic Games Store Scraper
Scrape Epic Games Store offers, free games, deals, releases, demos, coming soon titles, and catalog update metadata with normalized prices and URLs.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Newbs
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 hours ago
Last modified
Categories
Share
Scrape Epic Games Store offers, free games, deals, releases, demos, coming soon titles, and catalog update metadata. The actor returns normalized game, price, discount, image, and URL data for storefront monitoring and promotion tracking.
What it can scrape
- Epic Games Store catalog search and offers.
- Free games and active promotions from Epic and EGData promotion sources.
- Discounted games and current deals from EGData discounted offer data.
- New release, demo, and coming soon discovery signals.
- Public offer changelog entries through EGData when available; metadata timestamps are used as a fallback.
Useful inputs
mode:search,new_releases,deals,demos,coming_soon, orupdates.query: game title or catalog search text.category: Epic tag, namespace, or genre-style filter such asaction,strategy, orrpg.gameId: Epic offer ID for update checks.gameUrl: Epic 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. Official Epic promotion and GraphQL rows are high confidence; EGData catalog/changelog rows are medium confidence; metadata-only fallback rows are low confidence.
Billing result definition
One result is one normalized Epic Games Store offer, promotion, release, demo, coming-soon, 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.
Example inputs
{ "mode": "deals", "maxItems": 10 }
{ "mode": "updates", "query": "Fortnite", "maxItems": 5 }