Traccar Python API Docs | dltHub
Build a Traccar-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Traccar's REST API allows access to its GPS tracking server functionalities. The API documentation is available at https://www.traccar.org/api-reference/. To use it, a server instance is required. The REST API base URL is https://{host}:{port}/api (examples: https://demo.traccar.org/api, https://server.traccar.org/api) and all requests require either HTTP Basic auth, a session cookie, or a user token.
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 pip install "dlt[workspace]" and start loading Traccar data in under 10 minutes.
What data can I load from Traccar?
Here are some of the endpoints you can load from Traccar:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| server | /server | GET | Fetch server information (single JSON object) | |
| session | /session | GET, POST | Retrieve or create a session; POST returns a User object and sets a cookie | |
| devices | /devices | GET | List of device objects (top‑level array) | |
| users | /users | GET | List of user objects (top‑level array) | |
| positions | /positions | GET | List of position objects (top‑level array) | |
| reports | /reports | GET | Various report endpoints returning lists | |
| events | /events | GET | List of event objects |
How do I authenticate with the Traccar API?
Traccar supports HTTP Basic auth (email:password), session‑based auth via POST /api/session that returns a session cookie, or a user token passed as a query parameter.
1. Get your credentials
- Log in to your Traccar web application (demo or self‑hosted). 2. Use your email and password for HTTP Basic authentication. 3. To create a user token, open your profile in the web UI and generate a token, or call the API to create one. 4. Optionally, obtain a session cookie by POSTing email and password to /api/session.
2. Add them to .dlt/secrets.toml
[sources.traccar_source] auth = { username = "your_email@example.com", password = "your_password" } # or for token usage # auth = { token = "your_user_token" }
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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt 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:
dlt ai toolkit rest-api-pipeline install
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 Traccar 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:
python traccar_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline traccar_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset traccar_data The duckdb destination used duckdb:/traccar.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline traccar_pipeline 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 positions and devices from the Traccar 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 traccar_source(auth=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{host}:{port}/api (examples: https://demo.traccar.org/api, https://server.traccar.org/api)", "auth": { "type": "http_basic", "password": auth, }, }, "resources": [ {"name": "positions", "endpoint": {"path": "positions"}}, {"name": "devices", "endpoint": {"path": "devices"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="traccar_pipeline", destination="duckdb", dataset_name="traccar_data", ) load_info = pipeline.run(traccar_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("traccar_pipeline").dataset() sessions_df = data.positions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM traccar_data.positions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("traccar_pipeline").dataset() data.positions.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 Traccar data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Traccar?
Request dlt skills, commands, AGENT.md files, and AI-native context.