Kong OpenID Connect Python API Docs | dltHub
Build a Kong OpenID Connect-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Kong OpenID Connect is a plugin that integrates Kong Gateway with third-party identity providers to handle authentication and authorization flows. The REST API base URL is http://localhost:8001 and Requests to administrative endpoints 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 Kong OpenID Connect data in under 10 minutes.
What data can I load from Kong OpenID Connect?
Here are some of the endpoints you can load from Kong OpenID Connect:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| openid_connect_issuers | /openid-connect/issuers | GET | data | Lists all discovery cache objects |
| openid_connect_jwks | /openid-connect/jwks | GET | Retrieves the JSON Web Key Set (JWKS) | |
| plugins | /plugins | GET | data | Lists all plugins |
| plugins_enabled | /plugins/enabled | GET | data | Lists all enabled plugins |
| proxy_cache | /proxy-cache | GET | data | Lists proxy cache objects |
How do I authenticate with the Kong OpenID Connect API?
The Kong Admin API requires authentication via a Bearer token in the 'Authorization' header when communicating with secure control planes, or is accessed via local ports 8001/8444 for administrative management.
1. Get your credentials
The Kong OpenID Connect plugin does not use plugin-specific credentials. It is managed via the Kong Admin API, typically accessible at http://{KONG_ADMIN_HOST}
. In production, you must secure this Admin API using Kong's built-in authentication (such as RBAC or ACLs) rather than relying on default open access. To authenticate the dlt pipeline, you should provide the appropriate Admin API credentials via the configuration.2. Add them to .dlt/secrets.toml
[sources.kong_openid_connect_source] admin_url = "http://your-admin-host:8001" # If the Admin API is protected, include credentials here: # api_key = "your_admin_api_key"
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 Kong OpenID Connect 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 kong_openid_connect_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline kong_openid_connect_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset kong_openid_connect_data The duckdb destination used duckdb:/kong_openid_connect.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 openid-connect/jwks and openid-connect/discovery-cache from the Kong OpenID Connect 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 kong_openid_connect_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:8001", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "openid_connect_issuers", "endpoint": {"path": "openid-connect/issuers", "data_selector": "data"}}, {"name": "plugins", "endpoint": {"path": "plugins", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="kong_openid_connect_pipeline", destination="duckdb", dataset_name="kong_openid_connect_data", ) load_info = pipeline.run(kong_openid_connect_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("kong_openid_connect_pipeline").dataset() sessions_df = data.openid_connect_issuers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM kong_openid_connect_data.openid_connect_issuers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("kong_openid_connect_pipeline").dataset() data.openid_connect_issuers.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 Kong OpenID Connect 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 Kong OpenID Connect?
Request dlt skills, commands, AGENT.md files, and AI-native context.