API Development with Apigee

DONT FORGET TO REPLACE ME LATER

API Lifecycle

Establishes the contract between the consumer and service provider, defining details such as:

APIGEE uses the OpenAPI specification to design APIs.

API proxies are created based on the OpenAPI specification. If no specification exists, APIGEE provides tools to build proxies.

The APIGEE portal facilitates development with built-in policies, testing, and debugging.

APIGEE offers built-in security policies including API key, OAuth 2.0, Basic Authentication, XML/JSON Threat Protection, SAML, and JWT. Traffic management policies like quota and spike arrest are also available.

APIs can be easily deployed via the APIGEE portal. Once deployed, proxies run and accept client requests. APIs are published on the developer portal for app developers to access and use.

APIGEE provides monitoring tools to track API health and analytics dashboards to analyze

What is Apigee

Work Environment and Setup

It starts with the Google Project, which serves as the foundation for creating an APIGEE organization and managing APIs. Each project has a nameproject ID, and project number. When a cloud project is created, a default VPC Network is also created.

Next is the APIGEE organization, which acts as the top-level container for APIs and is created during APIGEE provisioning. While provisioning APIGEE, you must select the cloud project and ensure the user has project owner or admin access for the APIGEE organization.

Key components of the APIGEE organization include:

SOAP web services configuration and SOAP message validation

API Proxy development using OPENAPI specification

API Proxy development using OPENAPI specification

How to use Assign message policy

How to use Extract message Policy

Creating and configuring Products and Apps

Message Transformation Techniques

Implementation of below listed Extensions

Implementation of below listed Security Policies