Load Glean data in Python using dltHub

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

Last updated:

Glean is an enterprise search and knowledge management platform offering REST APIs for platform integration, client operations, and content indexing. The REST API base URL is https://{instance-name}-be.glean.com and all requests require a Bearer token in the Authorization header, with some flows requiring an additional X-Glean-Auth-Type 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 Glean data in under 10 minutes.


What data can I load from Glean?

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

ResourceEndpointMethodData selectorDescription
collections/rest/api/v1/listcollectionsPOSTList all existing Collections
collections/rest/api/v1/getcollectionPOSTRead the details of a Collection given its ID
documents/rest/api/v1/getdocumentsPOSTdocumentsRead document details for a given list of IDs/URLs
documents/rest/api/v1/getdocumentsbyfacetsPOSTRead documents matching given facet conditions
entities/rest/api/v1/listentitiesPOSTList entities that fit the given criteria

How do I authenticate with the Glean API?

All requests require an 'Authorization' header with a 'Bearer' token. When using tokens from an external Identity Provider (IdP) for the Client API, an additional 'X-Glean-Auth-Type: OAUTH' header is required.

1. Get your credentials

  1. Sign in to your Glean Admin Console.
  2. Navigate to Platform -> API Tokens.
  3. Depending on the required API family, select the Client API Tokens or Indexing API Tokens tab.
  4. Click Add New Token (or Add Token).
  5. Enter a descriptive name, configure permissions (Global or specific app/datasource), and set an expiration date (required).
  6. Click Save/Create.
  7. Copy the generated token secret immediately, as it cannot be retrieved again.

2. Add them to .dlt/secrets.toml

[sources.glean_source] glean_api_token = "your_glean_issued_token_secret_here" # For global tokens, you may also need to configure the user to act as: # glean_act_as_email = "user@company.com"

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 Glean 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 glean_pipeline.py

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

Pipeline glean_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset glean_data The duckdb destination used duckdb:/glean.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 /rest/api/v1/search and /rest/api/v1/indexing from the Glean 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 glean_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{instance-name}-be.glean.com", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "platform_search", "endpoint": {"path": "api/search", "data_selector": "results"}}, {"name": "documents", "endpoint": {"path": "rest/api/v1/getdocuments", "data_selector": "documents"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="glean_pipeline", destination="duckdb", dataset_name="glean_data", ) load_info = pipeline.run(glean_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("glean_pipeline").dataset() sessions_df = data.documents.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM glean_data.documents LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("glean_pipeline").dataset() data.documents.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 Glean 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.
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 Glean?

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