Prepare and test your skills

Prepare and test your skills

API monetization strategies are ways to turn public-facing APIs into business value, either by charging for use or by growing business indirectly. Apigee (opens in a new tab) is Google Cloud's API management platform that supports monetization by publishing API products, registering developers, enforcing access limits, and collecting usage data. Direct models collect fees for API consumption, while indirect models create value through brand expansion, lead generation, and ecosystem growth.
Direct monetization models charge app developers or partners for access to and use of APIs. Rate plans (opens in a new tab) in Apigee define the billing currency and frequency, setup fees, recurring fees, and consumption-based fees. Usage-based billing charges for what is consumed, while tiered API products with recurring fees work like subscription plans with different limits.
Apigee supports postpaid and prepaid billing to control when developers pay:
| Billing account | When developers pay | How charges work |
|---|---|---|
| Postpaid | After using API products | Developers are billed after usage with no upfront payment. Apigee does not generate invoices, so the provider handles billing settlement. |
| Prepaid | Before using API products | Upfront payment goes into the developer's wallet. Setup fees, per-transaction costs, and recurring fees are deducted from the wallet. If the wallet has less than the setup fee at purchase, the purchase fails with an insufficient funds error. |
Apigee collects usage data based on rate plan configuration and the developer's unique API key, then generates monetization reports. The provider uses that data to create billing invoices for postpaid developers or to deduct charges from prepaid wallets.
Indirect monetization models do not charge for each API call but create business opportunities through brand expansion, lead generation, and ecosystem growth. The Apigee developer ecosystem lets providers manage a community of app developers, work with internal and external developers, formalize relationships, onboard developers, and create a developer portal. A developer portal gives app developers API documentation, samples, tutorials, API reference, blogs, forums, and support.
Apigee offers an integrated portal that can be instantly provisioned and a Drupal-based portal that enables full customization. SmartDocs makes documentation interactive so portal users can read about an API, send a live request, and view a live response. These features help attract third-party developers and partners, which expands brand reach and grows the ecosystem without billing per call.
Indirect value appears when other businesses build on a provider's services. Picsart's Apigee-powered shift from B2C to B2B lets printers, t-shirt makers, and phone case designers use Picsart's design APIs in their own products. Walgreens uses APIs and Apigee to support an app ecosystem around photo printing, prescriptions, and other services. In these cases the API drives partner activity and new business relationships rather than per-call revenue.
An API product (opens in a new tab) is a bundle of API proxies combined with a service plan. The service plan can set access limits, provide security, allow monitoring and analytics, and add features. API products are the central mechanism Apigee uses for authorization and access control, so direct pricing tiers and access rules are enforced in the product.
Publishing APIs for monetization follows an ordered process:
A numbered process flow showing the API provider creating an API product with proxies and a rate plan, registering developers and their apps to issue API keys, publishing documentation on a developer portal, then collecting usage data via the API key to generate monetization reports and bill developers through prepaid wallets or postpaid invoices.
A developer registers before registering an app. The app must pass its API key with every request to an API resource, the key is authenticated, and if valid the request is granted. The provider can revoke the key at any time, and deleting a developer invalidates all API keys associated with that developer.
Direct and indirect monetization answer different business goals and can be used together. Direct models collect revenue from API usage or subscription-style access, while indirect models use API exposure to grow brand, generate leads, and build an ecosystem that may produce revenue elsewhere.
| Model | Revenue source | Key Apigee features | Example |
|---|---|---|---|
| Direct | Fees paid by developers or partners for API access or consumption | Rate plans, postpaid and prepaid billing, API products with access limits, usage reports | Free, low-price, and higher-price API products with different request limits |
| Indirect | Brand expansion, lead generation, and ecosystem growth | Developer portal, community management, documentation, app registration | Picsart B2B design APIs and Walgreens app ecosystem |
Exam tip: Direct monetization charges for API consumption through rate plans and billing; indirect monetization earns value by growing a developer and partner ecosystem rather than billing each API call.
Ecosystem innovation through APIs means turning internal services and data into digital products that outside developers can use to build new apps. Instead of keeping pricing, ordering, tracking, or legacy database functions locked inside the company, an organization exposes them as secure, well-defined HTTP endpoints that return XML or JSON. External developers then build mobile apps, web apps, point-of-sale apps, and partner integrations on top of those assets, which speeds delivery and opens new business opportunities.
A managed API layer places a consistent interface between client applications and backend services. Apigee (opens in a new tab) is Google Cloud's native API management platform for building, managing, and securing APIs across environments and scale. API Gateway (opens in a new tab) is a distributed API management system on Google Cloud for providing secure access through a consistent REST API with hosting, logging, monitoring, traffic management, and authorization.
Traffic flows from the client app to the managed endpoint, and then from the managed endpoint to the backend service, while responses flow back along the same path. The backend can run on Cloud Run functions, Cloud Run, App Engine standard environment, app servers, databases, enterprise service bus (ESB), or service-oriented architecture (SOA) systems. Because all APIs sit behind one consistent interface, developers see the same pattern even when backends use Java, .NET, or Node.js.
Third-party integration lets outside developers create value the organization does not have to build itself. A retailer can expose product pricing and availability, sales and ordering, and order tracking services, and outside developers can then build photo-printing apps, prescription apps, store apps, or partner storefronts that call those services. This accelerates time-to-market because external teams work in parallel with internal teams and reuse proven organizational assets.
An API proxy maps a publicly available HTTP endpoint to a backend service and hides backend details. To use an API proxy, a developer only needs four pieces of information:
The proxy handles security, authorization, rate limiting, quotas, and monitoring, so backend teams keep control while outside innovation grows. Without this layer, each client app might need a different method to consume each service, and even services from the same provider could require different mechanisms.
An API proxy isolates app developers from backend service implementation, which transforms legacy systems into modern digital products. The public API stays consistent while the organization changes the database implementation, moves services to a new host, or shifts from one architecture to another. As long as the frontend API is unchanged, existing client apps continue to work without modification or redeployment.
Apigee supports REST, gRPC, SOAP, and GraphQL, so older SOAP services and newer REST services can be presented through one consistent model. Policies applied on Apigee add data transformation, filtering, security, conditional logic, custom code, caching, and fault handling without changing the backend server. This separation lets a company modernize behind the boundary while customers and partners depend on a stable product in front of it.
Exam tip: An API proxy is the mapping from one public HTTP endpoint to a backend service, while an API product is the bundle of one or more proxies offered to developers as a package.
Publishing is the process of making APIs available for consumption through a developer ecosystem. A developer portal lets client developers discover APIs, read documentation, try live requests, register, and receive API keys, while blogs, forums, and support keep them in sync when APIs change. Publishing follows an ordered workflow:
An API product is flexible because multiple products can share the same proxy with different business rules. That flexibility supports tiered monetization from the same underlying assets:
| Product tier | Access to resources | Usage limit |
|---|---|---|
| Free product | Read-only access to API resources | No charge, limited rights |
| Low-price product | Read and write access to the same resources | Low limit, such as 1000 requests per day |
| Higher-price product | Read and write access to the same resources | High limit for heavier use |
The provider defines access control and restrictions once in the product, and Apigee enforces the key check and limits on every call. Analytics and monitoring then show URL, IP, user ID, latency, errors, and custom headers or payload fields, which helps the provider measure traffic, track billing, prove reliability, and decide which products to expand next.
API management for security and scalability uses a central proxy layer to protect public endpoints, control traffic, and measure use. Apigee (opens in a new tab) is Google Cloud's native API management platform for building, managing, and securing APIs at any scale. Apigee places an API proxy layer between client apps and backend services, so all API traffic flows from clients through Apigee to backends rather than directly to backends.
The Apigee proxy layer is a facade that maps a public HTTP endpoint to a backend service such as a database, app server, or microservice. A client app only needs the proxy URL, required query parameters or headers, authentication credentials, and the response format in XML or JSON. The backend implementation stays hidden, so a database change, host move, or platform migration does not break existing client apps as long as the public API stays consistent.
Traffic flows from the client to Apigee and then to the backend in an ordered path:
Apigee is available in two flavors that place the runtime in different trust boundaries:
| Flavor | Where runtime runs | Who manages environment and data boundary |
|---|---|---|
| Apigee | In cloud hosted by Apigee | Apigee maintains the environment so teams focus on services and API definitions |
| Apigee hybrid | In your data center or chosen cloud, with management plane in Apigee cloud | API traffic and data stay confined within your enterprise-approved boundaries |
Securing applications and APIs (opens in a new tab) with Apigee means enforcing authentication, authorization, and traffic policies in the proxy layer instead of in each backend service. Policies on the API proxy can verify API keys and access tokens, validate message formats for REST, SOAP, gRPC, and GraphQL styles, handle TLS with keystore and truststore configuration, and apply conditional logic, fault handling, and data transformation. Because these controls live in Apigee, the same standard protections apply across all APIs even when different teams build and maintain the backends.
Access control is packaged through an API product, which is a bundle of one or more API proxies combined with a service plan. An API product defines operations by proxy, resource paths, and HTTP methods, and it can enforce quotas and security requirements. Developers register an app against a product and receive an API key, and Apigee then restricts that key to only the allowed operations, such as POST on /v1/payments for a mobile app versus PUT or DELETE on /v1/payments/1234 for a call-center app. Deleting a developer invalidates all associated keys and immediately removes access.
Outer network defenses can reinforce Apigee without replacing it. Cloud Armor attaches to the external Application Load Balancer to provide web application firewall (WAF) capabilities, distributed denial of service (DDoS) protection, and mitigation for risks in the OWASP Top 10. For website and mobile traffic, reCAPTCHA can add risk scoring before the request reaches Apigee, and Apigee then performs the final API-level check of keys or tokens and returns a 403 response for invalid requests.
Exam tip: An API proxy is a single public endpoint mapped to a backend, while an API product is the bundle of proxies plus service plan that controls access, quotas, and monitoring.
Rate limiting and quotas in Apigee protect backend resources from overload, spikes, and misuse while supporting tiered business models. A rate-limiting policy caps how quickly calls can arrive, and a quota policy caps how many calls a developer app can make over a period such as 1000 requests per day. When limits are exceeded, Apigee rejects the excess traffic at the proxy layer so backend compute, databases, and third-party services are not overwhelmed.
These limits also make different service plans possible on the same proxies. A provider can offer a free product with read-only access, a low-price product with read and write access at a low daily limit, and a higher-price product with the same access at a high limit. Multiple products can even share the same proxy, such as three products all using proxy 3 while only one product uses proxy 1. Caching further improves scalability by serving repeated responses from cache at the edge with Cloud CDN and Google Front End or with proxy caching policies, which reduces backend load during seasonal spikes and lowers compute and network use.
Apigee API Analytics is the monitoring and measurement system that collects data from every request and response flowing through API proxies. Apigee automatically collects URL, IP address, user ID, latency, and error data, and policies can add custom data such as headers, query parameters, or fields extracted from XML or JSON. Collection happens asynchronously from the request and response flow, so measurement has no effect on API performance.
Producers use analytics data to track developer consumption, availability, and business value in one place. The Apigee UI shows metrics and dimensions in dashboards and custom reports for business or operational questions, and the same data is also available through a command-line interface, RESTful analytics APIs, and export to Google Cloud for offline analysis. Common insights include how traffic trends over time, which methods are most popular, who is using each API product, and where latency or policy errors occur, which helps teams set quotas, plan capacity, and keep developers informed of changes.
Direct API monetization charges developers or partners for API access or consumption through rate plans, while indirect API monetization creates business value through brand expansion, lead generation, and ecosystem growth without charging for each API call. Direct models use rate plans, postpaid and prepaid billing, API products with access limits, and usage reports, while indirect models use the developer portal, community management, documentation, and app registration. Examples include tiered products with different request limits for direct monetization and Picsart B2B design APIs and the Walgreens app ecosystem for indirect monetization.
Postpaid billing charges developers after they use API products with no upfront payment, and Apigee does not generate invoices so the provider handles billing settlement. Prepaid billing requires upfront payment into the developer wallet from which setup fees, per-transaction costs, and recurring fees are deducted, and if the wallet has less than the setup fee at purchase the purchase fails with an insufficient funds error. Apigee collects usage data based on rate plan configuration and the developer unique API key to generate monetization reports used for postpaid invoices or prepaid wallet deductions.
An API proxy maps one public HTTP endpoint to a backend service and hides backend details, while an API product bundles one or more proxies with a service plan that controls access, quotas, security, and monitoring. API products are the central mechanism Apigee uses for authorization and access control, so pricing tiers and access rules are enforced in the product. Multiple products can share the same proxy with different business rules, such as a free product with read-only access, a low-price product with read and write access at a low limit such as 1000 requests per day, and a higher-price product with the same access at a high limit.
A traditional retail company stores valuable product pricing and inventory data in a legacy backend system. The company wants to achieve the following business goals without having to rebuild its core infrastructure:
How does exposing internal services through an API management platform like Apigee help the company achieve these goals?
By creating an abstraction layer that bundles legacy capabilities into secure, monetizable API products for external developers
By requiring external developers to build their applications using the exact same programming languages and architectures as the legacy backend
By granting third-party developers direct network access and database credentials to query the internal legacy systems
By automatically refactoring legacy monolithic code into containerized microservices so external partners can copy the source code
Last updated