As an API provider, you need an easy-to-use and flexible way to monetize your APIs so that you can generate revenue for the use of your APIs. Using monetization in Apigee Edge, you can create a variety of monetization plans that charge developers (or pay them through revenue sharing) for the use of your APIs.
To access APIs, app developers send an API key with requests, which uniquely identifies the developers and their apps in Edge. As an API provider, this allows you to track who is calling your APIs and charge app developers for their usage. You can also measure the usage data through analytics and generate reports.The following sections introduce key features of monetization:
Watch an introductory video to learn more about monetization.
Key components of monetization
To monetize your APIs, you define the components shown in the following figure.
The monetization components are summarized in the following table. The monetization components are scoped to your organization, the top-level container for all the objects (including APIs and developers) defined in your Edge account.
|API product||Collection of related RESTful APIs presented to developers as a bundle. Defines access limits, API key approval method, and other configuration for all bundled API proxies. For more information, see What is an API product?|
|API package||Bundle one or more API products into a single monetized container. For more information, see What is an API package?|
|Transaction recording policy||Rules that are used to determine which API calls are determined to be a
transaction for monetization. For example, if the
|Rate plan||Charges that are incurred for the use of APIs offered in a monetized API product bundle. For example, you can charge monthly flat rate or charge a specific rate per transaction. For more information, see What is a rate plan?|
Configure monetization in your developer portal
For details, see Configure monetization in the developer portal.