PlayStation Store Scraper — Games & Prices

Scrape public PlayStation Store catalog, category, search, concept, and product pages into clean game records. It is for game-market researchers, price trackers, catalog builders, and AI agents that need public Store pricing and metadata without a PlayStation account. It returns one validated record per game with its Store URL, current and original price, discount, availability label, platforms, artwork, and public description when available.

Use this actor for the digital PlayStation Store. Do not use it for consoles, controllers, accessories, or inventory from PlayStation Direct, and do not expect sign-in-only PlayStation Plus member prices, checkout data, user libraries, or private account information.

What data does it extract?

Each dataset item has a stable, agent-friendly shape:

Field	Description
gameId, title, productUrl	Store concept/product identifier, displayed title, and direct Store page
storefront	Store locale used to retrieve the public listing, such as en-us
currentPrice, currentPriceText, currency	Visible current price in both normalized and displayed forms
originalPrice, discountPercent, isOnSale	Pre-sale price and calculated promotion information when the Store provides it
isFree, availability, productType	Free/included status plus labels such as Pre-order, Game trial, or PlayStation Plus
platforms, description, imageUrl	Public platform labels, description, and artwork when available
sourceUrl, scrapedAt	Discovery page or direct input URL and the ISO-8601 extraction time

The actor never adds diagnostic rows to the dataset. Instead, every run writes compact OUTPUT and detailed RUN_SUMMARY JSON records in the default key-value store, so downstream workflows can distinguish a complete run, partial data, a valid empty response, invalid input, and an upstream outage.

When should I use it?

Use it to build a game catalog from a public browse/category page, collect a targeted list from a Store search URL, monitor displayed pricing on a list of direct concept URLs, or export Store metadata into your own analytics workflow. Pass the specific PlayStation Store URLs you care about when you need a focused result set. Leave Start URLs blank to begin from the selected storefront's Browse page.

For a fast listing-only export, set enrichDetails to false. For the fuller public detail-page data, leave it enabled. This two-stage approach retrieves catalog tiles first and then enriches discovered games from their concept/product pages while respecting the maximum result cap.

Input

Only six inputs are exposed, with safe defaults:

Input	Default	Purpose
startUrls	Selected storefront Browse page	Public PlayStation Store browse, category, search, concept, or product URLs
storefront	en-us	Default Browse locale if no URL is supplied
maxResults	20	Maximum persisted and billable game records, from 1 to 100
maxListingPages	1	Maximum numbered Browse pages to follow, from 1 to 10
enrichDetails	true	Visit direct game pages for description and fuller public metadata
useResidentialProxy	false	Enable Apify Residential Proxy only if direct Store access is blocked

Browse-page example

{
  "storefront": "en-us",
  "maxResults": 20,
  "maxListingPages": 1,
  "enrichDetails": true
}

Direct-game URL example

{
  "startUrls": [
    { "url": "https://store.playstation.com/en-us/concept/10017658" }
  ],
  "maxResults": 1,
  "enrichDetails": true,
  "useResidentialProxy": true
}

Output

The following is representative output; values depend on the selected Store locale and public page state.

{
  "gameId": "10017658",
  "title": "Call of Duty®: Black Ops II",
  "productUrl": "https://store.playstation.com/en-us/concept/10017658",
  "storefront": "en-us",
  "currentPrice": 19.99,
  "currentPriceText": "$19.99",
  "originalPrice": 39.99,
  "originalPriceText": "$39.99",
  "currency": "USD",
  "discountPercent": 50,
  "isFree": false,
  "isOnSale": true,
  "availability": null,
  "productType": null,
  "platforms": ["PS5", "PS4"],
  "description": "A public Store description when available.",
  "imageUrl": "https://image.api.playstation.com/example.png",
  "sourceUrl": "https://store.playstation.com/en-us/pages/browse",
  "scrapedAt": "2026-07-14T12:00:00.000Z"
}

Use the games view for spreadsheet-style output. AI agents should page the dataset through Apify's get-actor-output capability when the run returns more than the preview. OUTPUT contains the terminal outcome and charged-event count; RUN_SUMMARY adds processed-page counts and safe warnings.

Pricing

This actor uses Pay per event + usage. A game event is charged only after a complete game record passes validation and is stored in the dataset. No record is charged before it is persisted.

Event	Price	Trigger
Actor start	$0.00005	Once per run
Game scraped	$0.003	One complete, persisted game record

Platform compute and proxy usage are additional and passed through by Apify. The actor logs the maximum event charge before collecting data: 20 games cost at most $0.060 in game events plus the start event and platform usage. maxResults is also a hard guard against writing or charging beyond your intended cap.

API usage

Run the private actor from JavaScript after deploying it to your Apify account:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('khadinakbar/playstation-store-scraper').call({
  startUrls: [{ url: 'https://store.playstation.com/en-us/pages/browse' }],
  maxResults: 10,
  enrichDetails: true,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Reliability and limits

The Store currently returns catalog tiles as server-rendered HTML while deeper catalog content is served by PlayStation infrastructure that can change without notice. The actor uses low concurrency, retries, page-level warnings, optional detail enrichment, and optional residential routing to keep runs predictable. A temporary partial scrape succeeds with the data that was safely persisted; a target outage with no usable data is reported honestly as UPSTREAM_FAILED.

Only public, anonymous Store data is collected. Storefront prices, availability, promotions, and descriptions can differ by country, account, age gating, or time. The actor does not infer hidden prices and does not crawl private account data. Use small, focused URL batches when monitoring pricing, especially during large Store promotions.

FAQ

How many results can I scrape with PlayStation Store Scraper?

Set maxResults from 1 through 100. The default is 20, and the actor never intentionally persists or charges more game records than this limit.

Can I integrate PlayStation Store Scraper with other apps?

Yes. Dataset records export through the Apify API in JSON, CSV, Excel, and other supported formats, and they can be consumed by your own analytics, alerting, or database workflow.

Can I use PlayStation Store Scraper with the Apify API?

Yes. Use an Actor API call with direct Store URLs or a storefront/default Browse input, then retrieve its default dataset and OUTPUT record.

Can I use PlayStation Store Scraper through an MCP Server?

Yes. It is designed for Apify MCP discovery and returns a flat, consistent dataset shape. Use it for public game catalog and pricing extraction, not account, trophy, social, or PlayStation Direct data.

Do I need proxies to scrape PlayStation Store data?

Direct access is the low-cost default for public catalog pages. If a run receives Store blocking or repeated 403/429 errors, enable Residential Proxy and retry with a small URL batch.

Is it legal to scrape PlayStation Store data?

You are responsible for ensuring your use complies with applicable law, PlayStation's terms, and any data-use restrictions. This actor is limited to public pages and must not be used to access accounts, circumvent authentication, or collect private data.

Your feedback

If a Store page exposes a public field that is not returned consistently, include the exact public URL, storefront, and expected field in an issue so it can be reproduced and tested.