deprecated

Mobile DE API is a mobile.de api that searches public mobile.de inventory in Germany by vehicle phrase and optional postcode and returns 37 normalized fields with EUR prices and source URLs.

• The runtime is locked to mobile.de and Germany.
• An optional German postcode applies the source's 50 km request radius.
• Listing rows can carry price, year, mileage, seller, and direct detail links.
• The 37-field schema preserves absent source values as empty rather than inferred.

Run a one-result test · View API

Set max_results to 1 for the smallest useful test. Billing includes Actor Start and only the result rows actually written to the default Dataset.

What does Mobile DE API do?

Mobile DE API turns a public vehicle search into structured Dataset rows for Germany through public mobile.de vehicle inventory. It accepts the current schema inputs, follows the edition's routing rules, and writes source-linked records that can move directly into JSON, CSV, Excel, a database, or another Apify workflow.

mobile.de's official search FAQ documents detailed vehicle criteria, location-aware results, mileage, price, first registration, and links from result lists to full advertisements. See the official mobile.de search and buying FAQ.

The Actor is a collection and normalization tool, not a vehicle-history report, appraisal, inspection, financing decision, or guarantee of current stock. Important commercial facts should be checked on source_url, because listings and catalog pages can change after collection.

How do I run Mobile DE API?

Run Mobile DE API by starting with its prefilled scenario, reviewing one source-linked row, and increasing scope only after the data matches the intended workflow.

1. Open the Mobile DE API input page and review every required value.
2. Set country to Germany, keyword to Toyota Camry, and max_results to 50; for the smallest risk test, temporarily use max_results: 1.
3. Start the Actor and wait for the default Dataset.
4. Open source_url from a returned row before expanding the result ceiling or scheduling repeats.

{
  "max_results": 50,
  "country": "Germany",
  "keyword": "Toyota Camry"
}

The result limit is a ceiling rather than a promise. Live inventory, source access, unique listing URLs, and the fields available on each page determine how many records can be published.

What data does Mobile DE API return?

Mobile DE API returns one object per source record using exactly 37 public fields. Values unavailable from the source remain empty; the Actor does not derive a VIN, seller, mileage, location, or vehicle specification from the keyword.

Field group	Public fields	Meaning
Identity and price	main_image, title, price, currency, year, make, model, trim	Primary media, listing title, asking price, and vehicle identity.
Mileage and geography	mileage, mileage_unit, location, latitude, longitude, country	Odometer values and source-published place data.
Source and seller	platform, source_url, seller, seller_type	Marketplace attribution, original listing link, and public seller context.
Vehicle attributes	condition, body_type, seats, fuel, transmission, engine, drive_type, exterior_color, interior_color, vin	Source-published condition, dimensions, powertrain, colors, and identifiers.
Lifecycle and content	listing_id, posted_at, updated_at, description, images, price_text, official_url, processor, processed_at	Source identity, dates, descriptive content, additional links, and processing attribution.

This abbreviated illustrative item uses the same scenario; a real row follows the full 37-field schema.

{
  "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",
  "processed_at": "2026-08-10T08:04:05Z"
}

Apify Datasets support JSON, JSONL, CSV, Excel, XML, HTML, and RSS retrieval through the Dataset items API. Keep source_url and processed_at when exporting so later reviews retain both source provenance and collection time.

What inputs can I configure?

Mobile DE API exposes only inputs supported by its current runtime route, with required fields marked explicitly and no invented non-empty fallback for optional filters.

Input	Type	Required	Behavior	Example
max_results	integer	Yes	Maximum mobile.de records requested by the run.	50
country	string	Yes	Required market input; this edition accepts Germany.	"Germany"
keyword	string	Yes	Required make, model, or vehicle phrase preserved as submitted.	"Toyota Camry"
location	string	No	Optional German city or five-digit postcode; a resolved postcode applies a 50 km radius.	Omitted

The complete effective test input is formed from schema defaults overridden by prefills. API callers can replace those values, but must still send each required field with a schema-valid value.

What platforms and markets does Mobile DE API cover?

Mobile DE API covers Germany through public mobile.de vehicle inventory; coverage follows the source relationships registered for this edition rather than assumptions based on the Actor's title.

The edition covers mobile.de in Germany. It cannot be switched to another marketplace through input.

Omit location for a Germany-wide request. When location is supplied, it must resolve to a German postcode for the source-native 50 km filter.

Source inventory, language, seller-entered fields, and page availability change independently. The Dataset describes what was available when the run processed each record.

Why use Mobile DE API?

Mobile DE API is useful when a repeatable API and Dataset contract matters more than manually copying vehicle cards or maintaining a source-specific export parser.

Capability	Practical benefit
mobile.de-only routing	Keep source links and platform attribution consistent.
Optional postcode radius	Create regional samples using a native geographic request.
EUR, year, and mileage fields	Build price-versus-age or price-versus-odometer comparisons when values are present.
37-field Dataset	Retain a stable export contract while allowing nullable source fields.
API and MCP access	Run the same input from code, schedules, or an agent client.

The focused route provides consistent attribution and optional geography, while live source access and search-card field depth remain external constraints. This is why null handling and source-link retention are part of a reliable downstream design rather than cleanup tasks.

Who is Mobile DE API for?

