Samsung Galaxy Store Apps Scraper

Extract localized public Samsung Galaxy Store app metadata from package IDs or detail URLs. Get clean titles, descriptions, identifiers, icons, developer links, canonical URLs, locale alternates, Android deep links, and availability status without maintaining a custom parser.

Use the Actor for ASO research, app-catalog enrichment, localization audits, and recurring competitor checks. It accepts up to 100 known apps per run and exports one structured dataset row per app and requested locale.

This V1 focuses on reliable known-app enrichment. It does not claim Galaxy Store search, category crawling, rankings, download counts, ratings, or reviews.

What does Samsung Galaxy Store Apps Scraper do?

The Actor turns public Galaxy Store detail pages into structured records.

• 📱 Accept package IDs such as com.samsung.android.app.spage.
• 🔗 Accept galaxystore.samsung.com/detail/... URLs.
• 🌍 Request a language and country combination.
• 🧭 Discover canonical and hreflang alternate URLs.
• ✅ Distinguish available, fallback, and not-found results.
• 📦 Export JSON, CSV, Excel, XML, RSS, or JSONL through Apify datasets.

It uses server-rendered public metadata, so it does not need a browser, login, seller account, or API key.

Who is it for?

ASO and localization teams

Audit how known Samsung apps appear across markets and identify missing localizations. Track title or description changes in scheduled runs.

App-intelligence teams

Enrich a catalog of package IDs with Galaxy Store identifiers, icons, developer URLs, and deep links. Join the results with Google Play or Apple App Store datasets downstream.

Developers and data engineers

Replace fragile HTML parsing with an Actor API, webhook, schedule, or integration. Receive predictable typed records even when an app is unavailable.

Agencies and analysts

Monitor a fixed competitor list and deliver repeatable market snapshots to clients.

Why use this Galaxy Store extractor?

• Source-specific fields: retain Samsung package, store, locale, and deep-link semantics.
• Localized requests: control both language and three-letter country code.
• Explicit fallback: fallback records never falsely claim requested-market availability.
• Safe URL scope: URL inputs must point to a Galaxy Store app detail page.
• Batch workflow: process up to 100 unique known apps per run.
• Automation-ready: connect datasets to APIs, webhooks, schedules, or cloud storage.
• No authentication: extract only anonymous public metadata.

What data can you extract?

