OSF Python API Docs | dltHub

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

Last updated:

The OSF API documentation is available at https://developer.osf.io/. The API supports authentication and integrates with research workflows. The OSF provides a sandbox for testing. The REST API base URL is https://api.osf.io/v2 and All requests that require authentication use a Bearer token (Personal Access Token or OAuth2 access 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 OSF data in under 10 minutes.


What data can I load from OSF?

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

ResourceEndpointMethodData selectorDescription
nodes/v2/nodes/GETdataList nodes (projects); collection returns data array.
users/v2/users/GETdataList users; collection returns data array.
files/v2/files/GETdataList file resources; collection returns data array.
registrations/v2/registrations/GETdataList registrations; collection returns data array.
preprints/v2/preprints/GETdataList preprints; collection returns data array.
institutions/v2/institutions/GETdataList institutions; collection returns data array.
collections/v2/collections/GETdataList collections; collection returns data array.
providers/v2/providers/preprints/GETdataList preprint providers; collection returns data array.
tokens/v2/tokens/GETdataList personal access tokens for the user; collection returns data array.
root/v2/GETAPI root; returns top‑level object with links.

How do I authenticate with the OSF API?

The OSF API follows JSON:API and accepts an Authorization header of form Authorization: Bearer <token>. OAuth2 and Personal Access Tokens (PATs) are supported; include the header on requests that require auth.

1. Get your credentials

  1. Sign in to your OSF account at https://osf.io/.
  2. Navigate to Users → Settings → Personal Access Tokens (or to the developer console to register an OAuth application).
  3. For a Personal Access Token, click "Create new token", select the desired scopes, and copy the token that is shown once.
  4. For OAuth2, register a new application to obtain a client_id and client_secret, then follow the OAuth2 authorization flow to receive an access token.

2. Add them to .dlt/secrets.toml

[sources.osf_source] api_token = "your_personal_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 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 OSF 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 osf_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline osf_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 nodes and users from the OSF 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 osf_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.osf.io/v2", "auth": { "type": "bearer", "token": api_token, }, }, "resources": [ {"name": "nodes", "endpoint": {"path": "v2/nodes/", "data_selector": "data"}}, {"name": "users", "endpoint": {"path": "v2/users/", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="osf_pipeline", destination="duckdb", dataset_name="osf_data", ) load_info = pipeline.run(osf_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("osf_pipeline").dataset() sessions_df = data.nodes.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM osf_data.nodes LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("osf_pipeline").dataset() data.nodes.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 OSF 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 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 OSF?

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