NinjaRMM Python API Docs | dltHub
Build a NinjaRMM-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
NinjaRMM (NinjaOne) is an IT management platform that provides a REST API for accessing and managing system resources like users, organizations, and devices. The REST API base URL is https://app.ninjarmm.com/v2 and all requests require an OAuth 2.0 Bearer token 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 add "dlt[hub]" and start loading NinjaRMM data in under 10 minutes.
What data can I load from NinjaRMM?
Here are some of the endpoints you can load from NinjaRMM:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| devices | /v2/devices | GET | List all devices with basic information | |
| devices_detailed | /v2/devices-detailed | GET | List all devices with detailed information | |
| organizations | /v2/organizations | GET | results | List all organizations |
| activities | /v2/activities | GET | results | List system or device activities |
| custom_fields | /v2/custom-fields | GET | results | List custom fields configuration |
How do I authenticate with the NinjaRMM API?
The API uses OAuth 2.0 authentication, requiring an access token to be passed in the 'Authorization' header using the 'Bearer' scheme (e.g., 'Authorization: Bearer <access_token>').
1. Get your credentials
- Log in to your NinjaOne/NinjaRMM instance as a system administrator.
- Navigate to Administration > Apps > API.
- Click on the Client App IDs tab.
- Click Add (or Add Client App) to open the configuration form.
- For machine-to-machine integrations, select API Services (machine-to-machine) as the Application Platform.
- Configure your allowed grant types (e.g., Client Credentials) and permissions (scopes).
- Save the configuration. 8. Immediately copy and securely store the displayed Client ID and Client Secret, as the secret is shown only once and cannot be retrieved later.
2. Add them to .dlt/secrets.toml
[sources.ninjarmm_source] client_id = "your_client_id_here" client_secret = "your_client_secret_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 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 NinjaRMM 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 ninjarmm_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline ninjarmm_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset ninjarmm_data The duckdb destination used duckdb:/ninjarmm.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 /oauth/authorize and /oauth/token from the NinjaRMM 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 ninjarmm_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://app.ninjarmm.com/v2", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "devices", "endpoint": {"path": "v2/devices", "data_selector": "results"}}, {"name": "organizations", "endpoint": {"path": "v2/organizations", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ninjarmm_pipeline", destination="duckdb", dataset_name="ninjarmm_data", ) load_info = pipeline.run(ninjarmm_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("ninjarmm_pipeline").dataset() sessions_df = data.devices.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM ninjarmm_data.devices LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("ninjarmm_pipeline").dataset() data.devices.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 NinjaRMM 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 NinjaRMM?
Request dlt skills, commands, AGENT.md files, and AI-native context.