Playstation Store Scraper

What does PlayStation Store Scraper do?

PlayStation Store Scraper collects structured game catalog data from public PlayStation Store browse pages, category pages, and search result URLs. Provide a PlayStation Store URL in startUrls, choose a result limit, and receive records with localized pricing, sale details, platform information, product identifiers, store links, and optional media URLs.

The Actor is useful for PlayStation price monitoring, game catalog creation, regional market research, sale discovery, and gaming content workflows. It supports PlayStation Store locales such as en-us, en-gb, and de-de, so each run can reflect the language and market represented by its starting URL.

Why use PlayStation Store Scraper?

• Track game prices - Compare base prices, discounted prices, discount labels, and free-to-play status across scheduled runs.
• Build a game catalog - Store titles, product and concept identifiers, platforms, categories, store URLs, and media references in a structured dataset.
• Research regional stores - Run the Actor with a locale-specific PlayStation Store URL to collect pricing and catalog data for a selected market.
• Find games by search term - Use a PlayStation Store search URL and keep the original searchTerm with each matching result.
• Collect media references - Include cover art, logos, screenshots, trailers, and media roles when includeMedia is enabled.
• Automate downstream workflows - Export the dataset to JSON, CSV, Excel, or XML, or connect it to Google Sheets, Airtable, webhooks, Make, Zapier, and the Apify API.

What data can you extract from PlayStation Store?

The output shape depends on the starting URL. Browse and category pages produce concept-level records. Search pages produce product-level records. Fields that the source does not provide are omitted from that item.

Field	Type	Description
source	String	Identifies whether the item came from a category or search run.
storeLocale	String	PlayStation Store locale taken from the input URL, such as en-us.
name	String	Game or product title.
url	String	Direct PlayStation Store concept or product URL.
basePrice	String	Regular displayed price when available.
discountedPrice	String	Current sale price when available.
discountText	String	Store discount label or savings text.
isFree	Boolean	Indicates whether the item is free.
includesBundleOffer	Boolean	Indicates whether a bundle offer is available.
isExclusive	Boolean	Indicates whether the item is marked as exclusive.
isTiedToSubscription	Boolean	Indicates whether the offer is tied to a subscription.
platforms	Array	Platform values returned for search products.
categoryId	String	Category identifier for browse or category results.
categoryReportingName	String	Reporting name for the source category.
searchTerm	String	Search phrase used for a search result item.
conceptId	String	PlayStation concept identifier for category results.
productId	String	PlayStation product identifier for search results.
npTitleId	String	NP title identifier when supplied for a search product.
productIds	Array	Product identifiers associated with a category concept.
skus	Array	SKU identifiers associated with a search product.
coverImage	String	Cover art URL when media collection is enabled.
logoImage	String	Game logo URL when available.
screenshots	Array	Screenshot URLs when available.
videos	Array	Trailer or video URLs when available.
mediaRoles	Array	Media role values found for the item.
serviceBranding	Array	Service branding values attached to the offer.
upsellServiceBranding	Array	Branding values related to an upsell offer.
upsellText	String	Upsell text supplied by the store.
scrapedAt	String	ISO timestamp for when the item was collected.

How to scrape PlayStation Store data

1. Open PlayStation Store Scraper in Apify Console.
2. Add one public browse, category, or search URL to startUrls.
3. Set maxGames and choose whether to include media URLs.
4. Configure Apify Proxy if the run is large or repeated frequently.
5. Start the run and review the dataset preview.
6. Download the results or connect the dataset to your next workflow.

The Actor uses the first URL in startUrls as the run target. Use one URL per run when you need separate locale, category, or search collections.

Input Parameters

Parameter	Type	Required	Default	Description
startUrls	Array	No	PlayStation browse page	List of PlayStation Store URL objects. Supports browse pages, category pages, and search result pages. The first URL determines the run.
maxGames	Integer	No	20	Maximum number of items to save. Use 0 for unlimited results. Accepted range is 0 to 10000.
includeMedia	Boolean	No	true	Include cover images, logos, screenshots, and video URLs when available.
proxyConfiguration	Object	No	{"useApifyProxy": false}	Optional proxy settings. Residential proxies are recommended for larger or repeated runs.

Usage Examples

Basic Browse Collection

Collect games from the US PlayStation Store browse page with a small test limit.

{
  "startUrls": [
    {
      "url": "https://store.playstation.com/en-us/pages/browse"
    }
  ],
  "maxGames": 20
}

Category Collection

Use a category URL to collect concept-level records from a specific PlayStation Store category.

{
  "startUrls": [
    {
      "url": "https://store.playstation.com/en-us/category/d0446d4b-dc9a-4f1e-86ec-651f099c9b29/1"
    }
  ],
  "maxGames": 100,
  "includeMedia": true
}

Search by Game Title

Use a URL-encoded search path to collect product-level results for a specific game or phrase.

