Avamar

Avamar is enterprise backup and recovery software built on client-side global data deduplication, founded in Irvine, California and backed by Lightspeed Venture Partners before EMC acquired the company in November 2006 for approximately $165 million. Avamar now ships as Dell Avamar, part of the Dell Technologies data protection portfolio, and is deployed as a customer-hosted appliance or virtual edition rather than as a public SaaS. It exposes a REST API on the Avamar server for programmatic backup, restore, client, domain, dataset, policy and activity management, secured with OAuth 2.0 access tokens and optional OIDC single sign-on, and documented through a Swagger UI served from the appliance itself. A first-party Management Console Command Line Interface (mccli) and the avtar/avmaint command set provide the scripted administrative surface alongside the API.

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

Avamar’s developer surface includes documentation, API reference, getting-started guide, support, authentication, changelog, CLI, and 19 more developer resources.

🌐 Visit website 📡 Source on GitHub

26.4/100 thin ▬ flat Agent 5/100 agent aware library Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

AccessSelf serve

1 APIs

Company Backup Data Protection Deduplication Disaster Recovery Storage Enterprise Software InfrastructureDell TechnologiesOn-Premises

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 26.4/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 6.9 / 17

Access Clarity 2.7 / 17

Operational Transparency 2.0 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 5.6 / 15

Agent readiness — 5/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

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.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

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/avamar: 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.

Avamar REST API

The Avamar REST API provides a framework to develop applications and tools that interact with a stand-alone Avamar server. It exposes backup, restore, client, domain, dataset, r...

Security Posture 4

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

Avamar Authentication

oauth2/http/openIdConnect · 5 schemes

SECURITY

Avamar Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Avamar Vulnerability Disclosure

Bugcrowd · security.txt · contact published

SECURITY

Avamar Trust Center

ISO/IEC 27001:2022, SOC 2 Type II

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Avamar Scopes

5 scopes · password/authorizationCode/clientCredentials/implicit

5 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

DataModel

Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

CLI

CLI

Packages

Packages

Access & Security 8

Authentication, authorization, and security posture

Authentication

OAuthScopes

Compliance

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

DomainSecurity

DomainSecurity

SecurityTxt

SecurityTxt

Scroll for all 8

Operate 3

Status, limits, changes, and where to get help

Support

Support

Deprecation

Deprecation

ChangeLog

ChangeLog

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: avamar
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  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/avamar.png
name: Avamar
description: Avamar is enterprise backup and recovery software built on client-side global data deduplication, founded in
  Irvine, California and backed by Lightspeed Venture Partners before EMC acquired the company in November 2006 for approximately
  $165 million. Avamar now ships as Dell Avamar, part of the Dell Technologies data protection portfolio, and is deployed
  as a customer-hosted appliance or virtual edition rather than as a public SaaS. It exposes a REST API on the Avamar server
  for programmatic backup, restore, client, domain, dataset, policy and activity management, secured with OAuth 2.0 access
  tokens and optional OIDC single sign-on, and documented through a Swagger UI served from the appliance itself. A first-party
  Management Console Command Line Interface (mccli) and the avtar/avmaint command set provide the scripted administrative
  surface alongside the API.
url: https://raw.githubusercontent.com/api-evangelist/avamar/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- lightspeed-venture-partners
x-status: acquired
x-acquired-by: EMC Corporation (now Dell Technologies)
x-acquired-date: '2006-11-15'
x-deployment: customer-hosted
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Backup
- Data Protection
- Deduplication
- Disaster Recovery
- Storage
- Enterprise Software
- Infrastructure
- Dell Technologies
- On-Premises
tags_raw:
- Company
- Backup
- Data Protection
- Deduplication
- Disaster Recovery
- Storage
- Enterprise Software
- Infrastructure
- Dell Technologies
- On-Premise
apis:
- aid: avamar:avamar-rest-api
  name: Avamar REST API
  description: The Avamar REST API provides a framework to develop applications and tools that interact with a stand-alone
    Avamar server. It exposes backup, restore, client, domain, dataset, retention, policy, plugin and activity resources over
    HTTPS on the Avamar server itself. Third-party clients are registered as OAuth 2.0 clients and call the API with a bearer
    access token. A Swagger UI served from the appliance at /api/swagger-ui.html carries the complete operation and object-model
    listing.
  humanURL: https://www.dell.com/support/home/en-us/product-support/product/avamar-rest-api/docs
  baseURL: https://avamarserver/api/v1
  x-baseURL-note: Customer-hosted. <avamarserver> is the IP address or FQDN of the customer's own Avamar server; Dell publishes
    no shared multi-tenant production host.
  tags:
  - Backup
  - Data Protection
  - REST
  - Authentication
  tags_raw:
  - Backup
  - Data Protection
  - REST
  - OAuth
  properties:
  - type: Documentation
    url: https://www.dell.com/support/home/en-us/product-support/product/avamar-rest-api/docs
  - type: APIReference
    url: https://www.dell.com/support/manuals/en-us/avamar-server/avamar_administration_guide_19.10/avamar-rest-api
  - type: GettingStarted
    url: https://www.delltechnologies.com/asset/en-us/products/data-protection/technical-support/docu89854.pdf
common:
- type: Website
  url: https://www.dell.com/
- type: DeveloperPortal
  url: https://developer.dell.com/
- type: Documentation
  url: https://www.dell.com/support/home/en-us/product-support/product/avamar-rest-api/docs
- type: APIReference
  url: https://www.dell.com/support/product-details/en-us/product/avamar-rest-api/resources/manuals
- type: GettingStarted
  url: https://www.delltechnologies.com/asset/en-us/products/data-protection/technical-support/docu89854.pdf
- type: Support
  url: https://www.dell.com/support/home/en-us/product-support/product/avamar-server/overview
- type: GitHubOrganization
  url: https://github.com/dell
- type: Authentication
  url: authentication/avamar-authentication.yml
- type: OAuthScopes
  url: scopes/avamar-scopes.yml
- type: Conventions
  url: conventions/avamar-conventions.yml
- type: ErrorCatalog
  url: errors/avamar-error-codes.yml
- type: Lifecycle
  url: lifecycle/avamar-lifecycle.yml
- type: Deprecation
  url: https://www.dell.com/support/kbdoc/en-us/000185734/all-dell-emc-end-of-life-documents
- type: ChangeLog
  url: changelog/avamar-changelog.yml
- type: CLI
  url: cli/avamar-cli.yml
- type: DataModel
  url: data-model/avamar-data-model.yml
- type: Conformance
  url: conformance/avamar-conformance.yml
- type: Compliance
  url: https://www.dell.com/en-us/dt/about-us/security-and-trust-center/compliance-service-organization-control-overlay.htm
- type: TrustCenter
  url: security/avamar-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/avamar-vulnerability-disclosure.yml
- type: Security
  url: https://www.dell.com/support/contents/en-us/article/product-support/self-support-knowledgebase/security-antivirus/alerts-vulnerabilities/dell-vulnerability-response-policy
- type: DomainSecurity
  url: security/avamar-domain-security.yml
- type: WellKnown
  url: well-known/avamar-well-known.yml
- type: SecurityTxt
  url: well-known/avamar-security.txt
- type: Packages
  url: packages/avamar-packages.yml
- type: LLMsTxt
  url: llms/avamar-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: enriched
  artifacts_added: 14
  pass: local-v1
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io

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/avamar"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/avamar/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/avamar/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.

GitHub Google LinkedIn

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