Smartcar Python API Docs | dltHub

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

Last updated:

Smartcar is a platform that allows applications to retrieve vehicle data, issue commands, and manage vehicle connections via a REST API. The REST API base URL is https://vehicle.api.smartcar.com/v3 and all requests require an access token passed as a Bearer token in the Authorization header.

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 Smartcar data in under 10 minutes.


What data can I load from Smartcar?

Here are some of the endpoints you can load from Smartcar:

ResourceEndpointMethodData selectorDescription
connections/connectionsGETconnectionsList all vehicles connected to your application
connection/connections/{vehicleId}GETGet details about a specific vehicle connection
vehicle/vehicles/{vehicleId}GETGet attributes of a specific vehicle
vehicle_signals/vehicles/{vehicleId}/signalsGETRead all signals for a vehicle
webhooks/webhooks/{webhookId}/subscriptionsGETList all vehicles subscribed to a webhook

How do I authenticate with the Smartcar API?

Smartcar uses OAuth 2.0 Client Credentials flow for server-to-server communication, requiring an access token in the Authorization header as a Bearer token. Additionally, the sc-user-id header is required for requests accessing specific vehicle data or signals.

1. Get your credentials

To obtain your Smartcar API credentials, log in to the Smartcar Dashboard (dashboard.smartcar.com). Select your application from the dashboard, navigate to the API Credentials tab, and click Create Secret. The system will generate a Client ID and a Client Secret. Note that the Client Secret is only displayed once, so ensure you store it immediately in a secure location, such as a secrets manager or environment variables. You can manage up to 3 active secrets simultaneously for rotation purposes.

2. Add them to .dlt/secrets.toml

[sources.smartcar_source] SMARTCAR_CLIENT_ID = "your_client_id_here" SMARTCAR_CLIENT_SECRET = "your_client_secret_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 Smartcar 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 smartcar_pipeline.py

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

Pipeline smartcar_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset smartcar_data The duckdb destination used duckdb:/smartcar.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 /connections and /oauth2/token from the Smartcar 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 smartcar_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://vehicle.api.smartcar.com/v3", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "connections", "endpoint": {"path": "connections", "data_selector": "connections"}}, {"name": "batch", "endpoint": {"path": "batch", "data_selector": "responses"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="smartcar_pipeline", destination="duckdb", dataset_name="smartcar_data", ) load_info = pipeline.run(smartcar_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("smartcar_pipeline").dataset() sessions_df = data.connections.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM smartcar_data.connections LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("smartcar_pipeline").dataset() data.connections.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 Smartcar 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 Smartcar?

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