Please add Proxmox backup jobs to "backupSessions" endpoint

[CKNorth]

Hi there,

we're currently in migration from vSphere to Proxmox VE and therefore also migrating the backup-jobs in Veeam B&R.
For monitoring of the backup-status, we're using then API and the endpoint "/backupSessions".
Now it seems that it contains all kind of backup-sessions, but the Proxmox backup-sessions.
I already contacted the support and he told me that currently there is no way to check the status of the last Proxmox-backups via the API.
IMHO it makes no sense if an endpoint that shall return all backup-sessions misses out one particular type.
Therefore, I'd kindly like to request that also the Promox-related backups are added to the list that "/backupSessions" returns.
Many thanks in advance.

Regards,
Christian Keck

[david.domask]

Hi Christian, welcome to the forums.

Thanks for your request -- our plan is to expand the REST API with full coverage to match what you can do in remote console already, and Proxmox management is planned for a future release.

[CKNorth]

Hi David,
thanks for your reply.
I saw that the API endpoint for "Get All Job States" (/api/v1/jobs/states) also offers such a list and it seems that Proxmox-jobs are included.
This already almost fulfills my requirements. However, there should be a field named "LastRun", but this is missing for Proxmox-backups.
This is an example response line for one of our Proxmox-jobs:

{'type': 'Unknown', 'status': 'Inactive', 'lastResult': 'Success', 'workload': 'Vm', 'id': 'eb0c1a79-c21f-4e1c-b994-36886785a5d9', 'name': 'B2VHR_Proxmox_VMs', 'description': 'Created by .\\Administrator at 2/13/2026 10:47 AM.', 'nextRun': '2026-02-19T21:00:00+01:00', 'nextRunPolicy': '2/19/2026 9:00 PM', 'repositoryId': 'fa3326e1-6736-47ae-bdac-fc26974b00b9', 'repositoryName': 'VHR01 - BackupRepo', 'objectsCount': 20, 'highPriority': False, 'progressPercent': 0, 'isStorageSnapshot': False}

As you can see, the "LastRun" is missing. But this is exactly the data I need for my monitoring.
Is this known and will the missing field be added in future API-revisions? Is this perhaps already planned?

Thank you.

[david.domask]

Yes, I've noticed that they seem to get returned by Get All Job States as well, but with Unknown enum type.

Currently supported job types are listed here at the start of the Jobs section. As noted, our plan is to extend this to all features and job types in future releases, but right now the Jobs and Sessions supported are as noted in the API Reference user guide linked before.

[martin.schroeder]

Hello,

I was sent here by your support in case #08143323.

We can reproduce the same limitation with Veeam Software Appliance / Veeam Backup & Replication 13.0.2.29.

GET /api/v1/jobs/states returns our Proxmox VE backup jobs as type:Unknown and status:Inactive. Although lastResult is present, the lastRun field is missing.

In addition, GET /api/v1/sessions?jobIdFilter= returns no sessions for the Proxmox jobs, while the same request returns the expected sessions for Hyper-V jobs.

This prevents reliable monitoring of Proxmox VE backup jobs through the REST API and can lead to an incorrect overall monitoring status. Proper, enterprise-grade monitoring—just as it is currently available for Hyper-V jobs—is absolutely essential for us to seriously consider Veeam as a viable solution for our Proxmox VE environments.

We would therefore appreciate full REST API coverage for Proxmox VE jobs, including a dedicated job type, lastRun information and session data through the standard sessions endpoint. Consistent visibility in the VSA web interface would also be helpful.

On a related note: We also noticed that the Configuration Backup Job is missing from the /api/v1/jobs/states endpoint. Having a reliable way to monitor this job via the REST API is equally critical for us on VSA instances, as it is essential for restoring the backup server itself if neccessary.

Best regards,
Martin

[david.domask]

Hi Martin, welcome to the forums.

I'm happy to share that Proxmox sessions (along with Nutanix) will be accessible through the REST API.

> On a related note: We also noticed that the Configuration Backup Job is missing from the /api/v1/jobs/states endpoint. Having a reliable way to monitor this job via the REST API is equally critical for us on VSA instances, as it is essential for restoring the backup server itself if neccessary.

Acknowledged, but may I ask, why not monitor with api/v1/sessions?limit=200&typeFilter=ConfigurationBackup ? It will return there.