API Based Transaction Metering

Apprenda’s metering APIs allow developers to define transaction counters, block quantity counters, feature toggles, and feature thresholds to control application logic. This means that end user access to application functionality can be metered and controlled. Apprenda’s associated product management portal ensures that these API calls can be configured via meta-data as components of entitlement sets.

Application requirements frequently call for “access tiers” that grant different end users different feature sets. In addition, end user usage of application functionality needs to be tracked and potentially limited based on role or need. For example, power users in a particular application having the right to generate unlimited custom reports, with non-power users being limited to a single report per month.

Weaving this sort of control into an application would require that the application track transactions, provide a configurable means for control metered quantities, tracking metered usage, and reconciling usage for allocation on a periodic basis. Developers mark-up source code with API calls, and meta-data defines what an end user is entitled to in that application. At runtime, Apprenda evaluates entitlements against API calls to determine what an end user is and is not allowed to do.

Key Points

  • Metering and tracking of transactional-style “countable” quantities
  • Support for “on/off” feature toggles that block or grant access to functionality
  • Entitlement definitions tied to API calls
  • Declarative and imperative APIs for flexible, low impact modifications to source code

Apprenda’s out of the box metering APIs equip developers to flexibly tackle these use-cases with little to no effort. Developers can now achieve configurable, meterable end user usage management and tracking without having to build it.