Before you begin
Before you begin using monetization, you need to sign up for an Apigee Edge account at https://accounts.apigee.com/accounts/sign_up. You also need to purchase monetization.
An Apigee Edge account provides you with:
- An organization
- A username
- A password
You use these credentials to login to enterprise.apigee.com. This exposes the Edge API Services APIs and the Edge management UI.
After you purchase monetization, you need to:
- Work with the Apigee configuration team to complete the initial monetization setup, as described in Initial setup performed by the Apigee Edge configuration team.
- Complete the remaining monetization setup steps, as described in Set up monetization.
- Perform other related tasks after monetization is set up, as described in Manage monetization.
Initial setup performed by the Apigee Edge configuration team
Work with the Apigee Edge configuration team to complete the initial setup of monetization. Based on your input the configuration team will set up the following:
- Whether your organization is a telecommunications company.
- Which billing type you wish to support for developers who purchase your
rate plans: prepaid, postpaid, or both.
- A prepaid developer pays in advance for the use of your API products. Funds are deducted from a prepaid developer's balance when the API product is used.
- A postpaid developer is billed monthly (through an invoice) for the use of your API products.
- Whether you want detailed or summary data extracted from monetization into your accounting system and the data format required.
- Custom email reply address. For monetization email notifications that are sent to companies and developers, a default firstname.lastname@example.org address is configured. You must request a custom reply name and address for your organization.
Set up monetization
After the Edge configuration team creates the initial configuration, here's what you need to do to further set up and use monetization:
- Edit the organization profile. The organization profile includes your organization’s name, country, terms and conditions, and supported currencies.
- Add terms and conditions (T&C's) that developers must accept before they can purchase your rate plans. See Specify terms and conditions for details.
- Edit the currencies initially set up for your organization. See Manage supported currencies for details.
- Enforce monetization limits on the API proxies that you will include in your API products.
- Monetize API products that you want to bundle into API packages.
- Create API packages that you want to monetize for sale to developers. Each API package groups one or more API products.
- Create a transaction recording policy for each of your API products. The transaction recording policy defines what you would like to capture in the transaction records for an API product, including any custom attributes.
- Create rate plans for each API package. You can set up standard rate plans, rate plans for developer categories, or developer-specific rate plans. After you create rate plans, you can publish them for viewing by developers or save them as drafts (see Managing and publishing rate plans).
- Manage companies and developers (as applicable). By creating companies and assigning developers to them, you can create rate plans that apply to specific companies.
- Set up notifications using notification templates that you want to enable.
- Configure monetization in the developer portal, as described in Overview of Monetization in the Developer Portal.
After you set up monetization, you can do the following:
- Create reports. You can create prepaid balance, revenue, and variance reports. For prepaid developers, you can reconcile prepaid balance reports with bank deposits.
- Make adjustments to billing and traffic details to correct discrepancies in your records, for example.
- Issuing credits (such as refunds and adjustments), if applicable.
- Manage prepaid account balances for prepaid accounts using a third-party payment provider or by setting up automatic reload.
- Post refunds to developers for purchase transactions.
- Schedule monetization jobs to send notifications, fetch and revise tax rates, and more.
- Synchronize Apigee Edge data with monetization, if instructed to do so by Apigee.
- Test notification setup to test the execution of webhooks and notifications, and view status of transactions.
- Extract files to other systems for accounting (and billing if you don't use monetization for billing). This depends on the extraction process for integration with other systems that the Apigee Edge configuration team created in the initial configuration.