Tokopedia Catalog Monitor
Pricing
from $7.50 / 1,000 monitor runs
Tokopedia Catalog Monitor
Track changes in Tokopedia product prices, stock, availability, and variants across runs. Scrape keyword results, aggregate product details with reviews, and shop details with products and seller reviews—an unofficial Tokopedia scraper for catalog monitoring and marketplace analysis.
Pricing
from $7.50 / 1,000 monitor runs
Rating
0.0
(0)
Developer
Crawl Stone
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Find Tokopedia products, collect detailed product or shop information, and monitor prices, stock, availability, and variants over time.
Unofficial Actor: Tokopedia Catalog Monitor is an independent tool and is not affiliated with or endorsed by Tokopedia.
What can this Actor do?
- Search Tokopedia for products using a keyword.
- Get product details, variants, images, and customer reviews.
- Get shop information, products, and seller reviews.
- Monitor up to 10 products for price, stock, availability, and variant changes.
- Continue a monitor later using its saved monitor ID.
- Export results as JSON, CSV, Excel, and other Apify Dataset formats.
- Manage the required Indonesian residential proxy automatically with no proxy setup.
Quick start
- Click Try for free on the Actor page.
- Choose what you want to do.
- Enter a keyword, product URL, shop URL, or monitor ID.
- Click Save & Start.
- Open the Output tab when the run finishes.
For your first run, try discovering products:
{"mode": "discover","keyword": "wireless mouse","maxResults": 20}
The Actor saves one result for each product found, up to your selected limit. If Tokopedia returns no matching products, the run still succeeds with an empty Dataset.
Choose a mode
| Mode | Use it for | Required input | Results |
|---|---|---|---|
discover | Search for products | keyword | One result per product found |
productDetail | Inspect one product | productUrl | One product with variants and customer reviews |
shopDetail | Inspect one shop | shopUrl | One shop with products and seller reviews |
monitor | Track products over time | New monitor: productUrls; existing monitor: monitorId | One observation per checked product |
The Store form starts with Discover products and the sample keyword laptop, so its prefilled input is ready to run. Fill in only the fields needed for your chosen mode.
Input fields
| Field | Used by | What to enter |
|---|---|---|
mode | Every run | discover, productDetail, shopDetail, or monitor |
keyword | discover | One non-empty Tokopedia search term |
maxResults | discover | Optional result limit from 1 to 1,000; default 20 |
productUrl | productDetail | One public Tokopedia product URL |
shopUrl | shopDetail | One public Tokopedia shop URL |
productUrls | New monitor | 1–10 unique public Tokopedia product URLs |
monitorId | Existing monitor | The monitor ID returned by an earlier run |
maxProducts | shopDetail | Optional product limit from 1 to 1,000; default 20 |
maxReviews | productDetail, shopDetail | Optional review limit from 1 to 100; default 20 |
Use normal public URLs from www.tokopedia.com. Product and shop URLs should not contain query parameters or fragments such as ?source=... or #section.
Input examples
Discover products
{"mode": "discover","keyword": "laptop stand","maxResults": 50}
Products remain in the order returned by Tokopedia. If the same product appears more than once in the search results, each occurrence is kept.
Get product details
{"mode": "productDetail","productUrl": "https://www.tokopedia.com/example-shop/example-product","maxReviews": 20}
The result can include:
- product name, URL, image, price, discount, rating, review count, and sold count;
- description, SKU, categories, images, stock, and availability;
- shop information;
- product variants and options;
- customer reviews, media, helpful counts, and seller replies.
If the product is identifiable but no longer available, the Actor can still return its available public information.
Get shop details
{"mode": "shopDetail","shopUrl": "https://www.tokopedia.com/example-shop","maxProducts": 20,"maxReviews": 20}
The result can include:
- shop name, URL, location, and merchant status;
- products from the shop;
- seller reviews and the products they refer to.
A shop with no returned products or reviews still produces one valid result with empty lists.
Monitor products over time
Monitoring is useful for price tracking, stock alerts, availability checks, and catalog-change workflows.
Create a monitor
Start with 1–10 product URLs:
{"mode": "monitor","productUrls": ["https://www.tokopedia.com/example-shop/example-product","https://www.tokopedia.com/another-shop/another-product"]}
The first successful run creates a monitor and returns a monitorId. Save this ID—you will use it for every later check.
The first observation is a baseline. It records the current product information but does not report changes yet.
Continue a monitor
Run the Actor again with the saved ID:
{"mode": "monitor","monitorId": "123e4567-e89b-42d3-a456-426614174000"}
Each continuation compares the newest information with the previous successful observation. A result can report changes to:
- product identity;
- availability;
- price;
- stock;
- variants.
The product URL list is fixed when the monitor is created. To track a different set of products, create a new monitor.
Schedule regular checks
Use an Apify Schedule or Task to run the same monitorId hourly, daily, or at another interval.
Do not run the same monitor more than once at the same time. Use one schedule or workflow per monitor and avoid overlapping manual runs.
Monitor data is stored in the named tokpedmon-state Key-value store. Deleting the corresponding monitor-<monitorId> record permanently removes that monitor.
Understanding the results
Results are saved in the run's default Dataset. The Output tab provides separate views for Monitor, Discover, Product detail, and Shop detail.
| Mode | Number of results | What each result contains |
|---|---|---|
discover | Zero to maxResults | Product information and its shop |
productDetail | One | Product details with variants and customer reviews |
shopDetail | One | Shop details with products and seller reviews |
monitor | One per checked product | Current observation, previous observation when available, and detected changes |
Detailed information remains grouped naturally:
- a product keeps its shop and variants together;
- product details keep customer reviews with the product;
- shop details keep products and seller reviews with the shop;
- monitor results keep previous and current observations together.
This makes the JSON output easy to use from applications while still allowing downloads in other Dataset formats.
Some fields are optional because Tokopedia does not always provide them. Missing information is left out. Confirmed values such as zero stock, zero reviews, or false merchant flags are preserved.
Empty results, partial monitoring, and errors
An empty Dataset can be a valid result when a discovery keyword has no matches. Empty discovery runs are not charged.
Product and shop detail runs are complete-or-fail. If the Actor cannot collect all requested information, it saves one error result when possible, marks the run as failed, and does not charge for the failed result.
Monitoring handles each product separately:
- if some products succeed, their observations are saved together with error results for failed products;
- failed products keep their previous successful monitor information;
- if every product fails, the run is marked as failed, the monitor is left unchanged, and the run is not charged.
An error result includes a readable message and may include the affected URL and monitor ID. Source availability can change, so retrying later may resolve temporary failures.
Use with Apify MCP
You can use Tokopedia Catalog Monitor from MCP-compatible AI clients through Apify's hosted MCP server:
https://mcp.apify.com?tools=crawlstone/tokopedia-catalog-monitor
Connect your Apify account using OAuth or an API token, then send the same inputs used in the Store form. For example:
{"mode": "discover","keyword": "mechanical keyboard","maxResults": 10}
For monitoring, create the monitor once, keep the returned monitorId, and use that ID in later MCP requests. See the Apify MCP documentation for setup instructions.
Managed proxy
You do not need to configure or supply a separate proxy. The Actor automatically uses a managed Indonesian residential proxy for Tokopedia requests. Proxy usage is included in the Actor price, and there are no proxy settings to configure.
Pricing
You pay only for successfully saved results. The Actor uses these billing events:
discover-product— charged for each product saved bydiscover. If no products are found, this event is not charged.product-detail— charged once when a completeproductDetailresult is saved. Included customer reviews do not create an additional charge.shop-detail— charged once when a completeshopDetailresult is saved, including when the shop has no returned products.shop-product— charged for each product included in a savedshopDetailresult. It is not charged when the returned product list is empty.monitor-run— charged once when a monitor run saves at least one successful product observation, regardless of how many configured products succeeded.
Error results are free. Failed product or shop detail runs are not charged. A monitor run where every product fails is also free and leaves the previous monitor information unchanged.
Platform and managed proxy usage are included in the Actor price. Check the Actor's Pricing tab for current rates and plan pricing. Standard Apify storage costs may still apply if you access or retain data after the run.
Frequently asked questions
Can I monitor more than 10 products?
One monitor supports up to 10 products. Create additional monitors if you need to track more products.
Can I add or remove products from an existing monitor?
No. A monitor keeps the product list used when it was created. Create a new monitor for a different list.
How often can I check a monitor?
You can use an Apify Schedule at the interval that suits your workflow. Leave enough time for one run to finish before the next starts, because overlapping runs for the same monitor are not supported.
Why does the first monitor run show no changes?
The first run creates the baseline used for later comparisons. Changes can only be detected after another successful run.
Why is a field missing from a result?
Tokopedia does not always provide every value. Unknown values are omitted rather than guessed. Confirmed zero and false values remain in the result.
Why did I receive an error result?
Tokopedia may have returned an unavailable page, blocked a request, changed its response, or temporarily failed. Read the result's message for details and try again later when appropriate. Failed one-shot results and all-product monitor failures are not charged.
Can I use the Actor from my application?
Yes. Open the API tab on the Actor page to copy a request for your preferred language. You can also use webhooks, schedules, integrations, or Apify MCP.
Privacy and responsible use
The Actor processes public Tokopedia pages and uses your Apify run input and storage. Do not include passwords, tokens, private customer information, or other secrets in the input.
You are responsible for your inputs, stored results, retention settings, compliance with applicable laws and platform terms, and how the collected data is used.
Support
If you need help, contact support from this Actor's Apify Store page and include:
- the Apify run ID;
- the selected mode;
- the keyword, product URL, shop URL, or monitor ID involved;
- the error message, if available;
- what you expected and what happened.
Never send your Apify API token, proxy credentials, or other secrets.