As a Systems Engineer monitoring Proxmox hypervisors with both native PRTG sensors and custom EXE/Script Advanced (PowerShell) sensors, I want the device-level "Credentials for Proxmox" fields (API Token ID, Secret, Port) to be available as placeholders (e.g., %proxmoxtokenid, %proxmoxtokensecret, %proxmoxport) in my script parameters, so that I maintain the API token in one single place and token rotation no longer requires redundant, error-prone updates across two credential sections.

Background:
We heavily rely on Custom EXE/Script Advanced Sensors (PowerShell) to monitor our hypervisors for specific metrics, like aging snapshots. While migrating to Proxmox, we noticed that we cannot pass the newly introduced "Credentials for Proxmox" (API Token ID, Secret, and Port) to our custom scripts, as there are no placeholders available.
Support confirmed this limitation and suggested using the generic "Credentials for Script Sensors" instead. However, if we want to use PRTG's native Proxmox sensors alongside our custom scripts, this workaround forces us to maintain the exact same API token in two different sections. This duplicate credential management is a nightmare for token rotation and completely violates the DRY principle.
Since the native Proxmox integration is a relatively recent addition to PRTG, it seems mapping these credential fields to the custom script engine was simply forgotten during development.
Please close this gap and add standard placeholders (e.g., %proxmoxtokenid, %proxmoxtokensecret, %proxmoxport). This small fix would allow us to securely pass the credentials to our scripts without forcing redundant data entry.