North Data Python API Docs | dltHub
Build a North Data-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
North Data is a database platform providing programmatic access to company information, financial data, and visualizations via REST API. The REST API base URL is https://www.northdata.de/_api and all requests require an API key.
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 North Data data in under 10 minutes.
What data can I load from North Data?
Here are some of the endpoints you can load from North Data:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| company | /company/v1/company | GET | Retrieve a company. | |
| company_publications | /company/v1/publications | GET | Retrieve the publications associated with a company. | |
| person | /person/v1/person | GET | Retrieve a person. | |
| person_publications | /person/v1/publications | GET | Retrieve the publications associated with a person. | |
| publications | /pub/v1/publications | GET | Retrieve publications. |
How do I authenticate with the North Data API?
Authentication is performed by passing an API key either as an 'X-Api-Key' HTTP header or as a query parameter named 'api_key'.
1. Get your credentials
North Data does not document a self-service API-key dashboard. Purchase or request access to the North Data Data API, then obtain the key from North Data by contacting support@northdata.com; the documentation says an API key is required and the user guide explicitly instructs users to contact support for one. North Data’s Data Services page describes API pricing and service packages, so review or arrange the appropriate package there first. After receiving the key, keep it secret and send it in the X-Api-Key HTTPS header for production requests. North Data also documents api_key as a URL or POST parameter, but recommends the header method for production because query-string keys can leak through logs and intermediaries.
2. Add them to .dlt/secrets.toml
[sources.north_data_source] api_key = "XXXX-XXXX"
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 North Data 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 north_data_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline north_data_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset north_data_data The duckdb destination used duckdb:/north_data.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 company and person from the North Data 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 north_data_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.northdata.de/_api", "auth": {"type": "api_key", "api_key": api_key, "name": "X-Api-Key", "location": "header"}, }, "resources": [ {"name": "publications", "endpoint": {"path": "pub/v1/publications"}}, {"name": "company_publications", "endpoint": {"path": "company/v1/publications"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="north_data_pipeline", destination="duckdb", dataset_name="north_data_data", ) load_info = pipeline.run(north_data_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("north_data_pipeline").dataset() sessions_df = data.publications.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM north_data_data.publications LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("north_data_pipeline").dataset() data.publications.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 North Data 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 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 North Data?
Request dlt skills, commands, AGENT.md files, and AI-native context.