OLX India Listings Scraper
Pricing
from $0.07 / 1,000 result extracteds
OLX India Listings Scraper
Scrape public OLX India classified listings by keyword, category, location, or listing URL for prices, sellers, images, and attributes.
Pricing
from $0.07 / 1,000 result extracteds
Rating
0.0
(0)
Developer
Fetch Cat
Maintained by CommunityActor stats
0
Bookmarked
17
Total users
6
Monthly active users
8 days ago
Last modified
Categories
Share
Export public OLX India classified listings with prices, locations, seller labels, images and category attributes. Search by keyword or supply public category/search/listing URLs, then download the dataset as CSV, JSON or Excel through Apify.
Only publicly available listing data is collected. Contact-reveal, chat and login-only data are not supported. Some fields can be missing, and a readable search with no matches returns an empty dataset.
Quick start
- Open the input form and enter a search query, or replace it with an OLX India URL.
- Set Maximum listings to a small number and run the Actor.
- Open the dataset to inspect results and export them.
{"queries": ["car"],"locationId": "1000001","maxItems": 20}
At least one queries or startUrls entry is required. You can use both. Queries are processed first and share one total listing limit.
Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.
Ready-to-run examples
Choose a public example to see its settings before starting a run:
What you get
One public listing row with its ad ID, source attribution and available asking price, location, seller labels, images and category attributes. Optional detail enrichment can leave the base row intact with a warning. Description text is redacted for contact-like content rather than revealing private phone or chat information.
Who is it for?
- Classifieds-market researchers reviewing public asking-price samples.
- Vehicle and electronics analysts checking source-linked local listing context.
- Inventory research teams comparing their own retained listing snapshots.
- Data developers importing category attributes, provenance and row outcomes.
How you can use the data
- Review a small India car sample. Use the existing car query and all-India location ID with a small cap. Keep adId, public URL, asking price and available location fields before making a manual comparison, rather than treating the result as a complete local market.
- Inspect optional bike-listing enrichment. Use the existing bike example when extra public category fields matter. Keep detailStatus and warnings with the row, since unavailable details retain a valid base listing rather than proving those attributes do not exist.
- Compare iPhone asking-price samples carefully. Use the existing iPhone workflow with explicit location selection and inspect actual locations. Search URLs containing /q- use keyword and locationId, not guaranteed embedded city or browser filters.
- Join your own repeat exports. Retain adId, collection time and source provenance for comparisons in your destination. The Actor does not generate change reports or alerts. An interrupted run can use its own checkpoint through Apify resurrection, while a newly started run does not automatically reuse another run's storage.
Input settings
| Setting / API key | Purpose |
|---|---|
Search queries / queries | Up to 20 keyword searches. |
Start URLs / startUrls | Public OLX India category, search or exact listing URLs. Strings or objects with url. |
OLX location ID / locationId | Numeric location for keyword searches, including URLs containing /q-. Default 1000001 means all India. |
Maximum listings / maxItems | Total saved listings across all sources. Default 20, maximum 10,000. |
Detail enrichment / includeDetails | Request additional public listing fields. Default false. Unavailable details leave the base row intact. |
Maximum pages / maxPages | Per-source page limit. Runtime default 250. |
Request retries / maxRequestRetries | Retry limit. Default 2. |
Maximum run time / maxRuntimeSecs | Run budget of 40–270 seconds. Runtime default 270. |
Proxy configuration / proxyConfiguration | Optional managed or customer proxy settings. See field help for the existing automatic connection behavior and charges. |
Search URLs containing /q- use the keyword and locationId. Other filters or a city embedded in that URL are not guaranteed to be retained. Category URLs can contain results selected by OLX, so inspect the returned category and location fields. There is no input for sorting results. Order follows OLX responses.
Example inputs
Use the Quick start input as a small first run. Adjust the fields described above for your own data.
Output data
Illustrative shape only. This is not a newly observed listing:
{"adId": "example-id","title": "Example public listing","price": null,"currency": null,"location": {},"sellerName": null,"imageUrls": [],"attributes": {},"sourceUrl": "car","sourceType": "query","sourcePage": 1,"detailStatus": "not_requested","warnings": []}
| Fields | Meaning |
|---|---|
url, adId, title, descriptionSnippet | Listing identity and public description with contact-like text redacted. |
price, priceDisplay, currency | Numeric and displayed asking price when available. |
location | Available country, state, city, locality and coordinates. |
categoryId, categoryName, status, postedAt, createdAt, validTo | Public category, status and timestamps. |
sellerName, sellerType, sellerId, isBusiness, isKycVerifiedUser, eliteSeller | Available public seller labels and flags. |
hasPhoneParam | Contact-availability indicator, not a phone number. |
favoriteCount, imageCount, videoCount | Available listing and media counters. |
imageUrls, images | Image links and dimensions when available. |
attributes, rawAttributes | Category attributes and their public labels. |
sourceUrl, sourceType, sourcePage, scrapedAt | Input provenance, page and collection time. |
detailStatus, descriptionRedacted, warnings | Enrichment status, redaction indicator and row warnings. |
Fields depend on what OLX exposes. The key-value store's RUN_SUMMARY reports saved results, source outcomes and warnings. An interrupted run may retain RUN_CHECKPOINT for continuation through Apify resurrection. Starting a new run does not automatically reuse another run's storage.
Download your results
Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.
See Apify's download and export guide for the available formats and field options.
Pricing
The start event is charged once after a usable listing response or a readable empty or unavailable result. A run failing before any usable response does not incur it. The result event applies to each unique saved listing. Duplicates, failed requests and failed optional enrichment are not separate paid rows, while a saved base listing still counts when details are unavailable.
Use a small row cap with explicit page and runtime budgets when needed. Optional enrichment adds requests and Apify platform or proxy usage may apply separately. See the live Pricing tab for current rates and discounts.
Tips for best results
- Choose an explicit location ID for keyword searches. Browser URL city and filter details may not carry over.
- Keep the first query and cap small. Queries run before supplied URLs under one shared limit.
- Review output location and category fields. Source recommendations can affect which listings are returned.
- Retain enrichment status and warnings. A useful base row can survive missing optional details.
- Read the summary before comparing datasets. Mixed or time-limited runs can preserve useful but incomplete samples.
Limits and caveats
Only public OLX India listings are collected. Contact revelation, chats, login-only and private account data are unsupported. Contact-like description text is redacted, and hasPhoneParam is an availability indicator rather than a phone number. Public seller flags do not independently verify identity. This tool is not affiliated with OLX.
At least one query or URL is required and both can contribute, with queries first under one shared saved-row cap. Up to twenty queries are supported. Search URLs containing /q- use keyword and locationId, while other filters or embedded cities are not guaranteed. Category results follow OLX selections. No custom sorting is exposed and source response order is retained.
Fields depend on public availability. Optional detail failure leaves the saved base listing with unavailable status and a warning rather than a separate paid error row. Seller, media and attribute values are public source labels and can be missing or change.
Readable no-match searches and unavailable exact listings can succeed with zero rows. Blocks, unexpected responses, storage failures and all-source failures do not establish an empty market. Mixed runs can retain useful rows alongside source warnings or failures. Large requests can stop partially within the run budget, so inspect RUN_SUMMARY rather than assuming the cap was reached.
An interrupted run may retain RUN_CHECKPOINT for Apify resurrection. Starting a new run does not automatically reuse another run's storage. Keep your own ad-ID joins and collection times for historical comparisons, change reporting or notifications.
Automation and integrations
Save your settings for next time
Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.
Run on a schedule
Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.
Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.
Send results to your other tools
Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.
For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.
API usage
Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.
The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.
For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.
cURL
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~olx-india-listings-scraper/runs' \-H "Authorization: Bearer $APIFY_TOKEN" \-H 'Content-Type: application/json' \--data @- <<'JSON'{"queries": ["car"],"locationId": "1000001","maxItems": 20}JSON
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('fetch_cat/olx-india-listings-scraper').call({"queries": ["car"],"locationId": "1000001","maxItems": 20});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Python
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('fetch_cat/olx-india-listings-scraper').call(run_input={'queries': ['car'], 'locationId': '1000001', 'maxItems': 20})print(client.dataset(run['defaultDatasetId']).list_items().items)
MCP and AI agents
You can ask your AI assistant to collect data with OLX India Listings Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.
Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.
Easier setup with an Apify plugin
If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.
Use Apify AI in Console
Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's OLX India Listings Scraper. You can describe the data you want and ask questions about the results.
Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.
Choose your assistant
- Claude and Claude Code (Anthropic): Apify setup guide.
- ChatGPT and Codex (OpenAI): Apify setup guides.
- Grok Bot (xAI): Apify plugin guide.
- Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.
Connect just this scraper
To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=fetch_cat/olx-india-listings-scraper"}}}
Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.
Use Apify's general server
Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use OLX India Listings Scraper by Fetch Cat, or give it the identifier fetch_cat/olx-india-listings-scraper.
Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.
Example requests
- “Use Fetch Cat’s OLX India Listings Scraper to collect up to 5 car listings with location ID 1000001 and details off. Keep IDs, source links, asking prices and available locations without claiming complete India-wide coverage.”
- “Collect up to 5 iPhone listings with location ID 1000001 and details off. Keep price currency and output locations for my own comparison, without treating hidden contact indicators as phone numbers.”
- “Retrieve up to 5 bike listings with location ID 1000001 and public detail enrichment enabled. Keep base rows, enrichment status and warnings if optional details fail, without revealing contacts or automatically restarting interrupted work.”
Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.
Pay with x402
If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.
Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.
Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.
Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.
Other ways for agents to pay
Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.
FAQ
Is this an official OLX API?
No. It is an independent Actor exporting publicly available listing data through the Apify API. It is not affiliated with OLX.
Do I need an OLX account, and can I get phone numbers?
No OLX login is needed. Phone revelation, chats and private account data are not supported. Contact-like text in descriptions is redacted.
Can I export OLX India listings to CSV or Excel?
Yes. Use Apify's dataset export after the run, or retrieve JSON through the API.
Why are optional details missing?
OLX may omit fields or make a detail page unavailable. A valid base listing remains saved with detailStatus: "unavailable" and a warning if requested enrichment fails.
Why did my city search include other locations?
For URLs containing /q-, set the desired numeric locationId explicitly. URL filters are not guaranteed to carry over. Inspect the output location before using it in a local comparison.
Related Actors
- Craigslist Classifieds Scraper — another classified marketplace.
- AutoScout24 Car Listings Scraper — vehicle-listing research.
- Google Shopping Results Scraper — shopping result comparisons.
- eBay Marketplace Scraper — marketplace product research.
- Gumtree Listings Scraper — public classifieds exports.
Support and feedback
For custom additions or integrations, email hello@fetchcat.dev.
Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.
Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.
Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.
Made with care for curious people, AI agents and the possibilities in data. ♥