Field	Meaning
title	Localized public app title
description	Localized public app description
developerUrl	Developer website exposed by Galaxy Store
packageId	Normalized Android-style package identifier
storeId	Galaxy Store identifier
iconUrl	Public app icon URL
canonicalUrl	Canonical Galaxy Store detail URL
localeAlternates	`hreflang
androidDeepLink	samsungapps:// product detail deep link
status	available, fallback, or not_found
isAvailableInRequestedLocale	Whether the requested locale returned app metadata
requestedLocale	Requested language and country combination
resolvedLocale	Locale used for returned metadata
sourceUrl	Original normalized requested URL
fetchedUrl	URL that produced the final result
scrapedAt	ISO timestamp of extraction

How to scrape Samsung Galaxy Store apps

1. Open the Actor input page.
2. Add one or more package IDs or Galaxy Store detail URLs.
3. Choose a language code such as en_US or de_DE.
4. Choose a three-letter country code such as USA or DEU.
5. Keep fallback enabled if US English metadata is useful when a locale is unavailable.
6. Click Start.
7. Open the dataset to preview or download the app records.

The default input uses one deterministic Samsung package so a first run stays quick and inexpensive.

Input parameters

Galaxy Store package IDs

packageIds accepts up to 100 IDs. Package IDs must contain dot-separated letters, numbers, or underscores. Duplicates across IDs and URLs are removed before requests begin.

Galaxy Store detail URLs

startUrls accepts public URLs in this exact scope:

https://galaxystore.samsung.com/detail/com.samsung.android.app.spage

URLs from other hosts, catalog pages, or unrelated paths fail validation instead of silently changing product scope.

Localization

languageCode accepts forms such as en, en_US, ko_KR, and de_DE. countryCode uses Samsung's three-letter country values, for example USA, GBR, KOR, and DEU.

Fallback behavior

When fallbackToDefaultLocale is true and the requested page does not expose valid app metadata, the Actor tries one bounded en_US / USA request. A successful fallback has status: "fallback" and isAvailableInRequestedLocale: false.

Example input: package IDs

{
  "packageIds": [
    "com.samsung.android.app.spage",
    "com.samsung.android.game.gamehome"
  ],
  "languageCode": "en_US",
  "countryCode": "USA",
  "fallbackToDefaultLocale": true
}

Example input: detail URLs

{
  "startUrls": [
    {
      "url": "https://galaxystore.samsung.com/detail/com.android.samsung.utilityapp"
    }
  ],
  "languageCode": "de_DE",
  "countryCode": "DEU"
}

You may combine packageIds and startUrls in the same run.

Example output

{
  "title": "Samsung News",
  "description": "Get news from every angle...",
  "developerUrl": "https://www.samsung.com",
  "packageId": "com.samsung.android.app.spage",
  "storeId": "com.samsung.android.app.spage",
  "iconUrl": "https://img.samsungapps.com/productNew/...png",
  "canonicalUrl": "https://galaxystore.samsung.com/detail/com.samsung.android.app.spage",
  "androidDeepLink": "samsungapps://ProductDetail/com.samsung.android.app.spage?gsw_source=GSWebToDetail",
  "isAvailableInRequestedLocale": true,
  "status": "available",
  "requestedLanguageCode": "en_US",
  "requestedCountryCode": "USA",
  "requestedLocale": "en_US_USA",
  "resolvedLocale": "en_US_USA",
  "sourceUrl": "https://galaxystore.samsung.com/detail/com.samsung.android.app.spage?langCd=en_US&cntyCd=USA",
  "scrapedAt": "2026-07-18T00:00:00.000Z"
}

Optional metadata is omitted when Samsung does not expose it. Core status and request fields remain present.

How much does it cost to scrape Galaxy Store app metadata?

This Actor uses pay-per-event pricing:

• Start: a small one-time charge for each run.
• App record: one charge for each dataset row, including explicit not-found records.
• Volume discounts: lower per-record prices on higher Apify subscription tiers.

Current rates are a $0.005 start plus the following price per app record:

Apify tier	Price per app record
Free	$0.00022105
Bronze	$0.00019222
Silver	$0.00014993
Gold	$0.00011533
Platinum	$0.000076888
Diamond	$0.000053821

Keep known apps together in one batch to avoid repeated start fees. A one-app smoke test is the cheapest way to validate your workflow before scheduling a larger catalog.

Localization and availability semantics

available means Samsung returned valid app metadata for the requested language and country URL. fallback means that URL did not provide valid metadata, but US English did. not_found means neither the requested URL nor the enabled bounded fallback returned a matching app record.

The Actor validates Samsung's returned bundle ID against your requested package. A generic Galaxy Store error page is never emitted as a real app.

Tips for reliable app catalog audits

• 🧪 Begin with one package and the default locale.
• 🗺️ Use three-letter country codes, not two-letter codes.
• 🔁 Schedule identical inputs to detect metadata or availability changes.
• 🧩 Keep package IDs as your stable join key across app stores.
• 📊 Compare status and resolvedLocale, not title alone.
• 🛑 Disable fallback when you need strict requested-market availability only.
• 🐛 Enable debug only when troubleshooting because it saves raw HTML to the key-value store.

Integrations and automation workflows

Google Sheets and Excel

Schedule a package list, export the dataset as CSV or Excel, and compare localized columns between runs.

Webhooks and change alerts

Attach a run-finished webhook, fetch the dataset, and notify Slack or email when a package changes to not_found.

Data warehouses

Load JSONL into BigQuery, Snowflake, or a lakehouse and join by packageId and requestedLocale.

Multi-store app intelligence

Combine this Actor with Google Play and Apple App Store data in your own pipeline. Keep source-specific status fields while normalizing shared fields such as title, description, developer, and icon.

Use the Actor through the API

Replace <APIFY_TOKEN> with your Apify API token.

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/samsung-galaxy-store-apps-scraper').call({
  packageIds: ['com.samsung.android.app.spage'],
  languageCode: 'en_US',
  countryCode: 'USA',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient('<APIFY_TOKEN>')
run = client.actor('automation-lab/samsung-galaxy-store-apps-scraper').call(run_input={
    'packageIds': ['com.samsung.android.app.spage'],
    'languageCode': 'en_US',
    'countryCode': 'USA',
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

cURL

curl -X POST \
  'https://api.apify.com/v2/acts/automation-lab~samsung-galaxy-store-apps-scraper/runs?token=<APIFY_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"packageIds":["com.samsung.android.app.spage"],"languageCode":"en_US","countryCode":"USA"}'

Use with Apify MCP and AI assistants

Connect the Actor to Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/samsung-galaxy-store-apps-scraper"

For Claude Desktop, Cursor, or VS Code, add this MCP server configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/samsung-galaxy-store-apps-scraper"
    }
  }
}

Example prompts:

• “Extract US English metadata for these five Galaxy Store package IDs.”
• “Check whether these Samsung apps are available in Germany and return fallback status.”
• “Compare this week's Galaxy Store titles with my previous dataset.”

Scheduling a Galaxy Store monitor

Create an Apify schedule with your stable competitor package list. Send each completed dataset to your preferred integration or webhook. Store historical snapshots using the run ID and scrapedAt timestamp.

For strict regional checks, disable fallback and alert on not_found. For catalog enrichment, leave fallback enabled so your pipeline can still receive useful public metadata.

Error handling

Invalid package IDs and out-of-scope URLs fail fast with a clear message. Transient server or rate-limit failures use bounded retries. One failed request does not erase valid rows from other package IDs. If every app request fails at the transport or extraction layer, the run fails instead of reporting a false success.

A valid missing package is different: it produces a typed not_found row for downstream monitoring.

Is it legal to scrape Galaxy Store metadata?

The Actor extracts publicly accessible app metadata and does not bypass login or access private user data. You are responsible for your use case, request volume, contracts, and compliance with applicable laws and Samsung's terms. Do not use the output for spam, impersonation, or infringement. Avoid submitting personal data as input.

FAQ

Does this Actor search the whole Galaxy Store?

No. V1 enriches known package IDs and detail URLs. It does not promise unproven search, rankings, categories, or reviews.

Does it require a Samsung account or proxy?

No. The supported detail metadata is publicly available through anonymous HTTP responses.

Why did I get status: "fallback"?

The requested locale did not expose matching app metadata, while the bounded US English fallback did. Check isAvailableInRequestedLocale and resolvedLocale before using localized text.

Why did I get not_found for a real app?

The package may not be published in the requested country, may have moved, or may no longer be public. Try the default en_US / USA combination and confirm the package ID from a current Galaxy Store detail URL.

Can I submit Google Play URLs?

No. URL scope is enforced. Extract the package ID and submit it directly, or use a dedicated Google Play actor.

How many apps can one run process?

Up to 100 unique package IDs after deduplication. Use multiple scheduled runs for larger catalogs.

Related scrapers

Build a broader app-intelligence workflow with other automation-lab Actors:

• Google Play Store Scraper
• Apple App Store Scraper

Use this Actor when Samsung Galaxy Store locale and availability semantics matter. Use source-specific companion Actors for other stores rather than treating them as equivalent.

Support

If a current public Galaxy Store detail page produces an incorrect record, open an Actor issue with:

• the package ID or source URL,
• requested language and country,
• expected status or field,
• run ID,
• and a small output sample.

Do not include passwords, tokens, private account information, or unrelated personal data.