Skip to main content
The Digital Vending Machine® (DVM™) APIs let Resellers and Content Providers build, distribute, and manage subscription Offers at scale. Without needing bespoke integrations for every partner. The APIs abstract the complexity of subscription partnerships, bundling, entitlements, and lifecycle management into a small set of consistent resources and workflows. This page gives you a high-level tour of how the DVM works, the core concepts you’ll interact with, and how operational resources move through their lifecycle.

​
Core concepts

​
Core API concepts

The DVM APIs are organized around a set of concepts that represent the commercial, billing, and service relationships that underpin subscription bundling. Some of the core concepts you’ll work with are:
  • Offer – the commercial package created by a Reseller
  • Product – the digital content product or service, owned by a Content Provider. A Product has product tiers.
  • Offer Plan – the pricing, billing, and phase structure of an Offer
  • Consumer Offer – a live instance of an offer purchased by a specific consumer
  • Entitlement – the consumer’s access rights to individual Product Tier.

​
Resource lifecycles

The DVM handles complex subscription behavior by tracking state explicitly. Operational resources such as Consumer Offers and Entitlements have lifecycles represented by status. A status describes:
  • Where the resource is in its operational journey
  • What actions are valid next
These lifecycles are logically connected, but clearly separated in responsibility.