InformationGrid Python API Docs | dltHub

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

Last updated:

InGrid-API is a centralized interface for managing InGrid datasets and metadata search capabilities. The REST API base URL is http://localhost:8550/v3/api-docs and 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 pip install "dlt[workspace]" and start loading InformationGrid data in under 10 minutes.


What data can I load from InformationGrid?

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

ResourceEndpointMethodData selectorDescription
catalogs/portal/catalogsGETRetrieves all catalogs containing at least one dataset.
catalog_hierarchy/portal/catalogs/{id}/hierarchyGETRetrieves the hierarchical structure of a dataset within a catalog.
search/portal/searchPOSTExecutes an Elasticsearch search query via the request body.
api_docs/v1/api-docsGETRetrieves API specification documentation.
info/v1/infoGETReturns general API usage information.
version/v1/versionGETReturns current API version information.

How do I authenticate with the InformationGrid API?

Authentication is managed via Keycloak using OAuth2. Clients must include a bearer token in the Authorization header for API requests.

1. Get your credentials

To obtain your API credentials for the Ingrid (InformationGrid) platform, register an account on the official Ingrid developer portal. Upon registration, you will be issued an API token, which must be included in every request within the 'Authorization' HTTP header using the 'Bearer' prefix (e.g., 'Authorization: Bearer <your_token_here>'). Keep this token secure, as it functions like a password, and ensure backend-only usage.

2. Add them to .dlt/secrets.toml

[sources.informationgrid_source] api_token = "your_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 harness:

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:

dlthub 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 InformationGrid 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 informationgrid_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline informationgrid_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 session.create and siw/session.create from the InformationGrid 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 informationgrid_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:8550/v3/api-docs", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "catalogs", "endpoint": {"path": "/portal/catalogs"}}, {"name": "search", "endpoint": {"path": "/portal/search"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="informationgrid_pipeline", destination="duckdb", dataset_name="informationgrid_data", ) load_info = pipeline.run(informationgrid_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("informationgrid_pipeline").dataset() sessions_df = data.catalogs.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM informationgrid_data.catalogs LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("informationgrid_pipeline").dataset() data.catalogs.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 InformationGrid 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.
dlthub ai toolkit data-exploration install dlthub ai toolkit dlthub-platform install

Was this page helpful?

Community Hub

Need more dlt context for InformationGrid?

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

Available Pipelines