Tokopedia Catalog Monitor

We built Tokopedia Catalog Monitor to provide a straightforward way to query search listings, extract product and shop metadata, and track catalog changes. Instead of managing custom browser automation or coordinating proxies, you can use pre-built modes to retrieve structured results on-demand.

Whether you are performing market research, auditing competitor prices, or evaluating merchant inventory, this Actor delivers structured, nested datasets.

Unofficial Actor: This is an independent tool and is not affiliated with, authorized, or endorsed by Tokopedia.

---

From Discovery to Automated Monitoring

We designed this Actor to follow your natural workflow, helping you capture, inspect, and track catalog data in three stages. We keep the monitor deliberately focused on essential catalog changes, avoiding complex diff engines so you get clear, actionable outputs.

1. Discover products (discover)

Search by keyword to return matches in their exact search-page order, preserving source order and duplicate occurrences.

• Inputs: keyword (required), maxResults (optional, default: 20, range: 1–1000).
• Returned data: Product IDs, names, URLs, prices, discounts, ratings, review counts, sold counts, merchant locations, and available open, official, and Power Merchant flags.

2. Inspect a product (productDetail) or shop (shopDetail)

Extract targeted attributes from specific listings or shop profiles and listings.

• Inspect a product: Feed the Actor a product URL to retrieve description, categories, stock, availability, variant options, and paginated customer reviews with ratings, helpful counts, and seller replies when available.
  • Inputs: productUrl (required), maxReviews (optional, default: 20, range: 1–100).
• Inspect a shop: Extract merchant location, official level, products, and seller reviews.
  • Inputs: shopUrl (required), maxProducts (optional, default: 20, range: 1–1000), maxReviews (optional, default: 20, range: 1–100).
  • Note: Empty storefronts succeed with valid empty arrays.

3. Monitor selected products (monitor)

Track price, stock, availability, and variants over time.

• Creation: Initialize with 1–10 product URLs to generate a monitorId and record baseline revision 0 (contains current snapshots, an empty changes array, and no previous snapshot).
• Continuation: Run subsequent checks using only the monitorId to increment the revision and output comparisons.
• Change tags: Detected differences are flagged in the changes array as: product, availability, price, stock, or variants. (Detailed variant diffs are not provided).
• Robust error handling: Each product is checked independently. Successful scrapes output monitorObservation rows; failures output error rows (with no snapshot fields), preserving the product's last successful snapshot. If all products in the monitor fail, the run fails.
• Scheduling: Configure exclusive Apify Schedules with your monitorId; overlapping runs are not supported.

---

Quick Start

1. Click Try for free on the Actor page.
2. Set the Mode to Discover products.
3. Set the Search keyword to laptop.
4. Click Start.
5. View your results in the Dataset tab once the run finishes.

For your first run, use the prefilled discovery configuration:

{
  "mode": "discover",
  "keyword": "laptop"
}

---

URL Requirements

Input URLs must be public, direct links. Remove all query parameters (such as ?source=...) and hash fragments (such as #section):

• Product URLs (used in productDetail and monitor modes): Must have exactly two path segments after the domain: https://www.tokopedia.com/shop-name/product-slug
• Shop URLs (used in shopDetail mode): Must have exactly one path segment after the domain: https://www.tokopedia.com/shop-name

Path segments must use plain public characters. Modified or malformed URLs will be rejected by the input schema's strict validation rules.

---

Data Structure & Examples

Each dataset row represents a single Tokopedia record. Tabular exports like CSV or Excel will flatten or serialize nested structures, while JSON exports preserve their relationship.

Monitor Observation Snippet (monitor)

This is an abridged preview of selected fields, not a complete schema-valid Dataset row.

{
  "type": "monitorObservation",
  "monitorId": "7b0a9c75-cb30-47ea-fc0c-6d4220b36e14",
  "revision": 3,
  "productUrl": "https://www.tokopedia.com/tech-store/wireless-mouse-silent-2-4ghz",
  "changes": ["price", "stock"],
  "previous": {
    "productId": "11223344",
    "available": true,
    "price": 150000,
    "maxPrice": 150000,
    "stock": 42,
    "variants": []
  },
  "current": {
    "productId": "11223344",
    "available": true,
    "price": 145000,
    "maxPrice": 145000,
    "stock": 18,
    "variants": []
  }
}

---

Pricing & Proxies

Indonesian Residential Proxies

Requests are automatically routed through residential proxies configured for Indonesia to manage rate limits and request blocks. No user-side proxy configuration, credentials, or session settings are required. Note that proxy routing helps protect runs from immediate blocking but does not guarantee continuous source availability.

Pay-per-Event (PPE) Billing

Both platform compute and managed-proxy expenses are included in the Actor's price; you do not pay separate platform memory or run-time fees. You are billed based on successful operations using these five stable custom events:

• discover-product: Charged per product successfully saved during discover mode. If zero matches are found, you are not charged.
• product-detail: Charged once per saved productDetail aggregate row. Included customer reviews do not trigger additional charges.
• shop-detail: Charged once per saved shopDetail aggregate row (even if the shop product list is empty).
• shop-product: Charged per product successfully nested inside a saved shopDetail result.
• monitor-run: Charged once per monitor check that saves at least one successful product observation, regardless of how many of the 1–10 products succeeded.

Uncharged Operations: If an operation fails completely due to network or source errors, or if a monitor run fails for all monitored products, no custom events are charged.

Please check the Actor's Pricing tab for current PPE event rates.

---

Use with Apify MCP

If you integrate marketplace data into AI assistant workflows, you can connect this Actor to compatible clients (like Claude Desktop) using Apify's hosted Model Context Protocol (MCP) server:

https://mcp.apify.com?tools=crawlstone/tokopedia-catalog-monitor

Once connected, you can query keywords, retrieve shop inventories, or inspect products using natural language.

---

Frequently Asked Questions

What should I do when a discovery run returns zero rows?

This is normal and occurs when Tokopedia has no products matching your keyword. The run succeeds, but because no product rows are saved, the discover-product event is not charged.

Why do some monitor rows lack previous or current snapshots?

The baseline check (revision 0) records your initial product snapshots to compare against later, meaning it contains current data but lacks previous data and has an empty changes array. If a monitored product check fails on a subsequent run, the Actor writes an error row containing the failure message and target URL with no snapshot fields.

What happens when some products in a monitor run fail?

Monitoring handles each URL separately. If a single product check fails, its error row is saved, but its last successful snapshot remains intact in the durable state for future comparisons. The monitor check still charges one monitor-run event as long as at least one product produces an observation.

Can I monitor more than 10 products or modify the URL list?

No. A monitor ID supports a fixed, immutable set of 1–10 product URLs defined when it is created. To track a different list or monitor more products, run the Actor with your new list of productUrls to create a new monitorId.

Why are some fields missing from my results?

Tokopedia does not always return every metadata field for every product or shop. The Actor omits missing fields rather than outputting placeholders, but confirmed numeric zero values and boolean false flags are preserved.

---

Support

If you need help, please open a ticket on this Actor's Discussion tab and provide:

• Your Apify Run ID.
• The selected Mode and the Input values you provided.
• A description of what you expected versus what occurred.

Do not share your Apify API Token or other private credentials in support tickets.