Cato Networks Python API Docs | dltHub
Build a Cato Networks-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Cato Networks provides a GraphQL-based API for automating management and retrieving data from the Cato SASE platform. The REST API base URL is https://api.catonetworks.com/api/v1/graphql2 and all requests require an API key in the x-api-key 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 Cato Networks data in under 10 minutes.
What data can I load from Cato Networks?
Here are some of the endpoints you can load from Cato Networks:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| entity_lookup | entityLookup | POST | data.entityLookup | Retrieve account entities with pagination support using offset and limit. |
| events_feed | eventsFeed | POST | data.eventsFeed.eventsFeedAccountRecords | Retrieve large-scale event logs using marker-based pagination. |
| account_list | accountList | POST | data.accountList | List accounts associated with the authenticated user. |
| app_stats | appStats | POST | data.appStats | Retrieve application statistics. |
| audit_feed | auditFeed | POST | data.auditFeed | Retrieve audit log entries. |
How do I authenticate with the Cato Networks API?
Authentication is performed using an API key provided in the 'x-api-key' HTTP header for all requests. The API key is generated within the Cato Management Application (CMA).
1. Get your credentials
- Log in to the Cato Management Application (CMA). 2. Navigate to Resources > Admin API Keys (or Service API Keys for non-admin service integrations). 3. Click New to create a key. 4. Enter a name, set required permissions (View or Edit), optionally configure IP restrictions or expiration, and click Apply. 5. A pop-up will display the API Key value; copy it immediately as it cannot be retrieved again. 6. Note your CMA Account ID (often visible in the CMA URL or under Administration > Account > General Info) for use in API requests.
2. Add them to .dlt/secrets.toml
[sources.cato_networks_source] api_key = "REPLACE_ME"
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 Cato Networks 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 cato_networks_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline cato_networks_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset cato_networks_data The duckdb destination used duckdb:/cato_networks.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 eventsFeed and accountMetrics from the Cato Networks 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 cato_networks_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.catonetworks.com/api/v1/graphql2", "auth": {"type": "api_key", "api_key": api_key, "name": "x-api-key", "location": "header"}, }, "resources": [ {"name": "entity_lookup", "endpoint": {"path": "api/v1/graphql2", "data_selector": "data.entityLookup"}}, {"name": "events_feed", "endpoint": {"path": "api/v1/graphql2", "data_selector": "data.eventsFeed.eventsFeedAccountRecords"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="cato_networks_pipeline", destination="duckdb", dataset_name="cato_networks_data", ) load_info = pipeline.run(cato_networks_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("cato_networks_pipeline").dataset() sessions_df = data.entity_lookup.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM cato_networks_data.entity_lookup LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("cato_networks_pipeline").dataset() data.entity_lookup.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 Cato Networks 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 Cato Networks?
Request dlt skills, commands, AGENT.md files, and AI-native context.