API / APIGEE Gateway Interview Questions
What is an API Product in Apigee and how does it differ from an API Proxy?
An API Product is a curated bundle of API proxy resources combined with a usage plan. It is the unit that developers subscribe to, and it represents how you monetise or control access to your APIs. A single API proxy can be included in multiple products with different entitlements.
| Aspect | API Proxy | API Product |
|---|---|---|
| What it is | The technical proxy configuration that handles request/response | A business-facing package of API resources with access rules |
| Who configures it | API developers / platform engineers | API product managers |
| Contains | ProxyEndpoint, TargetEndpoint, policies, flows | One or more proxies, specific resource paths, environments, and quota settings |
| Developer sees | Never directly (transparent) | Visible in developer portal; developer subscribes to it |
| Purpose | Transform, secure, route traffic | Package, monetise, and control access to API capabilities |
<!-- API Product configuration (conceptual) --> API Product: "Premium Weather API" - Proxies: weather-proxy - Environments: prod - Resource paths: /current, /forecast, /historical - Quota: 10,000 calls/day - Approval: automatic API Product: "Free Weather API" - Proxies: weather-proxy - Environments: prod - Resource paths: /current (forecast and historical NOT included) - Quota: 100 calls/day - Approval: automatic # Same proxy, different products = different entitlements per tier # Developer creates an App, subscribes to a Product, # receives a consumer key tied to that product's quota
This separation of concerns is powerful: the API proxy implementation stays the same while the product layer defines which paths, environments, and rate limits apply to each developer audience.
More Related questions...