If you are trying to scrape Webmotors - Brazil's largest used car marketplace - to monitor prices, benchmark a dealership's stock, or feed a market research dashboard, you already know the frustrating part: it is not a static HTML page you can pull with a single requests.get(). This post walks through why scraping Webmotors is harder than it looks, what a DIY approach actually costs you in maintenance, and how to get clean structured data (price, odometer, seller, specs, FIPE percentage) without babysitting a scraper. Whether you searched "webmotors scraper", "webmotors api" or "scrape used cars brazil" to get here, the tradeoffs below apply either way.
Why scraping Webmotors is harder than it looks
Webmotors, like most modern car marketplaces, renders its listing grid client-side with JavaScript. A plain requests.get() returns a near-empty HTML shell - the actual make, model, price and photos get injected after the page hydrates in the browser. That alone rules out the simplest scraping approach and forces you into a headless browser.
Then there is anti-bot protection. Car marketplaces get scraped constantly by dealers, aggregators and price-comparison tools, so datacenter IPs get rate-limited or blocked outright after a handful of requests. You either rotate residential proxies yourself, or your scraper quietly dies after a few hundred listings.
