1688 Product Listings & Price Extractor

Search 1688 by product keyword and return structured product listings with price, seller, MOQ, sales, supplier history, tags and offer URL for sourcing, research and automation.

Business use and first result

For: Buyers researching public 1688 wholesale listings and initial supplier options.

Why run it: Search a specific product keyword and retrieve structured product IDs, source URLs, available prices, minimum order quantities and seller identifiers.

First result: Run the LED灯 example below, open a returned offerUrl, and inspect priceCny, minOrderQuantity, monthlySales and sellerLoginId where present. Use Chinese keywords when possible.

Scope: This is public listing search, not full product-page detail extraction, automatic translation or verified supplier due diligence.

Why use this Actor

Buyers need direct structured 1688 product, price and supplier fields without manually browsing wholesale search pages or first running an intelligence workflow.

Key features

• Buyer-native inputs aligned to 1688 product scraper.
• Predictable structured output in the default Apify Dataset.
• Pay Per Event pricing tied to measurable result rows or reports.
• Optional MCP connector delivery for downstream automation and AI agents.

Quick start

Start with this working example and replace the target values with your own:

{
  "queries": [
    "LED灯"
  ],
  "maxResultsPerQuery": 10,
  "minMonthlySales": 0,
  "maxPriceCny": 0
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

• queries — Product keywords: Wholesale product keywords. Chinese terms usually improve matching.
• maxResultsPerQuery — Results per query: Maximum product listings returned per keyword.
• minMonthlySales — Minimum monthly sales: Optional minimum observed monthly sales filter.
• maxPriceCny — Maximum price CNY: Optional price ceiling. 0 disables the filter.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

Each Dataset item is a 1688 listing with offerId, title, priceCny, minOrderQuantity, sellerLoginId and offerUrl where available. The Output tab links the rows as results and run diagnostics as summary.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.001200 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

• Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
• Use the Actor from API or schedules for recurring collection, comparison or monitoring.
• Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
• Export successive Datasets for comparison outside this Actor; previousSnapshot is not a supported input.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

• Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
• Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
• Analytical outputs depend on the quality and coverage of the supplied or collected source data.
• Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

What it does

This Actor is the direct SOURCE layer for 1688 product research. It extracts public product-search data first. Downstream sourcing intelligence can then score or compare those rows separately.

Input

• queries: one or more product keywords
• maxResultsPerQuery: product rows per keyword
• minMonthlySales: optional demand filter
• maxPriceCny: optional price ceiling

Chinese search terms usually improve 1688 matching.

Output

Each Dataset row can include search query, offer ID, title, seller login ID, member ID, price in CNY, monthly and total sales, MOQ, supplier years, delivery hours, public tags, offer URL and scrape timestamp.

Quick start

Use the default example with LED灯 or provide one buyer-native product keyword. No upstream Dataset is required.

Use cases

• wholesale product research
• procurement and factory sourcing
• dropshipping discovery
• price and MOQ comparison
• recurring 1688 product snapshots
• AI-agent product retrieval

Pricing

Pay Per Event. The primary event is one normalized 1688 product listing row.

Automation and AI

The Actor supports optional MCP connector delivery for compatible downstream tools and AI-agent workflows.

Limitations

1688 anti-bot behavior can vary. The Actor tries direct MTOP access, then managed proxy fallbacks. Public fields vary by listing, and unavailable values are left empty rather than invented.