Mobile DE 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.

Mobile DE Car Listing is a source-locked Germany vehicle inventory API that searches mobile.de by keyword and optional postal area and publishes a normalized 35-field Dataset.

• Germany-only public country: the focused input cannot route to unrelated international vehicle markets.
• Automatic mobile.de source lock: every focused run is restricted to the named marketplace.
• Native postal-radius support: a resolved German postcode applies mobile.de's 50 km search radius.
• 35 documented output fields: unsupported source values remain empty instead of becoming inferred vehicle facts.

Run a one-result test · View API

For the smallest controlled test, set max_results to 1 and budget at most $0.02250 on the FREE tier for one result plus Actor Start. Verify platform and source_url before scaling. The intended Store and API pages were not live during the July 21, 2026 audit, so publication remains a release prerequisite.

What does Mobile DE Car Listing do?

Mobile DE Car Listing sends a vehicle keyword to mobile.de's public car search and normalizes qualifying result links. The adapter recognizes official /fahrzeuge/details.html destinations, listing-card text, structured page data, price strings, first-registration years, and kilometre values. A published item can therefore contain a title, price, currency, year, mileage, Germany attribution, platform name, and direct source URL when those values are exposed by the live results page.

An optional location can be supplied as a German city or five-digit postcode. When location normalization produces a postcode, the adapter sends it to mobile.de with a 50 km radius. Without location, it performs a Germany-wide keyword search.

The runtime now locks this focused Actor to mobile.de before applying country, location, and query-capability checks. Its public schema contains no platform selector, and input cannot broaden a run to AutoScout24. Global Car Listing remains available for intentional multi-source Germany research.

The Actor is not affiliated with mobile.de. It is not an inspection, valuation guarantee, ownership-history service, financing offer, or private dealer database. Source records can change after collection.

How do I run Mobile DE Car Listing?

1. Open the Mobile DE Car Listing input page.
2. Keep country set to Germany and enter a vehicle phrase such as Toyota.
3. Optionally enter 10115 or another German location for a resolved 50 km postal radius.
4. Set max_results to 1, run the Actor, and confirm platform is mobile.de before increasing volume.

This source-locked example applies a Berlin postcode:

{
  "country": "Germany",
  "keyword": "Toyota",
  "location": "10115",
  "max_results": 1
}

The keyword is trimmed but not translated or expanded. max_results is the mobile.de run maximum, not guaranteed inventory. A source page can contain fewer unique, publishable detail links.

What data does Mobile DE Car Listing return?

Every item follows a 35-field shared Dataset schema. mobile.de search results usually expose a subset; missing values remain empty.

Field group	Public fields	Meaning
Listing identity	title, listing_id, vin, description	Source title, text, and identifiers when available.
Images	main_image, images	Primary image and image collection when published.
Price	price, currency, price_text	Parsed amount, EUR or source currency, and formatted price text.
Vehicle identity	year, make, model, trim, condition	First-registration year and source vehicle identity values.
Specifications	mileage, mileage_unit, body_type, fuel, transmission, engine, drive_type, exterior_color, interior_color	Kilometres and optional source-published specifications.
Seller and market	seller, seller_type, location, country, platform	Dealer or seller context, Germany, and route attribution.
Links and dates	source_url, platform_url, official_url, posted_at, updated_at	Listing traceability and source dates when exposed.
Processing	processor, processed_at	Actor attribution and UTC processing time.

This abbreviated record illustrates the contract without claiming a current listing:

{
  "title": "Toyota Corolla 2.0 Hybrid Touring Sports",
  "price": 23845,
  "currency": "EUR",
  "year": 2022,
  "make": "Toyota",
  "model": "Corolla",
  "mileage": 80895,
  "mileage_unit": "km",
  "location": "10115 Berlin",
  "country": "Germany",
  "platform": "mobile.de",
  "source_url": "https://suchen.mobile.de/fahrzeuge/details.html?id=example",
  "processor": "https://apify.com/username/actor_name",
  "processed_at": "2026-07-21T12:00:00Z"
}

Retrieve Datasets using 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	Germany, the only public country for this release.
keyword	string	Yes	A non-empty vehicle make, model, or phrase sent without translation.
location	string	No	German city or five-digit postcode; mobile.de uses a resolved postcode with a 50 km radius.
max_results	integer	Yes	From 1 to 10,000, applied to the source-locked mobile.de run.

The runtime requires country, keyword, and max results; location remains optional and has no non-empty default. Source selection is absent because this focused Actor enforces mobile.de and user input cannot override it.

If a supplied location cannot resolve to a postal code, mobile.de is rejected for that location rather than pretending to apply a geographic filter. For a countrywide search, omit location entirely.

What platforms and markets does Mobile DE Car Listing cover?

The public market is Germany. The named source is mobile.de Toyota inventory, where public result pages can show new and used vehicles, asking prices, first registration, mileage, fuel, dealer context, and detail links. The Actor publishes only the values it observes and normalizes.

The focused runtime admits only the mobile_de route. AutoScout24 remains available through Global Car Listing but is not selectable or reachable through this Actor.

This focused Actor does not cover other countries. For multi-market research, use Global Car Listing. Live listing count and field completeness can change independently of the Actor.

Why use Mobile DE Car Listing?

