Skip to main content

Veeam Backup & Replication Python API Wrapper (Beta)

  • January 29, 2026
  • 4 comments
  • 57 views

JonahMay
Forum|alt.badge.img+12

Hi all 👋,

 

After yesterday’s post about a beta release of a VSPC Python package that acts as a REST API wrapper, I’m back today with the same but for Veeam Backup & Replication this time. Thanks again to ​@mkevenaar for his assistance in making this happen!

 

This project brings the same philosophy and structure to VBR automation: typed, versioned, reusable Python clients generated directly from Veeam’s own API specs.

This is the first public beta release, and the official unveiling of the project.

 

What it does

veeam-br:

✅ is generated from Veeam’s official OpenAPI specs
✅ provides versioned client modules (currently v1_3_rev1)
✅ supports both synchronous and asynchronous API calls
✅ exposes models and endpoints as real Python objects
✅ is suitable for scripts, jobs, or full applications

Example usage:

from veeam_br.v1_3_rev1 import Client
from veeam_br.v1_3_rev1.api.login import create_token
from veeam_br.v1_3_rev1.models.token_login_spec import TokenLoginSpec
from veeam_br.v1_3_rev1.models.e_login_grant_type import ELoginGrantType

client = Client(base_url="https://vbr.example.com:9419", verify_ssl=False)

body = TokenLoginSpec(
grant_type=ELoginGrantType.PASSWORD,
username="administrator",
password="SuperSecret"
)

with client:
token = create_token.sync(client=client, body=body, x_api_version="1.3-rev1")

auth_client = AuthenticatedClient(
base_url=client._base_url,
token=token.access_token,
verify_ssl=client._verify_ssl,
)
# Now you can call other endpoints with auth_client…

 

Current status

  • Supported API Version: VBR REST API 1.3-rev1 (Veeam Backup & Replication 13.0.1.180)
  • Generated from OpenAPI schemas
  • Offers both sync and async interfaces
  • Open source — Apache-2.0 license

This beta should cover the full API surface for the supported version, but real-world validation and feedback are what make a 1.0 release strong.

Expect rapid iteration and improvements based on use cases from the community.

 

How to try it

Install via pip:

pip install veeam-br

Repo + docs:
👉 https://github.com/Cenvora/veeam-br

 

Who this is for

  • Engineers automating VBR reporting

  • MSPs building internal tooling

  • Service providers integrating VBR into portals

  • Anyone tired of writing ad-hoc REST scripts

  • Python users who want a reusable, generated client

 

What I’m looking for

Since this is brand new, I’m actively looking for:

  • feedback on API usability

  • requests for missing endpoints or coverage gaps

  • schema/version needs

  • early pull requests

  • real-world use cases to prioritize

Your feedback will directly shape the 1.0 release.

 

Disclaimer

This is a community project, not an official Veeam product or R&D deliverable.
It’s open source, Apache-2.0 licensed, and maintained in the open.

 

If you automate around VBR and Python, I’d love your input — this is the kind of tool that gets better fast with community feedback.

Happy automating 🚀

4 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • January 29, 2026

Will add this one to my list to test out with the other VSPC one.  More to come.


Jonty
Forum|alt.badge.img+1
  • VUG Leader
  • February 2, 2026

I am interested in automation but most of it goes way over my head. How would recommend I get started? I see you using python would you start with learning python?


JonahMay
Forum|alt.badge.img+12
  • Author
  • Veeam Vanguard
  • February 2, 2026

I am interested in automation but most of it goes way over my head. How would recommend I get started? I see you using python would you start with learning python?

In many cases I find it to be a personal preference unless there is a specific use case. Python seems to be a relatively easy to learn language, which means many areas have started to adopt it. For example, AI capabilities at least in open source are commonly built on Python in part because of tools like pytorch. In this case, part of the reason I did this wrapper as Python is because I have been too lazy to build proper monitoring for my home lab with something like Zabbix and while I eventually will, I have been throwing key components into Home Assistant for the time being. Home Assistant integrations are built on Python, so I was able to use this with Copilot to develop a custom integration over the last week. I’ll be making a post here about that hopefully later this week, ​@mkevenaar and I are just taking some time to QC it before we release it into the wild.


Jonty
Forum|alt.badge.img+1
  • VUG Leader
  • February 2, 2026

Hi Jonah.

Thank you then I will give Python a shot and take it from there maybe its starts a whole new rabbit hole.Â