Scrape Webmotors Vehicle Listings and Dealer Data
Webmotors is a Brazilian car marketplace where listings, dealer pages and prices change constantly.
A hosted scraping API is one way for a data or engineering team to turn those public pages into structured records, instead of operating its own browser fleet, proxy pool and anti-bot handling. Whether that trade-off pays off depends on your volume, your tolerance for infrastructure maintenance and how much control you need over the rendering stack. This page explains what the API is designed to return, which request parameters change the result, and how credits are consumed, so you can judge whether it fits a pricing, inventory or dealer-network workflow.
What a Webmotors scrape can return
When the relevant request options are enabled, a single call to a Webmotors listing URL is designed to come back as rendered HTML, as parsed JSON, or as AI-extracted JSON. The output mode you choose determines how much parsing work stays on your side. The vehicle record is intended to cover make, model, year, mileage, price, color, body type, dealer information and the photo gallery. Dealer records are intended to cover dealer name, address, contact details and inventory size. Price-trend work relies on repeated snapshots per make, model and year combination over time, so plan a storage key that lets you line up the same vehicle or dealer cohort across periods. Confirm the exact field names against the extraction rules you configure before you build downstream schemas on them. Three common jobs map onto those fields: Vehicle detail collection — build a catalogue of listings with price, mileage, year and dealer attached. Dealer-network mapping — group listings by dealer and location to see who holds which inventory. Price-trend tracking — store snapshots on a schedule and compare the same make/model/year across periods. If you only need a visual check of how a page renders in a browser, a full-page screenshot option is also described; treat it as a supplementary record rather than a substitute for structured fields.
Request controls that change the result
The documented workflow sends a Webmotors URL to the API by POST or GET. Beyond the URL, four controls matter most: - render_js — set to true to have the page run in a headless browser and return post-render HTML. Use this when listing content is injected by JavaScript. - stealth_proxy — enable when a target becomes aggressive about blocking; it is documented as routing the request through residential proxies. - country_code — route through a residential IP in a chosen country, useful when content varies by geography. - extract_rules or ai_extract_rules — request parsed JSON. extract_rules maps CSS selectors to field names; ai_extract_rules takes a natural-language specification instead. The dashboard is described as offering a request builder: paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. That is the no-code path for testing before committing to an integration; verify that your account tier includes it before relying on it.
Decision checklist before you build
Use this to pick the right output mode and avoid rework:
- Does the listing content appear without JavaScript? If not, plan on
render_js=trueand budget the extra credits. - Do you need raw HTML for your own parser? Choose the default HTML response and parse on your side.
- Do you need a stable schema? Use
extract_ruleswith CSS selectors mapped to field names. - Is the schema still changing? Use
ai_extract_ruleswith a natural-language spec and iterate on the prompt rather than on selectors. - Does the target throttle aggressive patterns? Space out requests or use multiple sessions; the documented limit model is concurrency per plan, not a per-target rate limit.
- Does content differ by country? Set
country_codeand confirm the returned page reflects the expected market. - Do you need a visual record? Capture a full-page screenshot alongside the data.
Field and control map
The table below pairs each returned field group with the request control that most affects it. It is a reading aid, not a schema guarantee — confirm field names against the extraction rules you configure.
| Returned field group | Typical request control |
|---|---|
| Make, model, year, mileage, price, color, body type | extract_rules or ai_extract_rules |
| Dealer name, address, contact info, inventory size | extract_rules or ai_extract_rules |
| Photo gallery | extract_rules or ai_extract_rules |
| Post-render HTML | render_js=true |
| Geo-specific content | country_code |
| Blocked or challenged pages | stealth_proxy |
| Visual record | Full-page screenshot option |
Worked example: one make/model/year price snapshot
Suppose you want to track a single model across dealers. A practical loop is: 1. Request a Webmotors search or listing URL filtered to the make, model and year you care about. 2. Ask for parsed JSON via extract_rules (stable selectors) or ai_extract_rules (natural-language spec). 3. Store each returned listing with its price, mileage, year, dealer name and dealer location. 4. Repeat on a schedule and compare the same make/model/year across snapshots. Because each call is designed to fetch the page rather than serve a cached copy, the comparison is between snapshots you stored. That distinction matters for residual-value modelling: a price change is only meaningful if the underlying listing is the same vehicle or the same dealer cohort. Keep a listing identifier or URL alongside each record so you can tell a genuine price move from a new listing.
How credits are consumed
Requests start at one credit each. Enabling JavaScript rendering raises a successful request to five credits. Enabling premium proxies costs ten or twenty-five credits depending on whether JavaScript rendering is also on. API credits are valid for one month and do not roll over. Concurrency is the number of requests that can be sent at the same time, and it is set per plan rather than per target.
The practical implication: a JavaScript-rendered, premium-proxy request is the most expensive combination, so reserve it for pages that genuinely need both. Plain HTML requests are the cheapest way to test a URL before adding rendering or proxy options.
Plan and pricing details
Plan names, monthly prices, credit allowances, concurrency levels, support tiers and any trial or cancellation terms are commercial commitments that must come from the account owner. They are not asserted on this page. The owner-input template below preserves every relevant clause so the final copy can be filled in without inventing figures. - Plan name: [to be supplied by the account owner] - Monthly price: [to be supplied by the account owner] - Included API credits: [to be supplied by the account owner] - Concurrent requests: [to be supplied by the account owner] - JavaScript rendering included: [to be supplied by the account owner] - Rotating and premium proxies included: [to be supplied by the account owner] - Geotargeting included: [to be supplied by the account owner] - Screenshots and extraction rules included: [to be supplied by the account owner] - Priority email support: [to be supplied by the account owner] - Dedicated account manager: [to be supplied by the account owner] - Team management: [to be supplied by the account owner] - Free trial credits: [to be supplied by the account owner] - Credit card required for trial: [to be supplied by the account owner] - Cancellation terms: [to be supplied by the account owner] - VAT treatment: [to be supplied by the account owner] - Enterprise contact route: [to be supplied by the account owner]
Webmotors scraping: frequently asked questions
Frequently asked questions
Will I get blocked when scraping Webmotors?
When residential proxy rotation and headless rendering are enabled, requests are designed to resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request. Confirm the current proxy and rendering behaviour against the documentation before you rely on it for a production pipeline.
Can I scrape Webmotors without writing code?
Yes, if your account includes the dashboard request builder. It lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. Check your plan's feature list to confirm the builder is available to you.
How do I handle JavaScript when scraping Webmotors?
Pass render_js=true on the request. When rendering is enabled, the page runs in a headless browser, the JavaScript executes server-side, and the post-render HTML is returned. Verify the current rendering behaviour in the documentation before depending on it for JavaScript-heavy listing pages.
Can I scrape Webmotors from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography. Confirm which countries are supported on your plan before building geo-specific logic.
What is the rate limit for scraping Webmotors?
The documented limit model is concurrency per plan, not a per-target rate limit. If the target throttles aggressive patterns, space out requests or use multiple sessions. Check your plan's concurrency allowance before sizing a batch job.
How do I get structured JSON from Webmotors?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. When extraction is configured, the response comes back as parsed JSON. Validate the returned field names against your own schema before building downstream pipelines on them.