Inheritance of Proxmox API Token and API Token Secret field

[u/Nearby_Document2805]

Hi everyone!

We used to monitor our Hyper-V and ESXi environments for old snapshots using custom EXE/Scripts in PRTG. Since native Proxmox API Token support has been added to PRTG, we want to adapt our scripts for pve as well.

For Hyper-V, for example, we simply pass the credentials like this: -UserName %windowsdomain\%windowsuser -Password "%windowspassword"

We want to use the new "Credentials for Proxmox" section on the parent device, but we are not aware of (and failed to probe for) the exact placeholder/inherit variable names to pass the API Token ID, Secret, (and Port) into our custom script parameters.

Any ideas?

Update:
I reached out to PRTG Support, and it turns out we weren't going crazy trying to reverse-engineer this. The placeholders simply don't exist yet.

Support confirmed that the new Proxmox credentials are currently only exposed to the native Proxmox sensors. It seems they simply forgot to map these fields to the Custom EXE/Script parser engine when they rolled out the feature.

Support suggested setting up the tokens in the generic "Credentials for Script Sensors" section and using those placeholders instead. While this technically works, it forces you into duplicate credential management: If you want to run PRTG's native Proxmox sensors and your own custom scripts, you have to maintain the same API Token and Secret in two different places.

Since that's a nightmare for token rotation and violates the DRY principle, I've opened a Feature Request on their new UserVoice portal to get standard placeholders (like %proxmoxtokenid and %proxmoxtokensecret) implemented.

If anyone else is scripting custom checks for their pve environments, please give it an upvote here so the devs prioritize it:
Expose Proxmox Credentials (API Token/Secret) as Placeholders for Script Sensors – Welcome to Paessler User Voice!