{
  "startUrls": [
    {
      "url": "https://store.playstation.com/en-us/search/god%20of%20war"
    }
  ],
  "maxGames": 50,
  "includeMedia": false
}

Regional Price Collection

Run the same browse or search workflow separately with another locale when comparing regional catalog and price data.

{
  "startUrls": [
    {
      "url": "https://store.playstation.com/en-gb/search/elden%20ring"
    }
  ],
  "maxGames": 100,
  "includeMedia": false,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Sample Output

This example shows a category result with pricing, offer flags, identifiers, and media references. Actual fields vary by game and source page.

{
  "source": "category",
  "storeLocale": "en-us",
  "categoryId": "28c9c2b2-cecc-415c-9a08-482a605cb104",
  "categoryReportingName": "Browse",
  "conceptId": "10002363",
  "name": "Marvel's Spider-Man 2",
  "url": "https://store.playstation.com/en-us/concept/10002363",
  "basePrice": "$69.99",
  "discountedPrice": "$49.99",
  "discountText": "Save 29%",
  "isFree": false,
  "includesBundleOffer": false,
  "isExclusive": true,
  "isTiedToSubscription": false,
  "coverImage": "https://image.api.playstation.com/example-cover.jpg",
  "logoImage": "https://image.api.playstation.com/example-logo.png",
  "screenshots": [
    "https://image.api.playstation.com/example-screenshot-1.jpg"
  ],
  "videos": [
    "https://video.api.playstation.com/example-trailer.mp4"
  ],
  "mediaRoles": ["MASTER", "LOGO", "SCREENSHOT", "PREVIEW"],
  "productIds": ["UP9000-PPSA01411_00-SMTWOMARVELS0000"],
  "scrapedAt": "2026-08-09T10:30:00.000Z"
}

Tips for Best Results

• Start with a small limit - Test a browse, category, or search URL with maxGames set to 20 before collecting a larger catalog.
• Use the correct URL type - Browse and category URLs return concept records, while search URLs return product records.
• Keep locale consistent - Use the same locale in scheduled runs when you want comparable prices over time.
• Disable media for price checks - Set includeMedia to false when images and videos are not needed.
• Use 0 carefully - maxGames: 0 requests all available results and can create a large dataset.
• Review missing fields in context - Descriptions, ratings, genres, release dates, and other fields may not be present because this Actor returns the structured values exposed by the selected Store result type.
• Schedule repeat runs - Daily or weekly runs are useful for sale monitoring, while less frequent runs may be enough for catalog research.

Integrations and Export Formats

• Google Sheets - Review prices, discounts, and regional comparisons in a spreadsheet.
• Airtable - Build a searchable game catalog with media and store links.
• Webhooks - Send completed run notifications or dataset links to another service.
• Make and Zapier - Trigger alerts, database updates, or content workflows after a run.
• Apify API - Start runs and retrieve dataset items from your own application.

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

Frequently Asked Questions

Can I scrape PlayStation Store search results?

Yes. Put a PlayStation Store search URL such as /en-us/search/god%20of%20war in startUrls. Search records include fields such as productId, npTitleId, platforms, skus, and searchTerm when the Store provides them.

Can I collect a PlayStation Store category?

Yes. Use a browse URL or a category URL. Category results generally include conceptId, categoryId, categoryReportingName, and productIds when those values are available.

Can I compare PlayStation prices between countries?

Yes. Run separate collections with locale-specific URLs such as en-us, en-gb, or de-de, then compare the returned price strings and storeLocale values. Currency and available offers depend on the selected Store market.

Does startUrls process every URL I provide?

No. The Actor uses the first URL in the array as the run target. For separate regions or searches, run the Actor separately for each URL.

How do I collect only the pricing fields?

Set includeMedia to false and use a suitable maxGames value. Pricing and offer fields remain available, while media URL fields are omitted when they are not collected.

Why are some output fields missing?

Fields are omitted when the selected PlayStation Store result does not provide them. Category and search results also expose different identifiers and metadata, so their records are not identical.

Can I run this Actor on a schedule?

Yes. Create an Apify schedule for recurring price checks, sale monitoring, or catalog refreshes. Keep the same URL and locale when comparing results between runs.

Is PlayStation Store data real-time?

The dataset reflects the public Store data available when the run executes. Prices, discounts, availability, media, and catalog contents can change after a run completes.

Is it legal to collect PlayStation Store data?

You are responsible for complying with PlayStation Store terms, applicable laws, and privacy requirements. Collect only data you are permitted to use, respect access limits, and use the results responsibly.

Related Actors

• Steam Store Scraper - Collect comparable game catalog, pricing, platform, and media data from Steam.
• Steam Reviews Scraper - Add Steam Community discussion data to gaming research and feedback workflows.

Support

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

Legal Notice

This Actor is intended for legitimate collection of publicly available Store data. You are responsible for complying with PlayStation Store terms of service, applicable laws, access restrictions, and any licenses or permissions required for media and other collected data.