OLX India Scraper: New Listing & Price Alerts

Watch a search, get only what's new. This actor runs your search against OLX India's own "Panamera" search API — the largest OLX market by lifetime Store demand in the whole Asia sweep this catalogue was built from — and returns one clean row per listing: price, city, condition, seller trust signals, and whether a listing is a genuine new post or an old one bumped back to the top. Turn on monitoring and it becomes a watchlist: new listings and price drops since your last run, charged per new row, free on quiet days. Prefix a search id: to run the same search against OLX Indonesia instead.

Who it's for

A reseller or arbitrage buyer watching one category (phones, bikes, electronics) across India's biggest classifieds site for underpriced or newly-posted listings wants a live feed of what's actually on OLX right now, without refreshing the search page by hand. A market-research team tracking asking prices for a product category, or a Sheets/n8n workflow that reacts the moment something new is posted, gets the same shape here: paste a list of search terms, get back a flat row per listing, and pay only for listings actually returned — a search that finds nothing costs nothing.

Why this one

• Monitoring first, not a one-off dump. Turn on "Only return results that are new, or dropped in price" and this actor becomes a watchlist: it remembers every listing ID it has already shown you, and only bills you for what's actually new or has dropped in price since the last run.
• Bumped or genuinely new? OLX lets sellers push an old listing back to the top of search results without re-posting it. This actor reads both created_at (the listing's most recent activity) and created_at_first (its original post time) and flags isBump: true whenever those two diverge by more than a day — so a watchlist doesn't mistake a seller refreshing a month-old ad for a real new listing.
• Real trust signals, not just a price. Every row carries OLX's own business/individual split, "elite seller" badge, and KYC-verification flag — useful for filtering out anonymous or unverified sellers before you act on a listing.
• India and Indonesia, one actor. A plain search runs against OLX India; prefix it id: and the identical search runs against OLX Indonesia, reached through a residential-and-datacenter- resistant unblocking proxy this session confirmed works — billed as its own, separately priced event so an India-only run never pays extra for a country it didn't use.
• Never charged for a miss, or a quiet monitoring run. A search that finds nothing, or a scheduled watchlist run where nothing changed, still gets a row explaining what happened — and costs nothing.

What you get

One row per listing by default (turn off "Expand rows" in Advanced to get one row per search instead, with the listings nested under listings).

Field	Type	Description
query	text	The search you submitted, echoed back
found	boolean	true if OLX returned real search results for this search
status	text	OK on a match; NOT_FOUND, BLOCKED, or BAD_FORMAT on a miss
message	text	Plain-English reason for a miss — only present when found is false
searchQuery	text	The keyword actually searched (the id: prefix stripped)
sourceCountry	text	in (India) or id (Indonesia)
listingCount	number	India listings returned and billed this search (0 for an Indonesia search)
listingIdCount	number	Indonesia listings returned and billed this search (0 for an India search)
totalAvailable	number	Total listings OLX reports matching this search, including ones not returned
truncated	boolean	true if more results existed than were returned
newCount	number	New listings this run (monitoring only)
priceDropCount	number	Price drops this run (monitoring only)
listingId	text	OLX's own listing ID
title	text	Listing title
description	text	Listing description, with emails and phone-shaped numbers redacted
price / priceDisplay / currency	number / text / text	Numeric price, OLX's own display string, and currency (INR or IDR)
postedAt	date	Most recent activity time (a fresh post, or the moment a bump pushed it back up)
firstPostedAt	date	The listing's original post time
isBump	boolean	true when the listing is an old post bumped back up, not a genuinely new one
state / city / locality	text	OLX's own location hierarchy for the listing
isBusiness	boolean	OLX's own business-seller flag
eliteSeller	boolean	OLX's "elite seller" badge
kycVerified	boolean	OLX's own seller identity-verification flag
condition / brand / model	text	From OLX's own listing parameters, when the category exposes them
category	text	OLX category ID
listingStatus	text	active or sold, as OLX reports it
favorites	number	Times the listing has been favorited on OLX
imageUrl / imageCount	text (link) / number	First image and photo count
sellerHash	text	Anonymous, stable hash of the seller — lets you group listings by seller without exposing an identity
userName	text	Seller's raw OLX display name — only present with "Include raw seller name" on
isIndonesiaListing	boolean	true for an Indonesia-sourced row (drives the separate listing-id billing event)
changeType	text	new, price-drop, or seen (monitoring only)
isNew	boolean	true on this listing's first appearance (monitoring only)
previousPrice / priceDropPct	number	The price last recorded, and the percentage drop, when it fell (monitoring only)
firstSeenAt	date	When this watchlist first saw this listing (monitoring only)
url	text (link)	Listing link
scrapedAt	date	When this row was fetched

Deselect any field in the Input tab's column picker to drop it from every row — query, found, status, message, and scrapedAt always stay. Phone numbers and email addresses are never collected, on any field, regardless of "Include raw seller name".

Pricing

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see .actor/pay_per_event.json for exact prices. A miss is never charged.

India listings bill the base listing event. Indonesia listings (id:-prefixed searches) bill a separate, higher listing-id event instead — never both on the same row — because reaching OLX Indonesia costs this actor real unblocking-proxy traffic that a plain India request doesn't.

Monitoring / only new results

Turn on "Only return results that are new, or dropped in price" and a search line becomes a watchlist instead of a one-off dump:

• A listing counts as new the first time its OLX listing ID is returned by this watchlist.
• A listing counts as a price drop when its price falls by at least "Minimum price drop" (5% by default) since it was last seen.
• Already-seen, unchanged listings are dropped before you're billed. A quiet run still finishes and costs nothing beyond the flat run fee.
• The first run has nothing to compare against and returns everything as "new" by default. Turn on "Skip alerts on the first run" to instead have the first run bank everything quietly with zero rows and zero charge.

Schedule recipe. Save this actor as an Apify Task with deltaMode: true and a deltaName you choose, add an hourly (or daily) Schedule, and point the task's webhook at Discord, Slack, Google Sheets, or an n8n/Make webhook URL.

Price-drop window limitation. A price drop is only ever seen while the listing is still inside what a run actually fetches — if a listing falls out of your maxListingsPerSearch window or your price filters between runs, this actor has no way to notice it dropped.

How to use

1. In the Apify Console. Open the actor page and click Start — the searches field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~olx-india-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"searches":["iphone"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

4. Prefix any search id: (e.g. "id:iphone") to search OLX Indonesia instead of OLX India.
5. Turn on "Only return results that are new, or dropped in price" under Monitoring once you want a watchlist instead of a one-off dump — see "Monitoring / only new results" above.

Input

{
  "searches": [
    "iphone"
  ]
}

One search per line — a keyword like "iphone" (searches OLX India), "id:iphone" (prefix "id:" to search OLX Indonesia instead), or a pasted olx.in / olx.co.id search URL. Accepted formats: iphone, royal enfield, id:iphone, https://www.olx.in/api/relevance/v4/search?query=iphone.

Sample output

query	found	status	searchQuery	sourceCountry	listingCount	listingIdCount	totalAvailable	truncated	newCount	priceDropCount	listings	listingId	url	title	description	price	priceDisplay	currency	postedAt	firstPostedAt	isBump	state	city	locality	isBusiness	eliteSeller	kycVerified	condition	brand	model	category	listingStatus	favorites	imageUrl	imageCount	sellerHash	userName	isIndonesiaListing	isNew	changeType	previousPrice	priceDropPct	firstSeenAt	scrapedAt
iphone	true	OK		<country searched (in/id)>							<all listings found (full list)>				<description>		<price (as olx displays it)>		<posted / last bumped (date)>	<originally posted (date)>	<bumped, not a new listing>			<locality / area>								<status (active/sold)>				<seller (anonymous hash)>	<seller name (only with seller info on)>	<indonesia listing (billed separately)>	<is this listing new?>			<price drop %>		1970-01-01T00:00:00.000Z

A search that finds nothing comes back as a row with "found": false and is never charged.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~olx-india-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"searches":["iphone"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~olx-india-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"searches":["iphone"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~olx-india-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"searches":["{{search}}"]}, mapping the row's search into the searches array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "OLX India Scraper | Apify" — the agent will find and run this actor.

Tips

• Start monitoring with "Skip alerts on the first run" on for any watchlist you're setting up on a schedule — it avoids a wall of "new" alerts for your entire current search result on day one.
• Keep a monitored search reasonably narrow (a model, a tight category) — see "Price-drop window limitation" above for why a huge catch-all search misses price drops on listings outside what gets fetched.
• There's no published city-name-to-ID lookup for the "Location ID" field — run once with the default (all India) and read the city/locality columns on a result near where you want to search to find its OLX location ID.
• A BLOCKED status means OLX returned a 403, 429, or 503 after this actor's own automatic residential/unblocking-proxy retry also failed — trying again shortly usually clears it.

vs. natanielsantos/olx-scraper-india

The current Apify Store leader for OLX India, natanielsantos/olx-scraper-india, is the largest actor found across this catalogue's entire Asia demand sweep — 456 lifetime users — and is a one-off dump with no monitoring mode. This actor adds new-listing and price-drop monitoring as a first-class feature, bump-vs-new detection (OLX's own leader doesn't distinguish a refreshed old post from a genuine new one), and OLX Indonesia coverage in the same run.

	What it costs	What you get	Trade-off
This actor	Pay per listing returned; nothing for a miss or a quiet monitoring run	Monitoring (new + price drop), bump detection, trust signals, India + Indonesia	No published location-name lookup — location IDs are self-discovered from a first run
The current leader	Per-run pricing, no per-listing metering seen in its listing	A one-off dump of search results	No monitoring, no bump detection
Doing it yourself	Your time to build and maintain a scraper, a seen-listing store, and a price-tracking layer	The same data	This actor's monitoring state, bump logic, and redaction are the maintenance burden it absorbs

Data & privacy

This actor reads public search results that anyone can see without logging in. It doesn't log in, solve CAPTCHAs, or reveal hidden contact details. Seller identity is off by default: you get a business/individual flag, elite-seller and KYC badges, and an anonymous seller hash so you can group listings by seller without a name. Turning on seller info makes you responsible for having a lawful reason to process it. Phone numbers and email addresses embedded in a listing's own description are redacted to [redacted] and never collected as a separate field. Not affiliated with OLX.

Is this allowed? It collects the same public listing data your browser shows, for the searches you choose. It's built for monitoring a search, not for copying the marketplace. Check that your use fits OLX's terms and your local law.

FAQ

Why is a row empty, or why does found say false? Either the input line was blank (status: BAD_FORMAT), OLX returned a 403/429/503 that this actor's fallback couldn't clear (status: BLOCKED), or the search matched nothing on OLX right now (status: NOT_FOUND). Check the message column for the specific reason. None of these are billed.

Am I charged for a quiet monitoring run? No. When monitoring finds nothing new and no price drops, listingCount/listingIdCount are both 0 and nothing is charged.

What's the difference between postedAt and firstPostedAt? firstPostedAt is when the listing was originally posted. postedAt is its most recent activity — which can be later if the seller "bumped" it back to the top without re-posting. When the two differ by more than a day, isBump is true.

How do I search OLX Indonesia? Prefix the search id:, e.g. "id:iphone". Those rows bill the separate listing-id event instead of the base listing event.

Do I need to configure proxies? No. OLX India searches use Apify's default proxy configuration by default, with an automatic residential fallback if that's ever blocked. OLX Indonesia searches always route through an unblocking proxy automatically — no configuration needed either way.

Can an AI agent call this directly? Yes. It's registered on the Apify MCP server — an agent in Claude, Cursor, or another MCP client can find and run it by name ("OLX India Scraper | Apify"), or you can call the REST endpoint shown above from any script or workflow tool.

Related actors

• OLX Scraper — the same catalogue's European OLX actor (Poland, Portugal, Romania, Bulgaria, Ukraine), on OLX Group's different /api/v1/offers/ stack.