JD Mart Business Scraper
Pricing
from $4.99 / 1,000 results
JD Mart Business Scraper
A fast, high-performance scraper built for lead generation, competitor analysis, and business intelligence. Extracts detailed business profiles, including name, contact details, emails, phone numbers, location, ratings, and reviews from Jdmart Business. Supports custom search URLs, proxy rotation...
Pricing
from $4.99 / 1,000 results
Rating
0.0
(0)
Developer
Coding Frontned
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
15 hours ago
Last modified
Categories
Share
Collect public JD Mart supplier and product records from a keyword/location search or from specific product/profile URLs. The Actor uses an ordinary Chromium browser, does not alter browser fingerprints or automation signals, and can use an optional Apify proxy configuration.
Input
mode:search(default) ordirectUrl.keyword: required in search mode.location: search location; defaults toIndia.directUrls: HTTPS JD Mart product/profile URLs containing/pid-; required in direct URL mode.maxItems: maximum successful rows, from 1 to 200. It is an upper bound, not an exact-count promise.maxPages: search-page limit, from 1 to 20.scrapeDetails: visit profile pages for optional enriched fields; defaults totrue.proxyConfiguration: optional Apify Proxy settings. Invalid proxy settings fail the run rather than silently using direct traffic.
Unknown fields and invalid types are rejected. This bounded example requests at most three detailed records:
{"mode": "search","keyword": "office furniture","location": "Delhi","maxItems": 3,"maxPages": 2,"scrapeDetails": true}
Output
Successful public records are written to the default dataset. Required fields include the published business name and canonical JD Mart URL plus collection provenance, HTTP status, success flags, and timestamp. Optional fields such as price, rating, phones, description, website, specifications, and reviews are emitted only when the public page exposes them; the Actor does not invent missing values.
The OUTPUT key in the default key-value store reports the final status, requested limits, saved and scheduled counts, bounded request failures, and whether a proxy was configured. A successful run may contain fewer rows than maxItems when the public source has fewer accessible results. If every requested page fails, the run fails and leaves diagnostics in OUTPUT instead of producing placeholder rows.
Development
npm cinpm testnpm run lintnpx apify-cli validate-schemanode validate-datasets.js <dataset.json-or-directory-or-stdin-dash>
Respect JD Mart's terms and applicable privacy, data-protection, and marketing laws. Collect only public data you are authorized to use.