1688 Pet Supplies Scraper — China Wholesale Market Research
Pricing
from $4.50 / 1,000 products
Find profitable pet products to dropship from China's largest wholesale platform. Get English titles, dropship-ready scores, estimated landed costs, and compliance hints — all in one API call.
Version history and upgrade guidance. For current usage, see README.md.
Documentation-only release; no code, input, output or billing changes.
run-sync-get-dataset-items endpoint, ?timeout=900 guidance for
larger orders and 408 polling recovery — same shape as the image-search
Actor's section.Token-cache plumbing only; no input, output or pipeline-behaviour changes.
MTOP_KV_API_TOKEN + MTOP_KV_STORE_ID) are present, get() reads the
minter-published warm token from the shared KV store via the Apify REST
API BEFORE the SDK path. A fresh (<25 min) entry is used as-is
(shared-cache: hit); any failure silently degrades to the existing
SDK/bootstrap path (shared-cache: miss). Works for external users too,
whose SDK cannot see the owner's named store.shared-cache: hit/miss only; scrubSecret helper).tests/shared-cache-228.test.js (hit / miss / degrade /
flywheel / pool_health isolation / token-never-leaks).Billing-model change (platform pricing update + settlement code); no input, output or pipeline-behaviour changes.
return false before buffering).run-base-fee event ($0.01): charged once at run completion, and
only when the run delivered at least one row. Zero-row runs stay $0.
Settled after ALL flushes (settleRunBaseFee, both keyword and offerIds
paths), guarded by try/catch — a charge failure logs a warning and never
fails the run.pricePer1000 now $4.5 and estimatedCost uses
the real v2 arithmetic (max($0.04, rows × $0.0045 + $0.01)); new
runBaseFee block reports the delivered count and settlement result.Billing + docs-only change (no code, input or output changes):
pricingInfos record; price history preserved (append-only).apify-actor-start never charged).Docs-only change, no input/output/billing changes:
crawleast/1688-image-search-scraper)
with the recommended pipeline: discover by keyword (this Actor) →
source by photo (Image Search Scraper) → re-check finalists via its
offerIds detail-only mode. The Store link resolves once Actor 2
passes its W4 publication gate.No input or output data changes. Operations-review fix batch on top of 0.4.6:
0 results → $0.00 row to the price table and a "Run outcomes" section documenting the three run endings (products delivered / zero results / empty input NO_INPUT) and where errorCode lives (SUMMARY and OUTPUT key-value records).estimatedCost: "$0.00" instead of "$0.04" — the minimum-charge floor only fires when ≥1 product is delivered (cloud-verified in 0.4.6: zero-event runs charge exactly $0). Aligned with the NO_INPUT path.No input or output data changes for normal runs. Billing-fairness batch:
estimatedCost arithmetic updated to match.keywords and offerIds are empty/blank, the run now finishes SUCCEEDED with errorCode: "NO_INPUT" written to the SUMMARY and OUTPUT key-value records (previously a FAILED run). Nothing is researched and no per-product events are charged, so a misfired run costs nothing beyond the platform's treatment of zero-event runs.{"keywords": ["dog leash"], "maxResults": 5}) instead of the template placeholder.No input or output data changes. Added the Actor-level output schema (.actor/output_schema.json, mounted via the output key in actor.json) that the Apify Store publishing gate requires on top of the dataset and key-value store schemas: it exposes the product dataset (results) and the SUMMARY report (runSummary) as named run outputs with direct API links. Delivered rows and SUMMARY content are unchanged from 0.4.4.
No input or output data changes. Added a key-value store schema (.actor/key_value_store_schema.json) declaring the run's SUMMARY record as a typed collection (application/json), completing the Apify Store publishing "Output schema" requirement alongside the dataset schema added in 0.4.3. Delivered rows and the SUMMARY content are unchanged from 0.4.3.
No input or output data changes. Added a dataset output schema (.actor/dataset_schema.json) describing every delivered field — with English descriptions, types and examples — plus an "Overview" table view for the Console Output tab. This satisfies the Apify Store publishing requirement that an Actor ship an Output schema; the actual rows delivered are byte-for-byte identical to 0.4.2.
No input or output changes. This release refreshes the Actor's store listing around its real data source — 1688.com, Alibaba's domestic wholesale marketplace — so buyers searching for 1688 scraping, wholesale sourcing and dropshipping research find us accurately, and aligns the actor metadata version with the package version (0.4.2) for consistency. Release notes like this one move out of the README into this CHANGELOG; behaviour is unchanged from 0.4.1.
No input changes. Three improvements for existing users: you can now look up specific products by offerIds alone — no search keywords needed; sortBy=priceAsc / priceDesc / dropshipScore now genuinely re-order your ENTIRE delivered dataset (previously the platform's raw order could leak through); and data safety is stronger — if a run is interrupted or the platform moves it to another server, everything collected up to that point is still delivered instead of being lost. Note: the three sorting modes deliver all results in one ordered batch at the end of the run, so the dataset stays empty until then (expected).
No input changes. 0.4.0 is the first stable, generally available release: every order size (from 10 to 100 items) is verified end-to-end on the Apify cloud with full item counts and full detail coverage, backed by a repeatable cloud test-case suite. Billing stays honest and transparent — you only ever pay for the rows actually delivered. Nothing changes for existing users; this milestone simply marks a release we are confident to stand behind publicly.
No input changes. Fixed a reporting bug: when your order was fully filled (e.g. 60/60 items delivered) but an earlier search pass had ended early, the summary could still claim the run was incomplete (partial: true). A completed order now always reports shardStats.stopReason: "filled" with no partial flag — you will never rerun an order that was already finished. Also: cloud runs started without proxyConfiguration no longer go out on a bare datacenter connection (which 1688 blocks outright) — the Actor now automatically falls back to the RESIDENTIAL/CN proxy preset and logs a warning; an explicitly provided proxyConfiguration is still used exactly as given.
No input changes. When a large order hits the platform's temporary session-blocking wall, the Actor now waits briefly (~90 seconds) and tries once more before deciding to end early — leftover run time is spent on completing your order instead of being abandoned, and runs that genuinely cannot recover still stop honestly with partialReason: "identity_mint_fuse" (now only after the wait-and-retry has been spent). SUMMARY.shardStats gains two observability fields: mintCooldownRetries and mintCooldownRecovered.
No required input changes and no delivery-mechanics changes — this build is a data-quality pass over everything you receive. A few output values change shape for the better (flagged below and in "Field-semantics notes").
>, &, …) and inline markup (<span style=…>) are decoded/stripped from all output text fields (SKU specs, guarantee descriptions, titles, tags).weightKg is rounded to 3 decimals; quantityPrices tiers are deduplicated and strictly ascending by minQuantity; impossible stock sentinels (>10,000,000) are reported as null (unknown) instead of misleading mega-numbers.supplier.rateInfo now carries only positiveRate and score; other sub-fields previously present there have been removed.quantityPrices, tiers missing a numeric minQuantity are dropped — they are unusable for range logic.detailUrl is now always the canonical desktop link https://detail.1688.com/offer/{id}.html — no tracking parameters, no mobile/ad URL forms.isSuperFactory is derived from supplier.sellerType, isP4P also detects paid placements from the ad URL markers, and dropshipGrade now keeps just the letter (D+) with the caveat moved to a separate scoreConfidence field (ok / insufficient_data).keywords also accepts the common aliases query / search when keywords is absent.If your code parses output fields, note three shape changes: dropshipGrade is now a bare letter ("B" — previously it could carry a confidence caveat in the same string, which now lives in the new scoreConfidence field); stock.total / stock.skus[].count can now be null (previously always numeric); detailUrl strings change form (canonical, parameter-free), so URL-based dedup against older exports will not match.
No input changes — this build makes large orders more reliable and gives mid-size orders a bigger detail budget:
partialReason: "identity_mint_fuse" — you pay only for what was delivered. In practice: simply rerun; the next run starts with fresh sessions.One honest caveat: on large orders, part of the work depends on freshly created browsing sessions, and the platform sometimes blocks them. This never reduces the quality of what you receive — every delivered row keeps full details — it can only reduce how many rows arrive in a single run. If SUMMARY shows partial: true, rerun the Actor; billing is per delivered row either way.
Orders above 55 items change default behaviour. Starting with this build, an order with maxResults > 55 no longer returns the legacy mixed shape (full details up to the budget, search-card rows for the surplus). It runs full-detail sharding (SFD) by default:
maxResults. The SUMMARY states exactly why (partial + partialReason + shardStats.stopReason).Opt out: set fullDetailSharding: false to restore the legacy behaviour (surplus delivered at search-card level within the ~3-minute budget).