Zerto website screenshot

Zerto

Zerto, a Hewlett Packard Enterprise company, provides continuous data protection (CDP), disaster recovery, ransomware resilience, and multi-cloud data mobility for on-premises and cloud workloads. Its ZVM (Zerto Virtual Manager), ZCA (Zerto Cloud Appliance), and ZIC (Zerto In-Cloud) appliances expose a REST API under /v1, authenticated through an embedded Keycloak OAuth2 identity provider. The API lets teams manage Virtual Protection Groups (VPGs), orchestrate non-disruptive failover tests and live failover/failback, browse recovery checkpoints, run file- and VM-level restores, manage long-term retention repositories, and consume alerts and events — everything the Zerto UI does, driven programmatically. Zerto publishes an official PowerShell SDK, plus Python, Ansible, Terraform, and Postman examples via its ZertoPublic GitHub organization.

Zerto publishes 1 API on the APIs.io network. Tagged areas include Company, Disaster Recovery, Data Protection, Backup, and Ransomware Resilience.

Zerto’s developer surface includes documentation, API reference, getting-started guide, authentication, changelog, support, engineering blog, and 16 more developer resources.

26.8/100 thin ▬ flat Agent 6/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessSelf serve
1 APIs
CompanyDisaster RecoveryData ProtectionBackupRansomware ResilienceBusiness ContinuityCloud MigrationReplicationInfrastructure

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/zerto: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Zerto ZVM REST API

REST API exposed by the Zerto Virtual Manager / Zerto Cloud Appliance for programmatic disaster-recovery management — VPGs, failover, checkpoints, VRAs, peer sites, alerts, even...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Zerto Authentication

oauth2/openIdConnect · 2 schemes

SECURITY

Zerto Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: zerto
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/zerto.png
name: Zerto
description: Zerto, a Hewlett Packard Enterprise company, provides continuous data protection (CDP), disaster recovery, ransomware
  resilience, and multi-cloud data mobility for on-premises and cloud workloads. Its ZVM (Zerto Virtual Manager), ZCA (Zerto
  Cloud Appliance), and ZIC (Zerto In-Cloud) appliances expose a REST API under /v1, authenticated through an embedded Keycloak
  OAuth2 identity provider. The API lets teams manage Virtual Protection Groups (VPGs), orchestrate non-disruptive failover
  tests and live failover/failback, browse recovery checkpoints, run file- and VM-level restores, manage long-term retention
  repositories, and consume alerts and events — everything the Zerto UI does, driven programmatically. Zerto publishes an
  official PowerShell SDK, plus Python, Ansible, Terraform, and Postman examples via its ZertoPublic GitHub organization.
url: https://raw.githubusercontent.com/api-evangelist/zerto/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- battery-ventures
- crv
- ivp
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Disaster Recovery
- Data Protection
- Backup
- Ransomware Resilience
- Business Continuity
- Cloud Migration
- Replication
- Infrastructure
apis:
- name: Zerto ZVM REST API
  description: REST API exposed by the Zerto Virtual Manager / Zerto Cloud Appliance for programmatic disaster-recovery management
    — VPGs, failover, checkpoints, VRAs, peer sites, alerts, events, tasks, and long-term retention. Authenticated via embedded
    Keycloak OAuth2 (bearer JWT).
  humanURL: https://help.zerto.com/
  baseURL: https://zvm.example.com/v1
  tags:
  - Disaster Recovery
  - Replication
  - Data Protection
  properties:
  - type: Authentication
    url: authentication/zerto-authentication.yml
  - type: Conventions
    url: conventions/zerto-conventions.yml
  - type: ErrorCatalog
    url: errors/zerto-problem-types.yml
  - type: Lifecycle
    url: lifecycle/zerto-lifecycle.yml
  - type: Conformance
    url: conformance/zerto-conformance.yml
  - type: DataModel
    url: data-model/zerto-data-model.yml
  - type: X-MCPServerCandidate
    url: mcp/zerto-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.zerto.com/
- type: DeveloperPortal
  url: https://help.zerto.com/
- type: Documentation
  url: https://help.zerto.com/
- type: APIReference
  url: https://github.com/saackerman/ZertoSwaggerAPI
- type: GettingStarted
  url: https://github.com/ZertoPublic/zerto-api-quickstart
- type: Authentication
  url: authentication/zerto-authentication.yml
- type: Conventions
  url: conventions/zerto-conventions.yml
- type: ChangeLog
  url: changelog/zerto-changelog.yml
- type: Lifecycle
  url: lifecycle/zerto-lifecycle.yml
- type: DataModel
  url: data-model/zerto-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/zerto-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/zerto-llms.txt
- type: Packages
  url: packages/zerto-packages.yml
- type: SDKs
  url: packages/zerto-packages.yml
- type: DomainSecurity
  url: security/zerto-domain-security.yml
- type: Postman
  url: https://github.com/ZertoPublic/PostmanCollections
- type: GitHubOrganization
  url: https://github.com/ZertoPublic
- type: Support
  url: https://www.zerto.com/support-and-services/support/
- type: Community
  url: https://www.zerto.com/myzerto/forums/
- type: Blog
  url: https://www.zerto.com/resources/blog/
- type: Pricing
  url: https://www.zerto.com/try-or-buy/pricing-and-licensing/
- type: SignUp
  url: https://www.zerto.com/try-or-buy/try-zerto-free/
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 16
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/zerto"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/zerto/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/zerto/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.