Apigee

Apigee
• Apigee is Google Cloud's native API management platform that can be used to
build, manage, and secure APIs — for any use case, environment, or scale.
• Apigee offers high performance API proxies to create a consistent, reliable
interface for your backend services.

• The proxy layer gives you granular control over security, rate limiting, quotas,
analytics, and more for all of your services.

• Apigee supports REST, gRPC, SOAP, and GraphQL, providing the flexibility to
implement any API architectural style.
What does Apigee provide?
• Apigee provides an API proxy layer that sits between your backend
services and internal or external clients that want to use your
services.
• Apigee provides a rich array of policies that allow you to add security,
traffic management, data mediation, extension
• You can also add custom code, conditional logic, fault handling, rate
limiting, caching, and many other actions. Because the policies and
actions are implemented on Apigee, in the API proxy layer, your
underlying backend services can remain unchanged.
Who uses Apigee?
• Apigee is designed to benefit two key types of users and the unique
API management challenges they face:
• API producers: API producers build and manage the APIs that expose
their backend services.
• API consumers: API consumers use the data provided by the API in
their client applications.
Challenges for API producers
• API producers face a specific set of challenges when exposing backend
services, such as:
• Security: they must take all necessary steps to secure and protect their
services from unauthorized access.
• Discoverability: API producers must ensure that client application developers
can find their APIs and use them. As services change, the API producer needs
to keep app developers aware of updates and ensure that the services
remain compatible with other platforms and devices.
• Measurability: As an API producer, you should monitor your services to make
sure they are always available to client applications. You may also want to
measure traffic, set quotas, and gain insight into who is using your services.
Challenges for API consumers
• Client app developers consuming services from numerous providers face a
slightly different set of challenges, such as:
• Flexibility: There are many technologies available today for a service provider to
expose its services. The same client app might have to use one method to
consume a service from one provider, and a different method to consume a
service from a different provider.
• Ease of use: API consumers want to use APIs that are well-designed, easily
discoverable, and well-documented so they can get started quickly.
• Reliability: API consumers depend upon the reliability of the backend services to
keep their own client applications running smoothly. Maintaining a consistent API
interface allows API producers to implement backend service changes without
disruption to API consumers.
Key benefits of using Apigee
• Apigee API management offers features designed specifically to meet the needs of API producers
and consumers.
• API discoverability
• Apigee offers API producers a developer-focused portal where client app developers can discover
your APIs, find the documentation required to build applications using them, and register as an app
developer to stay in sync with any updates or changes. Learn more about developer portals in the
Publishing overview.
• API insights
• Apigee offers Advanced API security, API monitoring, and analytics features that enable API
producers to secure access to their services, monitor uptime and traffic with alerting, and gain
insight into how their APIs are being used.
• API reliability
• Apigee provides a consistent interface for API management and consumption. You can execute
policies for security, traffic management, and efficiency of your APIs at the proxy level. Using Apigee
proxies allows you to isolate API consumers from your backend service. This means that you can
make changes to your backend while allowing client applications to consume your services without
Apigee
• with Apigee you'll be able to securely expose bear Api's with API keys or OAuth or
JWT.
• modernize existing soap services
• Publish your Api's to developers through your own custom API portal and get
visibility into usage of your Api's via Api analytics
• all of that is available to you when you manage your Api's with Apogee edge.
• the key concept that enabling the API management goodness is the API proxy.
API Proxy
• proxy is a wrapper for your actual service clients instead of calling your API
endpoint directly call the API proxy and the API proxy calls your existing API.
• why the extra hop why use one extra moving part?
• API proxy provides the way to plug in an application independent mechanism for you to
specify consistent management rules and policies that apply to all of your API’s
• your Api's might be a mix of services lacking consistency with respect to security or data
model or even URL design
• an API proxy allows you to build a coherent facade around those various endpoints
• maybe all of your API are clean new implementations so you don't need a proxy to enforce
consistency but
• you will still want an API proxy to handle things like a lot token verification or caching routing
rate limiting and analytics and reporting
• Apigee can provide all of that with no coding and no modification of your existing services so
that's API management Apigee edge lets you easily add management to any API
In Apigee, the API used for managing and customizing the developer portal is the Apigee Management API. This
API allows you to programmatically manage and retrieve information about your APIs, API products, developers, and
other entities within the Apigee platform. The Management API is RESTful and can be accessed using standard
HTTP requests.
Here are some key aspects of the Apigee Management API that you may use when working with the developer
portal:
1.API Products API:
•Endpoint: https://api.enterprise.apigee.com/v1/organizations/{org_name}/apiproducts
•Purpose: Manage API products, which are collections of API proxies that developers can subscribe to.
2.Developers API:
•Endpoint: https://api.enterprise.apigee.com/v1/organizations/{org_name}/developers
•Purpose: Manage developer accounts, including registration, updating developer details, and viewing
developer information.
3.Apps API:
•Endpoint: https://api.enterprise.apigee.com/v1/organizations/{org_name}/developers/{developer_email}/apps
•Purpose: Manage developer apps, including app creation, updating app details, and viewing app information.
4.API Proxies API:
•Endpoint: https://api.enterprise.apigee.com/v1/organizations/{org_name}/apis
•Purpose: Manage API proxies, which define the behavior of your APIs.
5.Developers Apps API:
•Endpoint: https://api.enterprise.apigee.com/v1/organizations/{org_name}/developers/{developer_email}/apps
•Purpose: Retrieve a list of apps associated with a developer.
6.Monetization API:
•Endpoint: https://api.enterprise.apigee.com/v1/organizations/{org_name}/monetization-packages
•Purpose: Manage monetization packages and related configurations.
7.Key and OAuth Management API:
•Endpoint: Various, including https://api.enterprise.apigee.com/v1/organizations/{org_name}/developers/{developer_email}/apps/{app_name}/keys
•Purpose: Manage API keys, OAuth tokens, and other security-related aspects.
These are just a few examples, and the Apigee Management API offers additional endpoints and functionalities to
interact with various aspects of the Apigee platform.
To use the Apigee Management API, you typically need to include an API key for authentication, and you may also
need to handle OAuth for certain operations. Always refer to the official Apigee Management API documentation for
detailed information on available endpoints, request/response formats, and authentication requirements.