Webmotors Car Listing

Affiliate disclosure: Apify Store links in this README use the fpr=aiagentapi referral parameter, which may attribute a signup or purchase without changing your price.

Webmotors Car Listing is a Brazil vehicle inventory API that searches public Webmotors results by keyword and publishes source-linked records in one normalized 35-field Dataset.

• Automatic Webmotors source lock: every focused run is restricted to the named marketplace.
• Three-field public input: country, keyword, and a result ceiling are the complete user-facing contract.
• Official inventory pages: records are accepted from Webmotors cards, structured data, or verified /comprar/ links.
• 35 documented output fields: values absent from a source result remain empty instead of becoming inferred facts.

Run a one-result test · View API

For the smallest test, use Toyota, set max_results to 1, and budget at most $0.02300 on the FREE tier for one result plus Actor Start. Verify source_url before using a price or vehicle fact. The intended Store and API pages were not live during the July 21, 2026 audit, so publication remains a release prerequisite.

What does Webmotors Car Listing do?

Webmotors Car Listing converts a vehicle keyword into a public Webmotors inventory path, requests the official page, and publishes qualifying vehicle records. It recognizes vehicle cards, structured JSON-LD entries, and Webmotors detail links containing /comprar/. A record can include a source title, numeric or formatted price, BRL currency, image, Webmotors listing ID, Brazil attribution, platform name, and direct source URL when those values appear in the search response.

The Actor intentionally uses a focused public input. Brazil is the only country, and the runtime has only one compatible source for that country: Webmotors. There is no platform field to forget and no location control that the current adapter cannot natively honor.

The Actor is not affiliated with Webmotors. It collects publicly accessible search-result information; it is not an inspection, valuation guarantee, ownership-history report, financing offer, or private dealer database. Listings, prices, and availability can change after collection, so important decisions require source-page verification.

How do I run Webmotors Car Listing?

1. Open the Webmotors Car Listing input page.
2. Keep country set to Brazil and enter a make or model phrase such as Toyota.
3. Set max_results to 1 for the first run and click Start.
4. Confirm that platform is Webmotors and open source_url before increasing the ceiling.

Use this same scenario in the Console, API, or an Apify integration:

{
  "country": "Brazil",
  "keyword": "Toyota",
  "max_results": 1
}

The keyword is trimmed and converted into the source inventory path without adding a location. max_results is a maximum number of publishable records, not guaranteed inventory. A blocked, changed, or empty source page can produce fewer results.

What data does Webmotors Car Listing return?

Every published item uses the same 35-field Dataset contract. Search pages often expose only a subset; unobserved values remain empty.

Field group	Public fields	Meaning
Listing identity	title, listing_id, vin, description	Webmotors title, source identifier, and text when present.
Images	main_image, images	Primary image and image collection when exposed.
Price	price, currency, price_text	Parsed amount, BRL or source currency, and formatted price text.
Vehicle identity	year, make, model, trim, condition	Source-published model and condition values.
Specifications	mileage, mileage_unit, body_type, fuel, transmission, engine, drive_type, exterior_color, interior_color	Optional search-card or structured-data details.
Seller and market	seller, seller_type, location, country, platform	Seller context, geography, and route attribution when available.
Links and dates	source_url, platform_url, official_url, posted_at, updated_at	Listing traceability and source timestamps.
Processing	processor, processed_at	Actor attribution and UTC processing time.

This abbreviated example illustrates the normalized contract rather than a guaranteed live listing:

{
  "main_image": "https://example.com/webmotors/toyota-corolla.jpg",
  "title": "Toyota Corolla 2.0 Flex",
  "price": 119990,
  "currency": "BRL",
  "year": 2021,
  "make": "Toyota",
  "model": "Corolla",
  "mileage": 56635,
  "mileage_unit": "km",
  "country": "Brazil",
  "platform": "Webmotors",
  "source_url": "https://www.webmotors.com.br/comprar/example/123456",
  "listing_id": "123456",
  "processor": "https://apify.com/username/actor_name",
  "processed_at": "2026-07-21T12:00:00Z"
}

Apify Datasets can be retrieved in the formats supported by the current Dataset items API, including JSON, JSONL, CSV, Excel, XML, HTML, and RSS.

What inputs can I configure?

Input	Type	Required	Accepted value and effect
country	string	Yes	Brazil, the only public country and the route to Webmotors.
keyword	string	Yes	A non-empty vehicle make, model, or phrase sent without translation or replacement.
max_results	integer	Yes	From 1 to 10,000; the maximum number of Webmotors records published.

All three fields are required by the current runtime. The schema supplies convenient prefill values, but the Actor respects the submitted keyword and result ceiling.

There is no public platforms field because the runtime locks this Actor to Webmotors before routing. There is no public location field because the adapter builds a countrywide inventory URL and does not apply a user location to the native request. Removing controls that have no useful effect makes the Store form safer and easier to understand.

What platforms and markets does Webmotors Car Listing cover?

This Actor covers public Webmotors vehicle inventory in Brazil. The audited adapter begins from a URL such as the official Toyota inventory page, validates that the response contains Webmotors purchase links, and parses unique detail destinations.

The route does not claim every vehicle, category, city, seller, or Webmotors feature. Availability depends on the live keyword page, source markup, network response, and qualifying records. Fields visible only after interaction or on a separate detail view may not be present in a search-result item.

For cross-country or multi-marketplace research, use Global Car Listing. Do not pass an old online result as proof of current Webmotors inventory; rerun the Actor and inspect current links.

Why use Webmotors Car Listing?