Mobile DE API is designed for developers, German automotive analysts, dealer researchers, pricing teams, regional inventory monitors, and data operations specialists. It works for teams that need a reproducible input, structured output, and a review path back to each public source record.

Postcode-based inventory checks, make/model availability samples, EUR asking-price comparisons, mileage distributions, listing-link review queues, and recurring Germany snapshots are appropriate. Keep the exact keyword stable when comparing results over time.

Do not use it for inspections, registration history, seller consent, guaranteed valuation, private data, or a complete licensed replica of mobile.de. Vehicle purchases, lending, insurance, safety, and regulatory decisions require independent checks beyond a scraped public listing.

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

Mobile DE API has the public Actor ID i2fUsqPR5SPr2zU7g; the stable name form truefetch/mobile-de-api is also available for human-readable integrations.

i2fUsqPR5SPr2zU7g

This synchronous HTTP request uses the same scenario and returns Dataset items directly:

curl -L "https://api.apify.com/v2/acts/i2fUsqPR5SPr2zU7g/run-sync-get-dataset-items?maxItems=1" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer <APIFY_TOKEN>" \
  -d '{"max_results":50,"country":"Germany","keyword":"Toyota Camry"}'

Apify also provides a hosted Streamable HTTP MCP server:

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

After authentication, ask the MCP client to inspect Actor ID i2fUsqPR5SPr2zU7g, run the same input, and return the default Dataset rows. The Mobile DE API API page provides generated SDK and OpenAPI examples, while the Apify MCP guide documents current client setup.

How much does Mobile DE API cost?

Mobile DE API costs $0.00730 per result on the FREE tier plus $0.01000 per Actor Start event; memory determines the number of Start events at one per GB, minimum one.

Event or tier	Price	Billing unit
Actor Start	$0.01000	Per GB of Actor memory, minimum one event.
Result — FREE	$0.00730	One item written to the default Dataset.
Result — BRONZE	$0.00657	One Dataset item.
Result — SILVER	$0.00584	One Dataset item.
Result — GOLD	$0.00548	One Dataset item.
Result — PLATINUM	$0.00548	One Dataset item.
Result — DIAMOND	$0.00548	One Dataset item.

Smallest-test calculation, assuming the minimum one Start event: $0.01000 Actor Start + 1 result × $0.00730 = $0.01730. A run that writes no row can still incur Actor Start. Check the live pricing page before budgeting a larger workflow because prices can change.

How does Mobile DE API compare with alternatives?

Mobile DE API is the best fit when its documented source and normalized contract match the job; broader, manual, or contractual approaches solve different problems.

Option	Best fit	Trade-off
Mobile DE API	Germany-focused mobile.de discovery with optional postcode scope.	Native attributes missing from result pages remain empty.
Car Listings API	Multi-source or multi-country vehicle research.	More input breadth than a mobile.de-only workflow needs.
Manual mobile.de search	A one-time purchase review with complete interactive context.	Not convenient for automated export and monitoring.
A contractual marketplace feed	Guaranteed access terms or every native field.	Separate agreement, credentials, and data model.

No option eliminates the need to verify a mutable vehicle advertisement before a purchase or other high-impact decision.

What are the limits and troubleshooting steps?

Mobile DE API depends on public source responses, so troubleshooting begins with the exact input, the current source page, and whether the default Dataset contains a row.

Symptom or limit	Explanation and next step
A postcode is rejected	Use a valid five-digit German postcode or omit location for a countrywide request.
No rows are returned	Live source access can change. Confirm the query on mobile.de, retry later, and report a reproducible run ID if it persists.
Fewer rows than requested	max_results is a ceiling and cannot create unique live advertisements.
Optional values are empty	Search results may not expose every normalized field; inspect source_url.
A saved detail link disappears	The seller may remove or update the advertisement. Treat prior output as historical.

For a reproducible report, use max_results: 1, include the run ID and exact input, and add one public source URL when available. Never include an Apify token, private seller data, or credentials in an Issue.

Frequently asked questions

Which inputs are required?

max_results, country, and keyword are required. location is optional.

Is this a mobile.de car listings api?

Yes. It returns normalized rows from public mobile.de vehicle results through Apify endpoints.

Can I use it as a germany used car listings api?

Yes for mobile.de-sourced public inventory; it is not a government registration or vehicle-history API.

What location should I enter?

Use a German city or five-digit postcode. A resolved postcode applies a 50 km source radius.

Is there a free Germany car API?

The Actor uses pay-per-event pricing, although a small run may fit within your Apify account allowances.

Can I schedule runs to monitor mobile.de listings over time?

Yes. Keep keyword and optional postcode stable, then compare price, mileage, listing ID, and source URL across Datasets.

Why can a valid query return no rows?

Marketplace access, live inventory, and page responses can change independently of the Actor.

Related TrueFetch Actors

Three TrueFetch Actors cover the closest adjacent vehicle markets without duplicating this Actor's exact source scope.

• Car Listings API — Use it for multi-source country-aware research.
• Autohome API — Use it for Mainland China catalog records.
• Webmotors API — Use it for public Brazil inventory.

Support

Use the Store page for the input, the API page for generated integration examples, and Issues for a reproducible bug. Discuss vehicle-data workflows in the TrueFetch community on Telegram.

Run a focused Mobile DE API test · Open the Mobile DE API API

Last Updated: August 10, 2026