Filesdotcom Python API Docs | dltHub

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

Last updated:

Files.com is a cloud file storage and sharing platform that provides a REST API for managing files, users, and other resources. The REST API base URL is https://{subdomain}.files.com/api/rest/v1 and All requests require an API Key supplied in the X-FilesAPI-Key header or via 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 pip install "dlt[workspace]" and start loading Filesdotcom data in under 10 minutes.


What data can I load from Filesdotcom?

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

ResourceEndpointMethodData selectorDescription
users/usersGETList all users
users/users/{id}GETRetrieve a single user by ID
bundles/bundlesGETList all share‑link bundles
bundles/bundles/{id}GETRetrieve a specific bundle
sessions/sessionsGETList active sessions

How do I authenticate with the Filesdotcom API?

Provide the API Key in the X-FilesAPI-Key request header (or use HTTP Basic with the key as the username). No special payload is required besides the key.

1. Get your credentials

  1. Log in to your Files.com account.
  2. Click your profile avatar and choose Settings.
  3. In the settings menu, select API Keys.
  4. Click Generate New API Key, give it a name, and copy the generated key.
  5. Store the key securely; it will be used as the value for the X-FilesAPI-Key header.

2. Add them to .dlt/secrets.toml

[sources.filesdotcom_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 Filesdotcom 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 filesdotcom_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline filesdotcom_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 users and bundles from the Filesdotcom 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 filesdotcom_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{subdomain}.files.com/api/rest/v1", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "users", "endpoint": {"path": "users"}}, {"name": "bundles", "endpoint": {"path": "bundles"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="filesdotcom_pipeline", destination="duckdb", dataset_name="filesdotcom_data", ) load_info = pipeline.run(filesdotcom_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("filesdotcom_pipeline").dataset() sessions_df = data.users.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM filesdotcom_data.users LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("filesdotcom_pipeline").dataset() data.users.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 Filesdotcom 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.


Troubleshooting

Authentication Errors

If the X-FilesAPI-Key header is missing or the key is invalid, the API returns a 401 Unauthorized response.

Pagination Quirks

List endpoints use cursor‑based pagination. The response includes the header X-Files-Cursor-Next for the next page and X-Files-Cursor-Prev when a cursor is supplied. Use the cursor query parameter to retrieve subsequent pages, respecting the per_page limit (default 1,000, max 10,000).

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.


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 Filesdotcom?

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