Verified capability	Practical benefit
Single Brazil route	The focused Actor cannot silently mix another marketplace into a normal run.
Native keyword inventory path	Keep source search semantics without inventing extra filters.
Normalized 35-field Dataset	Store repeated exports in stable columns even when values are optional.
Direct /comprar/ links	Review the original Webmotors record before relying on a vehicle or price.
Per-result billing	Associate most cost with items actually written to the Dataset.

The key trade-off is search-page depth. The Actor publishes what it can verify from the inventory response; it does not promise every detail available elsewhere on Webmotors.

Who is Webmotors Car Listing for?

Webmotors Car Listing is designed for developers, Brazil automotive analysts, dealer researchers, pricing teams, inventory monitors, and data operations specialists. Useful workflows include make/model inventory samples, asking-price comparisons, listing discovery, repeat keyword checks, source-link review queues, spreadsheet exports, and scheduled internal market snapshots.

It is not a substitute for a licensed vehicle inspection, official registration record, financial advice, dealer consent workflow, or guaranteed comprehensive feed. Teams needing every source-specific detail should evaluate a dedicated integration and its legal or contractual requirements.

How can I use Webmotors Car Listing through the API or MCP?

The intended owner/name identifier is truefetch/webmotors-car-listing. The public Store API returned no current record for that identifier on July 21, 2026, so this README does not invent a numeric Actor ID or live usage statistics.

After publication, the synchronous endpoint can return Dataset items directly:

curl -L "https://api.apify.com/v2/actors/truefetch~webmotors-car-listing/run-sync-get-dataset-items?maxItems=1" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer <APIFY_TOKEN>" \
  -d '{
    "country": "Brazil",
    "keyword": "Toyota",
    "max_results": 1
  }'

See the official synchronous Actor run endpoint for current authentication, timeout, and charge-limit options.

Apify documents a hosted Streamable HTTP MCP server:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=actors,docs"
    }
  }
}

After publication, ask the MCP client to locate truefetch/webmotors-car-listing, inspect the input schema, run the one-result Toyota scenario, and return the Dataset item. Authentication is required to run Actors. Review the Apify MCP guide.

How much does Webmotors Car Listing cost?

The Actor uses pay-per-event pricing. Actor Start is charged once at run start; a result event is charged for every item written to the default Dataset.

Billed event and tier	Price per event	Billing unit
Actor Start	$0.01000	One Actor run start.
Result - FREE	$0.01300	One published Dataset item.
Result - BRONZE	$0.01257	One published Dataset item.
Result - SILVER	$0.01213	One published Dataset item.
Result - GOLD	$0.01170	One published Dataset item.
Result - PLATINUM	$0.01170	One published Dataset item.
Result - DIAMOND	$0.01170	One published Dataset item.

On the FREE tier, one result costs $0.01000 + $0.01300 = $0.02300. A run with no published records can still incur Actor Start. Actual totals depend on published items and the applicable tier. Confirm pricing on the live Store page after publication.

How does Webmotors Car Listing compare with alternatives?

Option	Best fit	Trade-off
Webmotors Car Listing	Repeatable Brazil Webmotors discovery with normalized output.	Search pages may expose fewer fields than detail pages.
Global Car Listing	Multi-country or multi-source automotive research.	Its broader form and routing are unnecessary for a Webmotors-only task.
Manual Webmotors browsing	One-off inspection with full page context.	Difficult to schedule, export, and compare at scale.
Dedicated native integration	Teams requiring all Webmotors-specific fields or workflows.	More implementation, monitoring, and normalization work.

Choose the focused Actor when source-linked search results and a stable cross-run schema are more important than capturing every native field.

What are the limits and troubleshooting steps?

Symptom or limit	Explanation and next step
The run returns fewer records than requested	max_results is a ceiling; live inventory and parseable detail links control output.
Optional fields are empty	Search cards and structured data do not expose every shared schema field. Open source_url.
The input rejects another country	Brazil is the only public market for this focused Actor.
No location field appears	The adapter performs a countrywide keyword inventory request and has no native user-location parameter.
A source page is blocked or changed	Webmotors can change firewall behavior or markup; retry later and provide a public failing URL to support.
An older record no longer exists	Listings are mutable; treat old output as historical and rerun for current inventory.

For reproducible support, send the run ID, exact input, expected behavior, and one public source URL. Do not include API tokens or private data.

Frequently asked questions

Which inputs are required?

country, keyword, and max_results are all required.

Is Webmotors selected automatically?

Brazil has only one compatible route in the audited runtime, so the run resolves to Webmotors without a platform field.

Can I filter by city?

Not with the current public schema. The adapter builds a countrywide inventory URL from the keyword.

Does max_results guarantee inventory?

No. It limits published items but cannot create or preserve source listings.

Why are some fields empty?

The normalized schema is broader than the values exposed by an individual search result.

Can I schedule runs?

Yes. Keep the exact country and keyword inputs with the schedule and compare current source links.

How is billing counted?

One result event is charged per Dataset item, plus the separate Actor Start event.

Are old Store metrics current proof?

No. The user identified online data as old, and this audit relies on local runtime evidence and current official source behavior instead.

Related TrueFetch Actors

• Global Car Listing supports multi-country and multi-source vehicle research.
• 28car Car Listing focuses on Hong Kong vehicle classifieds.
• Mobile DE Car Listing targets German mobile.de inventory.

These related directories were verified locally. Their public links must be checked again after each Actor is published.

Support and last updated

• Store: Webmotors Car Listing
• API: Webmotors Car Listing API
• Source: Webmotors Toyota inventory
• Apify help: Apify documentation
• Community: TrueFetch Telegram group
• Direct support: AiAgentApi support

Verified against local schemas, pricing metadata, source-lock regression evidence, and the public Webmotors inventory surface on July 21, 2026. Local Webmotors-only routing passes; unresolved prepublication Store/API and related-Actor links remain release blockers.

Test one Webmotors result · Review the API surface