Neptune Python API Docs | dltHub
Build a Neptune-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Neptune's REST API supports OpenAPI 2.x and 3.x specifications. The main reference is at https://docs-legacy.neptune.ai/api/neptune/. For client library details, see https://docs-legacy.neptune.ai/api/client_index/. The REST API base URL is https://app.neptune.ai and All requests require an API token (set as NEPTUNE_API_TOKEN or passed as api_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 Neptune data in under 10 minutes.
What data can I load from Neptune?
Here are some of the endpoints you can load from Neptune:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| runs | projects/{workspace}/{project}/runs | GET (via SDK) | runs | Fetch runs for a project (SDK: Project.fetch_runs_table()) |
| projects | projects/{workspace}/{project} | GET (via SDK) | project | Fetch project metadata (SDK: init_project()/Project object) |
| run_details | runs/{run_id} | GET (via SDK) | run | Fetch a run's metadata (SDK: init_run(with_id=...)) |
| models | projects/{workspace}/{project}/models | GET (via SDK) | models | List models in a project (SDK model APIs shown) |
| files | runs/{run_id}/artifacts | GET (via SDK) | artifacts | List files/artifacts associated with a run (SDK file methods) |
How do I authenticate with the Neptune API?
Neptune uses account API tokens. Clients provide the token via the SDK (api_token parameter) or via the NEPTUNE_API_TOKEN environment variable. When calling REST endpoints directly, include the token in requests the same way the SDK does (use the api_token value; many integrations expect the token in an Authorization header or as an api_token query/body parameter).
1. Get your credentials
- Sign in to your Neptune workspace at https://app.neptune.ai.
- Open the user menu / profile (top-right) and choose 'Profile' or 'Account settings'.
- Locate 'API token' or 'Manage API tokens' and create a new token (or copy an existing one).
- Save the token securely; set it as NEPTUNE_API_TOKEN in your environment or pass it to the SDK via the api_token parameter.
2. Add them to .dlt/secrets.toml
[sources.neptune_source] api_token = "your_neptune_api_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 Neptune 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 neptune_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline neptune_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset neptune_data The duckdb destination used duckdb:/neptune.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline neptune_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 runs and projects from the Neptune 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 neptune_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://app.neptune.ai", "auth": { "type": "api_key", "api_token": api_token, }, }, "resources": [ {"name": "runs", "endpoint": {"path": "projects/{workspace}/{project}/runs", "data_selector": "runs"}}, {"name": "projects", "endpoint": {"path": "projects/{workspace}/{project}", "data_selector": "project"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="neptune_pipeline", destination="duckdb", dataset_name="neptune_data", ) load_info = pipeline.run(neptune_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("neptune_pipeline").dataset() sessions_df = data.runs.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM neptune_data.runs LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("neptune_pipeline").dataset() data.runs.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 Neptune 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 Neptune?
Request dlt skills, commands, AGENT.md files, and AI-native context.