Perimeter81 Python API Docs | dltHub
Build a Perimeter81-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Perimeter81 (Harmony SASE) is a platform that provides secure access service edge (SASE) solutions, with its API allowing programmatic interaction with its services. The REST API base URL is https://api.perimeter81.com/api/rest and All requests require a time-based access token obtained by first using an API key for authorization..
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 Perimeter81 data in under 10 minutes.
What data can I load from Perimeter81?
Here are some of the endpoints you can load from Perimeter81:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| users | /v1/users | GET | data | Retrieve a list of users |
| users | /v1/users/{id} | GET | Retrieve a specific user by ID | |
| groups | /v1/groups | GET | data | Retrieve a list of groups |
| groups | /v1/groups/{id} | GET | Retrieve a specific group by ID | |
| devices | /v1/devices | GET | data | Retrieve a list of devices |
| networks | /v1/networks | GET | data | Retrieve a list of networks |
| regions | /v1/regions | GET | data | Retrieve a list of regions |
| auth_authorize | /v1/auth/authorize | POST | data | Authorize and get an access token |
How do I authenticate with the Perimeter81 API?
Authentication requires a two-step process: an API key is used to generate a time-based access token, which is then included in the Authorization header of subsequent requests as a Bearer token.
1. Get your credentials
To obtain API credentials, log in to your Perimeter81 Management Platform. Navigate to the 'Settings' or 'API' section and generate a new API key. This API key will be used to authorize and obtain an access token.
2. Add them to .dlt/secrets.toml
[sources.perimeter81_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:
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 Perimeter81 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 perimeter81_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline perimeter81_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset perimeter81_data The duckdb destination used duckdb:/perimeter81.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline perimeter81_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 users and devices from the Perimeter81 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 perimeter81_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.perimeter81.com/api/rest", "auth": { "type": "bearer", "access_token": api_key, }, }, "resources": [ {"name": "users", "endpoint": {"path": "v1/users", "data_selector": "data"}}, {"name": "devices", "endpoint": {"path": "v1/devices", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="perimeter81_pipeline", destination="duckdb", dataset_name="perimeter81_data", ) load_info = pipeline.run(perimeter81_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("perimeter81_pipeline").dataset() sessions_df = data.users.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM perimeter81_data.users LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("perimeter81_pipeline").dataset() data.users.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 Perimeter81 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.
Troubleshooting
Authentication Errors
Perimeter81 API uses a two-step authentication process. Ensure you are correctly using your API key to obtain a valid, time-based access token. Issues may arise if the API key is incorrect or if the access token has expired. Always re-authorize if you encounter authentication failures.
Pagination
List endpoints typically return paginated results within a data array, along with page, totalPage, and itemsTotal fields. Ensure your implementation correctly handles iterating through all pages to retrieve complete datasets.
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.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Perimeter81?
Request dlt skills, commands, AGENT.md files, and AI-native context.