Mobile.de Python API Docs | dltHub

Build a Mobile.de-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

mobile.de provides a suite of REST APIs for managing vehicle inventory, searching ads, and accessing insights and lead data for the mobile.de platform. The REST API base URL is https://services.mobile.de and All requests require HTTP Basic authentication..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Mobile.de data in under 10 minutes.


What data can I load from Mobile.de?

Here are some of the endpoints you can load from Mobile.de:

ResourceEndpointMethodData selectorDescription
leads/lead-api/sellers/
/events
GETeventsGet lead updates for a dealer using cursor pagination
seller_ads/seller-api/sellers/
/ads
GETRetrieve a list of ads for a specific seller
seller_details/seller-api/sellers/
GETRetrieve details for a specific seller
seller_feature_settings/seller-api/sellers/
/feature-settings
GETRetrieve feature settings for a specific seller
search_ads/search-api/searchGETSearch and retrieve ads based on parameters
ad_details/search-api/ad/{ad-key}GETFetch single ad by key

How do I authenticate with the Mobile.de API?

The API uses HTTP Basic authentication. Requests must include an 'Authorization' header with the value 'Basic ' followed by a Base64-encoded string of 'username

'.

1. Get your credentials

Mobile.de does not provide a self-service dashboard for API key generation. To obtain API credentials, follow these steps: 1. Identify your account type: API-Account (for general API access) or Dealer-Account (for dealer-specific integrations). 2. For an API-Account, request access by sending an email to service@team.mobile.de, including your project details and requirements, and specify whether you need access to the API Sandbox environment or production. 3. For a Dealer-Account, credentials can typically be generated or retrieved directly within the Dealer-Area of your mobile.de account. 4. Once your request is processed, Customer Support will provide your unique username and password. The API uses HTTP Basic Authentication.

2. Add them to .dlt/secrets.toml

[sources.mobile_de_source] mobile_de_username = "your_username_here" mobile_de_password = "your_password_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Mobile.de API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python mobile_de_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline mobile_de_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset mobile_de_data The duckdb destination used duckdb:/mobile_de.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads search-api/ad/{ad-key} and seller-api (base URL) from the Mobile.de API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def mobile_de_source(credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://services.mobile.de", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": credentials}, }, "resources": [ {"name": "leads", "endpoint": {"path": "lead-api/sellers/:mobileSellerId/events", "data_selector": "events"}}, {"name": "seller_ad_images", "endpoint": {"path": "seller-api/sellers/:mobileSellerId/ads/:mobileAdId/images", "data_selector": "images"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mobile_de_pipeline", destination="duckdb", dataset_name="mobile_de_data", ) load_info = pipeline.run(mobile_de_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("mobile_de_pipeline").dataset() sessions_df = data.leads.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM mobile_de_data.leads LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("mobile_de_pipeline").dataset() data.leads.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Mobile.de data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Mobile.de?

Request dlt skills, commands, AGENT.md files, and AI-native context.