🛒 Lelong Malaysia Scraper: Product Price Monitor

Marketplace monitoring suite Collect focused public marketplace signals with bounded runs and safer change tracking.
Mourjan classifieds Multi-category public listings	YallaMotor cars Private-beta access validation	Lelong Malaysia ➜ You are here

Build a current Malaysia product-price view without copying catalog pages by hand. Collect genuine public Lelong product IDs, MYR prices, stock, seller, shipping, image, and change fields for resellers, analysts, and catalog workflows.

🧾 Real product rows Keep public product IDs, titles, prices, and currencies instead of a list of navigation links.

🏷️ Variant-safe prices Each visible variant keeps its own identity and price when the source provides both.

📦 Seller and shipping Retain public seller and destination-specific shipping context when it is available.

🔄 Focused changes Reuse a monitor key to emit new, price, availability, update, and safe-removal events.

Lelong Malaysia Scraper turns public Lelong Malaysia product pages, category pages, and keyword results into structured marketplace records. It is designed for price checks, seller comparisons, product research, and recurring catalog monitoring without treating missing values as made-up data.

🔎 What this Actor does

Choose one source mode at a time: keyword search, category URLs, or direct product URLs. The Actor follows only the selected scope, enforces a total item cap across every source, and produces data fields only when the public page supplies them.

A verified Cloud run returned real product records rather than site-navigation links, including product ID, MYR price, stock, seller, and shipping fields. Product details are optional, while public contacts stay off unless you explicitly request them.

👥 Who is this for?

• I am a Malaysia reseller who needs a clean view of comparable products, prices, stock, and sellers before I update an offer.
• I am a catalog or market analyst who needs dated, source-linked product records for a spreadsheet, database, or dashboard.
• I am an automation builder who wants a focused change feed for Google Sheets, Airtable, n8n, or a custom workflow.
• I am a sourcing team member who needs variants to remain separate so a cheap option does not overwrite the parent product price.

🧭 How it works

CHOOSE SOURCES Start with one useful scope Enter keywords, public category URLs, or known product URLs.

SET COLLECTION Keep the run focused Choose detail depth, a total item limit, and polite request pacing.

USE OR MONITOR Export current records or changes Reuse a stable monitor key when you want later price or availability updates.

{
    "sourceMode": "keywordSearch",
    "keywords": ["toyota vios"],
    "detailLevel": "productDetails",
    "maxItems": 50,
    "maxPagesPerSource": 3
}

⚙️ Input

Field	Type	When to use it	What it controls
sourceMode	enum	Every run	Choose keywordSearch, categoryUrls, or productUrls. Do not mix modes.
keywords	array of text	Keyword search	Add one to five product terms.
categoryUrls, productUrls	array of URLs	URL modes	Add one to twenty public Lelong category or product pages.
category, minPrice, maxPrice, condition, sellerType, sortOrder	text, number, or enum	Keyword search	Narrow the public search results when the source supports the value.
detailLevel, includeVariants, reviewDetailLevel	enum or boolean	Any run	Choose product-page depth, variant rows, and public review detail.
deliveryPostcode, includeContacts	text or boolean	Optional enrichment	Request destination shipping context or explicitly allow public contacts. Contacts default to off.
blockedResponsePolicy	enum	Source reliability	Keep a blocked or failed source incomplete so it cannot create a false removal.
maxItems, maxPagesPerSource, maxDetailPages, maxConcurrency, requestDelayMs	integer	Every run	Keep collection finite. maxItems is the total cap across all selected sources.
runMode, monitorKey, emitUnchanged	enum, text, or boolean	Recurring checks	Use changes with one stable monitor key. A monitor key is required in changes mode.

📦 Output

Each real product or variant is a separate record. Stable source IDs are preferred; a canonical URL is an explicitly labeled fallback. The Actor omits missing values rather than filling them with placeholders.

{
    "recordType": "product",
    "sourceId": "221826664",
    "productId": "221826664",
    "title": "Arospeed Anti-Heat Coated TOYOTA VIOS 07 Air Ram System",
    "price": 368,
    "currency": "MYR",
    "availability": "InStock",
    "stock": 20,
    "seller": {
        "name": "AUTOBAGS"
    }
}

Fields	What they mean
sourceId, identityType, productId, variantId, canonicalUrl, sourceUrl	Public identity and source context.
title, description, sku, category, brand, model, condition	Product details when publicly shown.
price, listPrice, discount, currency	Observed product-price context.
availability, stock, variants, images, reviews	Public stock, variant, image, and review information when present.
seller, shipping, viewCount, soldCount	Public seller, delivery, and marketplace signals when present.
status, changeType, changes, observedAt, firstSeenAt, lastSeenAt	Current status and scoped monitoring history.

🗂️ Dataset views

The dataset keeps three focused views—no hidden fourth view or diagnostic export.

View	Use it for
overview — Product Overview	A compact product, price, availability, seller, URL, and observed-time table.
pricing — Commerce Details	Product IDs, variants, pricing, seller, shipping, and product media.
monitoring — Monitoring Changes	New, updated, price, availability, and safe-removal events.

💰 Pricing

Pricing is pay per result. Empty runs cost nothing, and there are no subscriptions. Keep the limits close to the amount of public marketplace data you actually need.

⭐ Did this save you a manual catalog check?

A rating helps other Malaysia marketplace teams find structured product data. Tell them which product, price, stock, or change workflow made the Actor useful.

★ Rate this Actor on Apify

🧠 Tips and limitations

• Use the same monitor key only for the same source scope. Changing the sources creates a different monitoring question.
• Shipping is returned only when a public page supports the requested postcode.
• Variant prices stay on their own records. They are never promoted to the parent product.
• A blocked or incomplete source is unknown, not a removal.
• This independent tool collects public information only. Use it in line with Lelong Malaysia's terms and applicable law.

❓ FAQ

Does it return product data or just links?

It returns product records. A current verified Cloud run produced public product IDs, MYR prices, stock, seller, shipping, and source fields rather than navigation links.

How do price and availability monitoring work?

Run a snapshot first. Then choose changes, keep the same source scope, and reuse the same monitor key. Unchanged active records stay out of the output unless you enable emitUnchanged.

Are public contacts included automatically?

No. includeContacts defaults to false. When you enable it, only source-published public contact values may be returned.

Can I collect the full Lelong catalog in one run?

No. Use focused keywords, category URLs, or known product URLs. The finite limits keep each run predictable and prevent one broad request from becoming an unbounded crawl.

🔗 Other actors

• Mourjan classifieds scraper and monitor ↗ — Public listings across property, cars, jobs, and services.
• Mahally Scraper ↗ — Products, stores, and specials from Mahally.
• Mahally Price Monitor ↗ — Track public product price movement in Saudi Arabia.
• Trendyol Price Monitor ↗ — Watch public Turkish product price and stock signals.