Freesound Python API Docs | dltHub

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

Last updated:

The Freesound API allows developers to browse, search, and retrieve metadata about sounds, users, and packs, as well as upload or manage content. The REST API base URL is https://freesound.org/apiv2 and API calls support token-based authentication (via query parameter) or OAuth2 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 Freesound data in under 10 minutes.


What data can I load from Freesound?

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

ResourceEndpointMethodData selectorDescription
search/apiv2/search/text/GETresultsSearch sounds by query
sound/apiv2/sounds/<sound_id>/GETRetrieve detailed sound information
sound_analysis/apiv2/sounds/<sound_id>/analysis/GETRetrieve audio analysis features
sound_comments/apiv2/sounds/<sound_id>/comments/GETresultsRetrieve sound comments
user/apiv2/users//GETRetrieve user information
pack_sounds/apiv2/packs/<pack_id>/sounds/GETresultsRetrieve list of sounds in a pack

How do I authenticate with the Freesound API?

For token-based authentication, append the API key as a query parameter named 'token' to all requests. OAuth2 authentication involves an authorization code grant flow that provides an access token for subsequent requests.

1. Get your credentials

  1. Log in to your Freesound account at https://freesound.org. 2. Navigate to the API credentials page at https://freesound.org/apiv2/apply. 3. Fill out the application form by providing a name and description for your application. 4. Accept the terms of use and click 'Apply for a new credential'. 5. Copy the 'Client secret / API key' from the resulting table.

2. Add them to .dlt/secrets.toml

[sources.freesound_source] api_key = "your_client_secret_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 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 Freesound 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 freesound_pipeline.py

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

Pipeline freesound_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset freesound_data The duckdb destination used duckdb:/freesound.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 /apiv2/search/ and /apiv2/sounds/<sound_id>/ from the Freesound 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 freesound_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://freesound.org/apiv2", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "search", "endpoint": {"path": "apiv2/search/text/", "data_selector": "results"}}, {"name": "pack_sounds", "endpoint": {"path": "apiv2/packs/<pack_id>/sounds/", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="freesound_pipeline", destination="duckdb", dataset_name="freesound_data", ) load_info = pipeline.run(freesound_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("freesound_pipeline").dataset() sessions_df = data.search.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM freesound_data.search LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("freesound_pipeline").dataset() data.search.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 Freesound 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 Freesound?

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

Available Pipelines