OLX Brasil Scraper: New Listing & Price Alerts
Pricing
from $1.52 / 1,000 listing returneds
OLX Brasil Scraper: New Listing & Price Alerts
OLX Brasil scraper by keyword: search Brazil's general classifieds marketplace, get one row per listing (title, price, category, city, link). Turn on monitoring for only new listings and price drops since your last run. No login required; empty searches and quiet runs are free.
Pricing
from $1.52 / 1,000 listing returneds
Rating
0.0
(0)
Developer
Adrian Voss
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Watch an OLX search, get only what's new. This actor runs your search against OLX Brasil's own search-results pages — olx.com.br, Brazil's #2 e-commerce site by traffic and the country's largest general classifieds marketplace (goods, cars, property, all in one search) — and returns one clean row per listing: title, price, category, location, and a permanent link. 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. Schedule it hourly and send the results to Discord, Slack, Google Sheets, or n8n.
Who it's for
A reseller or arbitrage buyer watching one category (phones, cars, tools) for underpriced or newly-posted listings across all of Brazil, or one state, wants a live feed of what's actually on OLX right now, without refreshing the search page by hand and without OLX Brasil's own site (which has no native saved-search alert at all). 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 or a filtered OLX search URL, 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. A quiet run — nothing new, nothing cheaper — still finishes and costs only the base run fee.
- Reads OLX Brasil's own server-rendered listing data, not a screen-scrape of rendered text — a React Server Components payload embedded in every search page — so price, category, and location are the same structured values OLX's own app reads.
- 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.
- Paste a keyword or your own saved search URL. Type plain keywords, or paste an OLX Brasil search-results URL you've already filtered on the site — its filters carry straight through.
- Excludes paid-placement listings from new-listing alerts by default. OLX Brasil pins a handful of paid listings to the top of every page; they re-surface on every run even though nothing about them changed. This actor drops them before billing unless you turn that off.
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 Brasil 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 (parsed out of a pasted URL, if you gave one) |
listingCount | number | Listings returned and billed for this search |
totalAvailable | number | Total listings OLX Brasil reports matching this search |
truncated | boolean | true if more results existed than were returned, or a later page was blocked |
newCount | number | New listings this run (monitoring only) |
priceDropCount | number | Price drops this run (monitoring only) |
monitorStatus | text | NO_NEW_ROWS on a quiet monitoring run, SEEDED on a silent first run, NEW_ROWS otherwise |
listingId | text | OLX Brasil's own numeric listing ID |
title | text | Listing title (contact-info-like strings redacted) |
price | number | Price in BRL, parsed from OLX's own formatted price string |
currency | text | Always BRL |
previousPrice | number | OLX's own previous price, when OLX itself shows a price-drop badge on the listing |
priceReduced | boolean | true when OLX Brasil is showing its own price-drop badge |
postedAt | date | See "A note on dates" below — OLX Brasil doesn't expose a separate original-post timestamp |
bumpedAt | date | Computed from OLX's own "last bumped N seconds ago" field |
isBumped | boolean | true when bumpedAt is meaningfully later than postedAt — see the note below |
category | text | OLX Brasil's own category name for this listing |
state | text | Two-letter Brazilian state code (UF) |
city | text | City |
neighbourhood | text | Neighbourhood, when OLX has one for this listing |
sellerType | text | private or professional, from OLX's own "professional ad" flag |
sellerName | text | Opt-in, professional sellers only. A business's own storefront name — never a private individual's |
isFeatured | boolean | OLX's own "featured" flag |
isPinned | boolean | true for a paid placement pinned to the top of the page — excluded by default, see "Why this one" |
condition | text | New / used / condition grade, when the category has one |
brand | text | Brand, when the category has one (electronics, vehicles) |
model | text | Model, when the category has one |
attributes | object | Every category-specific attribute OLX Brasil has for this listing (storage, mileage, fuel type, bedrooms, etc.), as a flat {name: value} object |
hasOlxPay | boolean | OLX Pay (in-platform payment) enabled on this listing |
hasOlxDelivery | boolean | OLX Delivery (shipping) enabled on this listing |
imageCount | number | Number of photos |
imageUrl | text (link) | First listing image |
changeType | text | new, price-drop, or seen (monitoring only) |
isNew | boolean | true on this listing's first appearance in your watchlist (monitoring only) |
priceChangePct | number | Percentage drop from the price this watchlist itself last recorded (monitoring only) |
previousSeenPrice | number | The price this watchlist last recorded for this listing (monitoring only) — distinct from OLX's own previousPrice badge above |
monitorFirstSeenAt | date | When this watchlist first saw this listing (monitoring only) |
url | text (link) | Permanent 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.
A note on dates. OLX Brasil's search results carry a "last bumped N seconds ago" counter but no
separate original-posting timestamp. postedAt and bumpedAt are therefore usually the same
moment, and isBumped is usually false — this actor doesn't fabricate a "first posted" date OLX
itself doesn't expose. What you reliably get is "how recently this listing moved" (was posted or
refreshed), which is what a new-listing alert actually needs.
A note on seller identity. OLX Brasil's search results carry no seller ID at all on this route
— not even a hashed one. There is nothing to de-duplicate sellers by beyond the private /
professional flag, so this actor doesn't invent a sellerHash column the way some other actors
in this catalogue do for platforms that do expose one.
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.
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 Brasil 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 this watchlist itself last saw it — not OLX's own
previousPricebadge, which is a separate, OLX-computed signal reported in every row regardless of monitoring. - Already-seen, unchanged listings are dropped before you're billed. A quiet run — nothing new,
nothing cheaper — still finishes and returns one free row with
monitorStatus: NO_NEW_ROWS. - The first run has nothing to compare against. By default it returns everything it finds as "new". Turn on "Seed silently" to instead have the first run bank everything quietly with zero rows and zero charge, and start alerting from the second run on.
- Sort is forced to OLX's own newest-first order whenever monitoring is on, so two runs of the same watchlist are always comparing the same ordering.
- Pinned (paid-placement) listings are excluded by default ("Exclude pinned" above) — they re-surface on every page regardless of what's actually new, which would otherwise show up as false "new listing" alerts every run.
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 to get pinged only when something actually changes.
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 between
runs, this actor has no way to notice it dropped. Keep searches reasonably narrow (a specific model,
a tight category, one state) rather than one huge catch-all if price-drop coverage matters to you.
Replaces your Telegram alert bot. OLX Brasil has no native saved-search alert feature at all — and it is, by a wide margin, the most bot-built target found in this catalogue's Latin America research: at least 7 independent GitHub Telegram-alert bots exist purely to fill that gap, each one a server someone has to run and fix when OLX changes its page. This actor is the same job as a hosted, schedulable API: no server to keep alive, no page-layout break to notice at 2am, and output that goes straight to Google Sheets, n8n, Make, or a webhook instead of a Telegram chat.
How to use
- In the Apify Console. Open the actor page and click Start — the
searchesfield is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found. - 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-brasil-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \-X POST \-H "Content-Type: application/json" \-d '{"searches":["iphone"]}'
- 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.
- 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 per line — plain keywords (e.g. "iphone", "honda civic") or a full search-results URL copied from olx.com.br, including any filters it already has. No login required. Accepted formats: iphone, honda civic, https://www.olx.com.br/autos-e-pecas/carros-vans-e-utilitarios/estado-sp?q=onix.
Sample output
| query | found | status | searchQuery | listingCount | totalAvailable | truncated | newCount | priceDropCount | monitorStatus | listings | listingId | title | price | currency | previousPrice | priceReduced | postedAt | bumpedAt | isBumped | category | state | city | neighbourhood | sellerType | sellerName | isFeatured | isPinned | condition | brand | model | attributes | hasOlxPay | hasOlxDelivery | imageCount | imageUrl | changeType | isNew | priceChangePct | previousSeenPrice | monitorFirstSeenAt | url | scrapedAt |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| iphone | true | OK | <monitoring status (quiet / seeded runs)> | <all listings found (full list)> | <price (brl)> | <olx's own previous price (price-drop badge)> | <posted / last bumped (olx doesn't separate the two)> | <last bump time (computed)> | <recently bumped, not a fresh post> | <state (uf)> | <seller type (private / professional)> | <business seller name (professional sellers only, opt-in)> | <pinned to top of search (paid placement)> | <all listing attributes (category-specific)> | <new / price-drop / seen> | <is this listing new?> | <price drop % since we last saw it> | 1970-01-01T00:00:00.000Z |
A search that finds nothing comes back as a row with "found": false and is never charged. A quiet
monitoring run comes back as a row with "found": true, "monitorStatus": "NO_NEW_ROWS" and is also
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-brasil-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-brasil-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-brasil-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 Brasil Scraper | Apify" — the agent will find and run this actor.
Tips
- Start monitoring with "Seed silently" 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, one state) — see "Price-drop window limitation" above for why a huge catch-all search misses price drops on listings that fall outside what gets fetched.
- Paste your own already-filtered OLX Brasil search URL instead of rebuilding filters in this actor's Input tab — anything the URL already filters on carries straight through.
- A
BLOCKEDstatus means OLX Brasil's Cloudflare protection didn't clear for this run — UNBLOCKER is intermittent by nature; try again shortly or lower "Max concurrency". - This actor requires the UNBLOCKER proxy group by default — leave the proxy configuration on its default rather than switching to a datacenter/no-proxy setting, or every search will be blocked.
vs. olx.com.br's own alerts, and vs. solidcode/olx-brasil-scraper
OLX Brasil has no native saved-search alert feature at all — buyers rely entirely on
third-party bots, and at least 7 independent GitHub Telegram-alert repos exist to fill that gap. The
current Apify Store leader for OLX Brasil, solidcode's actor, has 58 users in the last 30 days and
197 lifetime, rated 5 stars, with no monitoring mode — a one-off dump, the same shape every other
OLX Brasil scraper on the Store ships.
| What it costs | What you get | Trade-off | |
|---|---|---|---|
| This actor | Pay per listing returned; nothing for a miss or a quiet monitoring run | Any OLX Brasil category, state-level filtering, monitoring mode (new + price drop), pinned-listing exclusion | No original-posting timestamp (OLX doesn't expose one — see "A note on dates") |
| A Telegram alert bot from GitHub | Free, but you run and maintain the server | Alerts to your own Telegram | Breaks silently when OLX changes its page; no Sheets/n8n/webhook output |
| 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 RSC parsing, monitoring state, and privacy 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
private/professional flag, and — only for professional sellers, only when you turn it on — the
business's own storefront name. OLX Brasil exposes no seller ID at all on this route, so there is no
hashed seller identifier either. Phone numbers, WhatsApp links, and emails are never output, even
inside a listing's title; contact-info-like strings are redacted to [redacted]. Turning on seller
info makes you responsible for having a lawful reason to process it. Not affiliated with OLX Brasil
/ Grupo OLX Brasil.
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 Brasil's terms and your local law.
Seller phone numbers and emails are never collected. Brazil's data-protection law, the LGPD, is GDPR-like — seller identity is off by default here for the same reason it is on every other actor in this catalogue.
FAQ
Why is a row empty, or why does found say false?
Either the input line was blank (status: BAD_FORMAT), OLX Brasil returned a block page
(status: BLOCKED), or the search matched nothing on OLX Brasil 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, you get one row with
monitorStatus: NO_NEW_ROWS and listingCount: 0 — Actor.charge() only fires when
listingCount is greater than zero.
What's the difference between previousPrice and previousSeenPrice?
previousPrice is OLX Brasil's own price-drop signal — it's on every row, monitoring or not,
whenever OLX itself is showing a price-drop badge on that listing. previousSeenPrice only appears
with monitoring on, and is the price this watchlist last recorded for that listing — a different,
narrower signal based only on what you've actually seen.
Does this return the original posting date?
No — see "A note on dates" above. OLX Brasil's search results only expose a "last bumped" counter,
not a separate first-published timestamp, so postedAt and bumpedAt are usually the same moment.
Can I paste my own filtered OLX Brasil search instead of using this actor's category/state filters? Yes. Paste the full search-results URL from your browser's address bar as a search line — any filters already in it carry through unchanged, and the Category/State inputs are ignored for that line.
Do I need to configure proxies? This actor uses Apify's UNBLOCKER proxy group by default — OLX Brasil sits behind Cloudflare, which UNBLOCKER clears over a plain HTTP request (no headless browser needed). Leave the proxy configuration on its default.
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 Brasil Scraper | Apify"), or you can call the REST endpoint shown above from any script or workflow tool.
Related actors
- OLX Scraper — the European OLX
/api/v1/offers/stack (Poland, Portugal, Romania, Bulgaria, Ukraine). A different Grupo OLX company with a different API — not the same codebase as this actor.