Zuora Usage API
Consumption of a billable service or resource (such as database storage space or bundles of emails sent) provides the basis for some charge models - simple usage, tiered pricing, or volume pricing. To make this work, usage must be tracked in the system and usage charges must be calculated and invoiced. Usage is always billed in arrears - for example, you might bill customers in February for their January usage. Usage can be billed on a recurring monthly, quarterly, semi-annual, or annual basis.For more information about working with usage data, see Usage.
Zuora Usage API is one of 80 APIs that Zuora publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Usage. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 7 operations across 5 paths, and defines 13 schemas. It is described by OpenAPI 2.0, at version 2023-12-15.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 7
Across 5 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Consumption of a billable service or resource (such as database storage space or bundles of emails sent) provides the basis for some charge models - simple usage, tiered pricing,…
Schemas 13
The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are GETUsageWrapper (3 properties), ProxyNoDataResponse (3 properties), POSTUsageResponseType (3 properties), ProxyBadRequestResponse (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Zuora 12
Other APIs Zuora publishes across the network.