AG Grid Python API Docs | dltHub
Build a AG Grid-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
AG Grid's REST API documentation is available for reference, focusing on grid, column, and row interactions. Key methods include getCellValue and isEditing. For more details, visit the official AG Grid website. The REST API base URL is N/A (AG Grid is a client-side library; no vendor REST API/base URL) and no vendor REST API; library requires no API credentials.
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 AG Grid data in under 10 minutes.
What data can I load from AG Grid?
Here are some of the endpoints you can load from AG Grid:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| server_side_get_rows | /getRows | POST | rows | Server‑Side Row Model endpoint; request contains startRow, endRow, filterModel, sortModel, etc.; response includes rows array and optionally lastRow. |
| infinite_scroll_get_rows | /getRows | POST | rows | Infinite scrolling endpoint; similar to server‑side but may return rowsThisBlock instead of lastRow. |
| client_side_row_data | /rows | GET | rows | Returns full row data for Client‑Side Row Model; response can be a top‑level array or an object with a rows key. |
| export_csv | /export/csv | GET | (top-level array or csv) | Endpoint to provide CSV/Excel export of grid data. |
| metadata | /metadata | GET | (top-level object) | Returns column definition schema or other grid metadata. |
How do I authenticate with the AG Grid API?
AG Grid is a JavaScript/React client-side grid library and does not expose a vendor REST API. Any HTTP endpoints used with AG Grid are implemented by your application/backend; authentication is determined by that backend (e.g., Bearer token, API key, etc.).
1. Get your credentials
Not applicable. AG Grid itself does not issue API credentials; obtain credentials from whichever backend you implement to serve grid data.
2. Add them to .dlt/secrets.toml
[sources.ag_grid_source]
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 AG Grid 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 ag_grid_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline ag_grid_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset ag_grid_data The duckdb destination used duckdb:/ag_grid.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline ag_grid_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 server_side_get_rows and client_side_row_data from the AG Grid 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 ag_grid_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "N/A (AG Grid is a client-side library; no vendor REST API/base URL)", "auth": { "type": "none", "": , }, }, "resources": [ {"name": "server_side_get_rows", "endpoint": {"path": "getRows", "data_selector": "rows"}}, {"name": "client_side_row_data", "endpoint": {"path": "rows", "data_selector": "rows"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ag_grid_pipeline", destination="duckdb", dataset_name="ag_grid_data", ) load_info = pipeline.run(ag_grid_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("ag_grid_pipeline").dataset() sessions_df = data.server_side_get_rows.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM ag_grid_data.server_side_get_rows LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("ag_grid_pipeline").dataset() data.server_side_get_rows.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 AG Grid 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 AG Grid?
Request dlt skills, commands, AGENT.md files, and AI-native context.