OLX India Listings Scraper
Pricing
from $0.07 / 1,000 result extracteds
Scrape public OLX India classified listings by keyword, category, location, or listing URL for prices, sellers, images, and attributes.
Provide search keywords such as car or iPhone, or supply Start URLs instead. At least one query or URL is required; queries run before URLs. Up to 20 queries and 50 combined inputs are supported.
Public HTTPS olx.in or www.olx.in category, search or listing URLs. At least one URL or Search query is required. URLs containing /q- are searched by their keyword and the OLX location ID; additional URL filters are not guaranteed to carry over. For an exact listing, use its /item/...-iid-ID URL.
Numeric OLX location ID used for keyword searches and Start URLs containing /q-. Default 1000001 searches all India. A location embedded in a /q- URL does not override this field.
Maximum number of classified listings to save across all queries and start URLs.
Visit each public listing page to refresh its description, images, status, and other public fields. Base rows are still saved with a warning when optional enrichment fails. Seller chat and contact-reveal flows are never opened.
Safety cap for each query or Start URL. The runtime default is 250. Pagination also stops at Maximum listings, on a repeated page, or before the run deadline.
Retries for temporary blocks, rate limits, server errors, timeouts, and malformed responses. Retry-After is honored within the run deadline.
Total Actor time budget in seconds. The runtime default is 270. The Actor reserves the final 30 seconds for checkpoints, the run summary, and shutdown.
Existing automatic strategy: start directly when omitted or useApifyProxy is false with no custom URLs. After direct requests fail, one target-bound standard Apify Proxy attempt may occur per run, with possible proxy usage charges. False chooses the initial direct route; it is not a direct-only switch. Set useApifyProxy true for managed proxy traffic from the start, or provide proxyUrls for your own proxies. Explicit settings are used unchanged; configured proxies do not get an additional automatic route. Invalid or unsupported settings are rejected before requests. No separate connection selector is provided because a direct-only strategy is not supported.
{ "useApifyProxy": false}