Openverse Python API Docs | dltHub

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

Last updated:

Openverse is a REST API providing search and retrieval for openly-licensed media works across various cultural institutions and creative commons sources. The REST API base URL is https://api.openverse.org/v1 and all requests require 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 Openverse data in under 10 minutes.


What data can I load from Openverse?

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

ResourceEndpointMethodData selectorDescription
images/v1/images/GETresultsSearch openly-licensed images (paginated)
audio/v1/audio/GETresultsSearch openly-licensed audio (paginated)
images_detail/v1/images/{identifier}/GETRetrieve image by UUID
audio_detail/v1/audio/{identifier}/GETRetrieve audio track by UUID
images_stats/v1/images/stats/GETList image sources with counts

How do I authenticate with the Openverse API?

Requests to the Openverse API are authenticated by including a bearer token in the Authorization header. Specifically, the header must be formatted as 'Authorization: Bearer <access_token>'.

1. Get your credentials

To obtain credentials for the Openverse REST API, you must register your application via the API. Send a POST request to the /v1/auth_tokens/register/ endpoint with a JSON body containing your 'name', 'description', and 'email'. This will return a 'client_id' and 'client_secret'. Use these credentials to POST to the /v1/auth_tokens/token/ endpoint (with grant_type=client_credentials and application/x-www-form-urlencoded content type) to receive an 'access_token', which you then include as a Bearer token in the Authorization header of your subsequent API requests.

2. Add them to .dlt/secrets.toml

[sources.openverse_source] token = "your_openverse_access_token_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 Openverse 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 openverse_pipeline.py

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

Pipeline openverse_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset openverse_data The duckdb destination used duckdb:/openverse.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 /v1/auth_tokens/register/ and /v1/auth_tokens/token/ from the Openverse 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 openverse_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.openverse.org/v1", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "images", "endpoint": {"path": "v1/images/", "data_selector": "results"}}, {"name": "audio", "endpoint": {"path": "v1/audio/", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="openverse_pipeline", destination="duckdb", dataset_name="openverse_data", ) load_info = pipeline.run(openverse_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("openverse_pipeline").dataset() sessions_df = data.images.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM openverse_data.images LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("openverse_pipeline").dataset() data.images.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 Openverse 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 Openverse?

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

Available Pipelines