Studio Project workflows for Paessler PRTG devices, groups, probes, and sensors
Paessler PRTG Network Monitor is an agentless infrastructure monitoring tool that tracks the availability and performance of devices, network links, servers, and applications using sensors organized into a device/group/probe hierarchy.
This project provides OpenAPI specs for automating against PRTG's REST API via an Integration Model. The -latest spec is a curated subset covering common CRUD for automation — see OpenAPIs below.
| Asset | Description |
|---|---|
| OpenAPIs/ | Paessler PRTG REST API OpenAPI specs — curated -latest plus the full dated spec |
| Studio Projects/Paessler PRTG | 24 workflows covering common CRUD automation |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| Paessler PRTG | Core Server with REST API v2 (x-vendor-api-version: 2.0) |
| Paessler PRTG Integration Model | Required to build automation against the OpenAPI specs |
Import one of the OpenAPI specs from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at your PRTG core server.
Authentication is an API token in the Authorization header:
Authorization: PrtgSharedSecret <api_token> Generate a token in PRTG under Setup > Account Settings > My Account > API Token.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"Bearer": {
"value": "<your-bearer-token>"
}
},
"server": {
"protocol": "https",
"host": "<your-host>",
"base_path": "/api/v2"
}
} | Spec | Version | Operations | Description |
|---|---|---|---|
paessler_prtg-latest.json | latest (curated) | 77 | Actively-maintained spec, trimmed to 77 of 115 upstream operations — see breakdown below |
paessler_prtg-2.0.json | 2.0 | 115 | Full spec for PRTG REST API v2.0. |
paessler_prtg-latest.jsonActively-maintained spec (x-vendor-api-version: 2.0). Trimmed to 77 of 115 upstream operations covering common CRUD for automation.
Resources included, by category:
Not included: user/usergroup/API-key administration, session-based login (the API key header is used instead), schema-discovery endpoints, PRTG libraries (custom dashboards), lookup definitions, system settings/feature toggles/license info, and the sensor status summary/reporting endpoint. Pull the full spec below if you need one of those areas.
paessler_prtg-2.0.jsonFull, unmodified vendor spec for PRTG REST API v2.0 (115 operations) — the vendor's complete API surface, preserved as-is. See paessler_prtg-latest.json above for the curated subset if you just need common CRUD automation.
Backed by the Paessler PRTG:latest Integration Model (see paessler_prtg-latest.json above). The project contains 24 workflows organized into 5 folders, one atomic workflow per API operation, covering the common-CRUD subset of the curated spec.
| Folder | Workflows | Scope |
|---|---|---|
| Devices | List, Get, Update, Delete, Pause, Resume Device | Device lifecycle |
| Groups | List, Get, Update, Delete Group | Group lifecycle |
| Probes | List, Get, Pause, Resume, Delete Probe | Probe lifecycle |
| Sensors | List, Get, Update, Delete, Pause, Resume, Acknowledge Sensor | Sensor lifecycle and alarm handling |
| Channels | List, Get Channel | Channel visibility |
| Dependency | Notes |
|---|---|
Paessler PRTG:latest Integration Model | Import from paessler_prtg-latest.json before importing the project |
Paessler PRTG integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named Paessler PRTG — update the adapter_id value in each workflow task if yours is named differently |