MASV Python API Docs | dltHub
Build a MASV-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The MASV API allows for custom workflows to send and receive files, with RESTful web API support for MASV Agent. Authentication is handled via REST API calls. MASV Agent can be run locally or in the cloud. The REST API base URL is https://api.massive.app/v1/ and API keys (recommended) and JSON Web Tokens (package/user tokens) are used for authorization..
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 MASV data in under 10 minutes.
What data can I load from MASV?
Here are some of the endpoints you can load from MASV:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| teams_api_keys | /teams/{team_id}/api_keys | GET | (top-level array) | List API keys for a team (returns array of api key objects). |
| teams_packages | /teams/{team_id}/packages | GET | (top-level array) | List packages (sent/received) for a team (returns array of packages). |
| packages_get | /packages/{package_id} | GET | (object) | Get package metadata (single package object; includes access_token). |
| package_links | /packages/{package_id}/links | GET | (top-level array) | List links on a package (returns array of link objects). Requires X-Package-Token header. |
| api_keys_get | /api_keys/{api_key_id} | GET | (object) | Get single API key metadata (object). |
| packages_files | /packages/{package_id}/files | GET | (top-level array) | List files in a package (returns array of file objects). |
How do I authenticate with the MASV API?
Requests use API keys or JWTs in request headers. Supply an API key in the X-API-KEY header for most user-level endpoints; some management endpoints require a user JWT in X-User-Token. Package-scoped operations (links, downloads) require a package JWT in X-Package-Token.
1. Get your credentials
- Log in to the MASV web app (your account/team). 2. Create a Web Token (user JWT) if needed for API key management (generate via user auth flows in the dashboard or API). 3. Create an API key for your team via POST /teams/{team_id}/api_keys (requires X-User-Token). The response contains the
keyvalue — store this as your API key. 4. For package-specific actions, obtain the packageaccess_token(access_token property) from package responses.
2. Add them to .dlt/secrets.toml
[sources.masv_api_source] api_key = "your_api_key_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 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 MASV 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 masv_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline masv_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset masv_api_data The duckdb destination used duckdb:/masv_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline masv_api_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 teams_packages and package_links from the MASV 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 masv_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.massive.app/v1/", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "teams_packages", "endpoint": {"path": "teams/{team_id}/packages"}}, {"name": "package_links", "endpoint": {"path": "packages/{package_id}/links"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="masv_api_pipeline", destination="duckdb", dataset_name="masv_api_data", ) load_info = pipeline.run(masv_api_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("masv_api_pipeline").dataset() sessions_df = data.teams_packages.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM masv_api_data.teams_packages LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("masv_api_pipeline").dataset() data.teams_packages.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 MASV 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 MASV?
Request dlt skills, commands, AGENT.md files, and AI-native context.