Proxmoxer: A Python wrapper for Proxmox REST API
Proxmoxer is a python wrapper around the Proxmox REST API v2. It currently supports the Proxmox services of Proxmox Virtual Environment (PVE), Proxmox Mail Gateway (PMG), and Proxmox Backup Server (PBS).
It was inspired by slumber, but it is dedicated only to Proxmox. It allows not only REST API use over HTTPS, but the same api over ssh and pvesh utility.
Like Proxmoxia, it dynamically creates attributes which responds to the attributes you’ve attempted to reach.
Full Documentation is available at https://proxmoxer.github.io/docs/
Migrating to version 2
Full instructions for the minimal steps needed to update to version 2 can be found in Migration Docs.
Installation
pip install proxmoxer
To use the ‘https’ backend, install requests
pip install requests
To use the ‘ssh_paramiko’ backend, install paramiko
pip install paramiko
To use the ‘openssh’ backend, install openssh_wrapper
pip install openssh_wrapper
Short usage information
The first thing to do is import the proxmoxer library and create ProxmoxAPI instance.
from proxmoxer import ProxmoxAPI
proxmox = ProxmoxAPI(
"proxmox_host", user="admin@pam", password="secret_word", verify_ssl=False
)
This will connect by default to PVE through the ‘https’ backend.
Note: ensure you have the required libraries (listed above) for the connection method you are using
Queries are exposed via the access methods get, post, put and delete. For convenience two synonyms are available: create for post, and set for put.
Using the paths from the PVE API v2, you can create API calls using the access methods above.
>>> for node in proxmox.nodes.get():
... for vm in proxmox.nodes(node["node"]).qemu.get():
... print(f"{vm['vmid']}. {vm['name']} => {vm['status']}")
...
141. puppet-2.london.example.com => running
101. munki.london.example.com => running
102. redmine.london.example.com => running
140. dns-1.london.example.com => running
126. ns-3.london.example.com => running
113. rabbitmq.london.example.com => running
See Changelog in CHANGELOG.md
Metadata
Release files for proxmoxer 2.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| proxmoxer-2.3.0.tar.gz | 30.8 kB | Without provenance | Details for proxmoxer-2.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| proxmoxer-2.3.0-py3-none-any.whl | Python 3 | none | any | Details for proxmoxer-2.3.0-py3-none-any.whl |
Total release size: 50.6 kB
Release files / proxmoxer-2.3.0.tar.gz
| Download URL | proxmoxer-2.3.0.tar.gz |
|---|---|
| Size | 30.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b0b2067187af1fc6d4257a46ac68c8fd79cc25d2813637cdae7a9a98fbfd11f
|
|
BLAKE2b-256 checksum How to use checksums |
222e5481ad9cc91eff6e585eabac5be94879bc2297b8b615c7427bce610d1447
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / proxmoxer-2.3.0-py3-none-any.whl
| Download URL | proxmoxer-2.3.0-py3-none-any.whl |
|---|---|
| Size | 19.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c03445e95cf9c53b6e50614dbaf561e0e1eb3ec878cf45ddde4bc4421c56743
|
|
BLAKE2b-256 checksum How to use checksums |
f3fa598ceae13e96ac97cf8e9b481433587b87edddb4bb9200632bd8bd80e448
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for proxmoxer 2.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.