Verified capability	Practical benefit
Automatic mobile.de source lock	Keep platform attribution and detail links on the intended source without a user filter.
Germany-focused public schema	Prevent accidental routing to unrelated international marketplaces.
Optional postcode radius	Narrow mobile.de results using a source-native geographic request.
Normalized 35-field Dataset	Load repeated runs into stable columns even when fields are absent.
Direct source URLs	Verify the listing page before relying on price, mileage, or seller details.

The main trade-off is source specialization: the Actor is mobile.de-only and returns a normalized subset rather than every native marketplace field.

Who is Mobile DE Car Listing for?

Mobile DE Car Listing is intended for developers, German automotive analysts, dealer researchers, pricing teams, inventory monitors, and data operations specialists. Common uses include make/model inventory samples, regional asking-price comparisons, postcode-based listing discovery, scheduled keyword checks, source-link review queues, and normalized exports for internal dashboards.

It does not replace an inspection, registration record, independent valuation, seller consent workflow, or source-specific feed guaranteeing every native field. Use Global Car Listing when multiple Germany sources are required.

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

The intended owner/name identifier is truefetch/mobile-de-car-listing. The public Store API did not return a current record for that identifier on July 21, 2026, so no numeric Actor ID or legacy Store statistics are presented as current proof.

After publication, use the synchronous endpoint with the complete public input:

curl -L "https://api.apify.com/v2/actors/truefetch~mobile-de-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": "Germany",
    "keyword": "Toyota",
    "location": "10115",
    "max_results": 1
  }'

Consult the official synchronous Actor run endpoint for current authentication, timeout, and charge-limiting 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/mobile-de-car-listing, inspect its schema, run the one-result Toyota scenario, and retrieve the item. mobile.de is selected automatically. Authentication is required to run Actors. See the Apify MCP guide.

How much does Mobile DE Car Listing cost?

The Actor uses pay-per-event pricing. Actor Start is charged once at run start; one result event is charged for each record 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.01250	One published Dataset item.
Result - BRONZE	$0.01208	One published Dataset item.
Result - SILVER	$0.01167	One published Dataset item.
Result - GOLD	$0.01125	One published Dataset item.
Result - PLATINUM	$0.01125	One published Dataset item.
Result - DIAMOND	$0.01125	One published Dataset item.

On the FREE tier, one published mobile.de result costs $0.01000 + $0.01250 = $0.02250. A run with no records can still incur Actor Start. Each mobile.de record written to the default Dataset creates one result event. Confirm live pricing after publication.

How does Mobile DE Car Listing compare with alternatives?

Option	Best fit	Trade-off
Mobile DE Car Listing	Repeatable source-locked mobile.de research with normalized output and optional postcode radius.	Native fields absent from results remain empty.
Global Car Listing	Multi-country or multi-source automotive analysis.	Its broader scope is unnecessary for a mobile.de-only job.
Manual mobile.de browsing	One-off review with full source-page context.	Difficult to schedule, export, or compare repeatedly.
Dedicated native integration	Teams requiring every mobile.de-specific field.	More implementation, monitoring, and normalization work.

Choose this Actor when mobile.de-only normalized search results match the workflow. Use Global Car Listing for multi-source comparison.

What are the limits and troubleshooting steps?

Symptom or limit	Explanation and next step
A result identifies AutoScout24 or another source	Treat it as a source-lock regression; stop scaling and send the run ID plus source URL to support.
A location is rejected	It did not resolve to a German postcode required by the mobile.de postal filter. Try a five-digit postcode.
Fewer records arrive than requested	max_results is a ceiling; live inventory and unique detail links determine output.
Optional fields are empty	A search result does not expose every normalized vehicle field. Verify source_url.
A listing link no longer opens	Listings can be changed or removed after collection; rerun for current inventory.
Later pages stop early	A follow-up source request returned no usable page; retain completed records and retry later.

For support, send the run ID, exact input, expected platform, and one public source URL. Never send API tokens or private data.

Frequently asked questions

Which inputs are required?

country, keyword, and max_results are required. location is optional; no platform selector is exposed.

Can I select AutoScout24 instead?

No. This focused Actor is locked to mobile.de. Use Global Car Listing for AutoScout24 or multi-source Germany searches.

What location should I enter?

Use a German city or five-digit postcode. The resolved postcode is sent with a 50 km radius.

Can I run a countrywide search?

Yes. Omit location; the Actor remains locked to mobile.de.

Why are some fields empty?

The normalized schema is broader than the subset exposed on each mobile.de result card.

Can I schedule the Actor?

Yes. Scheduled inputs use the same four-field contract, and the Actor remains locked to mobile.de.

How is billing counted?

Each Dataset item triggers one result event; Actor Start is separate.

Are old online metrics current proof?

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

Related TrueFetch Actors

• Global Car Listing supports multi-country and multi-source vehicle research.
• Webmotors Car Listing focuses on Brazil inventory.
• 28car Car Listing focuses on Hong Kong vehicle classifieds.

These related project directories were verified locally. Their public links must be checked again after publication.

Support and last updated

• Store: Mobile DE Car Listing
• API: Mobile DE Car Listing API
• Source: mobile.de 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 mobile.de surface on July 21, 2026. Local mobile.de-only routing now passes; unresolved Store/API links remain a publication gate.

Test one mobile.de result · Review the API surface