M3ter CompoundAggregation API
Endpoints for Compound Aggregation related operations such as creation, update, list and delete.Use Compound Aggregations to create numerical measures from usage data by applying a calculation to one or more simple Aggregations or Custom Fields. These numerical measures can then be used as pricing metrics to price your Product Plans, enabling you to implement a wide range of usage-based pricing use cases.You can create two types of Compound Aggregation:**Global**- Pricing: Not tied to any specific product and can be used to price Plans belonging to any Product.- Calculation: can reference all simple Aggregations - both Global simple Aggregations and any product-specific simple Aggregations.**Product-specific**- Pricing: belong to a specific Product and can only be used to price Plans belonging to the same Product.- Calculation: can reference any simple Aggregations belonging to the same Product and any Global simple Aggregations.**IMPORTANT!** If a simple Aggregation referenced by a Compound Aggregation has a **Quantity per unit** defined or a **Rounding** defined, these will not be factored into the value used by the calculation. For example, if the simple Aggregation referenced has a base value of 100 and has **Quantity per unit** set at 10, the Compound Aggregation calculation *will use the base value of 100 not 10*. To better understand and use Compound Aggregations, refer to the example [Compound Aggregation Use Case](https://www.m3ter.com/docs/guides/setting-up-usage-data-meters-and-aggregations/compound-aggregations#example-use-case) in the m3ter documentation.
M3ter CompoundAggregation API is one of 58 APIs that M3ter publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include CompoundAggregation. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and a getting-started guide.
This API exposes 5 operations across 2 paths, and defines 12 schemas. It is described by OpenAPI 3.0.1, at version 1.0.
Requests are made against a single base URL, https://api.m3ter.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
M3ter CompoundAggregation API declares
1 security scheme
for authenticating requests.
It supports OAuth 2.0 (OAuth2) using the clientCredentials and authorizationCode flows, exposing 6 scopes.
By default, every request must be authenticated.
OAuth2— m3ter supports machine to machine authentication using the clientCredentials OAuth2 flow. The authorizationCode flow controls access for human users via the m3…
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Endpoints for Compound Aggregation related operations such as creation, update, list and delete. Use Compound Aggregations to create numerical measures from usage data by applying…
Schemas 12
The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are PaginatedCompoundAggregationResponseData (2 properties), AbstractResponse (2 properties), AbstractRequest (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from M3ter 12
Other APIs M3ter publishes across the network.
This is an independent, third-party profile of M3ter CompoundAggregation API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.