Gridly Python API Docs | dltHub

Gridly is a REST API-driven spreadsheet/CMS for managing content (grids, views, records, files, automations) programmatically. The REST API base URL is https://api.gridly.com/v1 and all requests require an ApiKey provided 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 Gridly data in under 10 minutes.

---

What data can I load from Gridly?

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

---

How do I authenticate with the Gridly API?

Gridly uses API key authentication. Include header: Authorization: ApiKey {YOUR_API_KEY}. All requests must use HTTPS.

1. Get your credentials

1. Sign in to https://app.gridly.com/ 2) Open a Grid and select a View, use the "API quick start" panel for a view-scoped key or go to Settings → API keys (Owner/Admin) to create company-level keys 3) Copy the API key value to use in the Authorization header as "ApiKey {KEY}".

2. Add them to .dlt/secrets.toml

Copy
[sources.gridly_data_source]
api_key = "your_api_key_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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 Gridly 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:

Copy
python gridly_data_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline gridly_data_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 records and views from the Gridly API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def gridly_data_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.gridly.com/v1",
            "auth": {
                "type": "api_key",
                "api_key": api_key,
            },
        },
        "resources": [
            {"name": "records", "endpoint": {"path": "views/{viewId}/records"}},
            {"name": "views", "endpoint": {"path": "views"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="gridly_data_pipeline",
        destination="duckdb",
        dataset_name="gridly_data_data",
    )
    load_info = pipeline.run(gridly_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):

Copy
import dlt

data = dlt.pipeline("gridly_data_pipeline").dataset()
sessions_df = data.records.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM gridly_data_data.records LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("gridly_data_pipeline").dataset()
data.records.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 Gridly data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication failures

If you receive 401 Unauthorized or an error with code unauthorized, verify your Authorization header is exactly: Authorization: ApiKey {YOUR_API_KEY}. Ensure the key has required scope (view-scoped vs company key) and you are calling https://api.gridly.com over HTTPS.

Rate limits and subscription tiers

API availability and which endpoints are allowed depend on subscription tier. Check your plan limits and API access in Gridly help pages. Use X-Total-Count header for pagination; paginate using page parameter (URL-encoded JSON: {"offset":,"limit":}). Default limit is 100, max 1000.

Pagination, filtering and sorting

List endpoints return arrays. Pagination uses page query param: page={"offset":,"limit":} (URL encoded). Filtering: query={"":{"":}}. Sorting: sort={"":"asc|desc"}.

Common API errors

Gridly returns conventional HTTP statuses. Error responses contain JSON with at least code and message. Common codes: unauthorized, accessDenied, badRequest, viewIsNotFound, gridIsNotFound, invalidRecordId, requestRecordsExceedLimitation.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack