
Understand the api lifecycle and apigee proxy development with open api specification. Configure soap web services, message validation, and policy usage for products, apps, and security.
Explore how APIs provide ready-made functionality, guided by API specifications and contracts, with credentials and billing, using Twitter's follower list JSON example to illustrate data access.
Explore the API lifecycle in Apigee from design and secure development to publish, scale, and monitoring, using open API specifications, API proxies, and built-in security and traffic policies.
Apigee is a platform to develop and manage APIs, creating a proxy layer that validates requests, enforces security, protects the backend, and offers monitoring, analytics, and a developer portal.
Select the Google Cloud project to provision the Apigee organization and manage APIs, including environment, environment group, API product, API proxy, developer, and app.
Provision Apigee in Google Cloud by enabling required APIs, creating a service network and an evaluation organization with a runtime instance, and configuring external or VPC-only access.
Provision Apigee on Google Cloud by creating a project, enabling the Apigee API, Compute Engine API, and Service Networking API, and configuring billing and a VPC for evaluation.
Explore the old and new proxy editors in Apigee, comparing classic xml and visual editor workflows, including proxy endpoint, target endpoint, pre flow, post flow, policies, and debugging across environments.
Explore the runtime environment for deploying api proxies in apigee, its provisioning status, and environment groups. Learn how to configure display names, proxy types, and deployment options.
Explore how environment groups in Apigee organize environments by hostnames for centralized management and avoid duplicate base paths. Learn to attach environments to groups so proxies deploy under assigned hostnames.
Learn how API proxies secure backend services, apply security and rate limiting policies, and expose proxy endpoints to developers via API products with quotas and the developer portal.
Create and configure an Apigee integrated developer portal, manage API catalogs and documentation, control admin and developer access, and publish APIs with pages, assets, themes, and rate plans.
Explore how Apigee components relate: developers create apps, API products include proxies, and organizations manage environments and environment groups.
Understand how flows govern API proxies by configuring pre, conditional, post, and post client flows on proxy and target endpoints, with policies guiding requests from client to backend.
Create and deploy an Apigee API proxy by configuring a base path, defining get operations and conditional flows, then deploy to environments and test with Postman against the back-end service.
Understand how proxy endpoint flows are defined in XML, including pre flow, conditional flows with operators like equals and matches, and the default flow, plus post client flow for logging.
Flow variables hold values during processing, enabling retrieval and updates for the next step, with primitive or object types and properties accessed via dot notation, for request and response data.
Explore Apigee policies to enhance flow without coding, focusing on assign message and extract variable policies that modify messages and create or store flow variables across request and response.
Create a loopback api proxy in apigee without backend target, configure a proxy endpoint, implement a get customer flow, and return a dummy json payload; deploy and test with postman.
Create a reverse proxy with extract variable and assign message policies to pass the ID via header or path parameter to the backend, handling two scenarios and header manipulation.
Debug API flows in Apigee by stepping through loopback and reverse proxies, attaching services, starting debug sessions, and inspecting requests, headers, and responses end-to-end.
Create an api proxy to call a soap web service, extract the number from the request, construct the soap payload, and return the web service response to the client.
Extract UI parameters to construct the SOAP message within an API proxy. Apply a SOAP validation policy to validate the response before returning it to the client.
Import and export API proxies by downloading proxy bundles, managing revisions, and deploying chosen revisions across environments using the Apigee portal.
Explore OpenAPI specification, a vendor-neutral, machine-readable description for designing HTTP-based APIs, covering servers, paths, parameters, request bodies, content schemas, and components.
Create a loopback api proxy from an open api specification (oas 3.0) with no target, configure get and post operations, deploy, and test the json response.
Import an open API specification document (OAS 3.0) to create a reverse proxy in Apigee, validate with Swagger Editor, and configure get and post operations against a target endpoint.
Apply the open api spec validation policy to the proxy to enforce numeric id parameters. Test numeric versus text inputs and verify validation in debug and deployment outputs.
In this example we have used <Add> and <Remove> tags.
In the <Add> tag, added Form parameters.
In the <Remove> tag, removed the Query parameters passed from the client.
Create and update flow variables using the assign message policy to set defaults from query parameters, build a json message with the set tag, deploy, and test the API proxy.
Extract XML message contents with the extract variable policy, store values in variables, and construct a JSON message via the assign message policy for a post to the API proxy.
Extract json message contents with the extract variable policy from the json payload, store values in variables, then construct a json message and apply the assign message policy.
Create an API product in the API portal, bundle the API proxy with get and post operations, and publish it to the developer portal with the Open API specification.
Register apps with an organization to obtain credentials, connect to API products and proxies, and manage API keys and secrets via developer portal or API UI.
The zip contains 4 revisions of API Proxy.
The zip contains 2 revisions of API Proxy.
Demonstrate how the Excel transform policy uses XSLT to convert XML to XML (and to HTML or text) via a stylesheet, with practical input-output examples.
The course starts by explaining the API and its life cycle as per APIGEE. The APIGEE provisioning is explained and configured showing all the steps. Once this is created we can build API proxies and API products. Components of the APIGEE are explained and the relationship between these.
Different kinds of policies are used while creating the API proxies. The proxy creation starts with the basic proxies to understand the apigee environemnt. The proxy creation is explained both in Classic and the new Proxy Editor.
After understanding the environment, the course continues to explain and create different proxies with with complex policies.
These are the different kinds of API proxies created
Calling SOAP webservices
Calling Java Class and utilize the functionality of Java.
Service callout policy is used call external endpoints in between the service to get the needed information for the proxy.
Flow callout policy implemented to call shared flows so that same functionality implementation can be reused.
JavaScript policy is implemented to demonstrate the functionality of JavaScript and how to interact with Flow variables in API proxy and JavaScript code.
Different kinds of security handling is explained and implemented using policies like Oauth, Basic Authentication, XML Thret Protection, JSON Threat Protection, JSON Web Token(JWT), JSON Web Signature (JWS), API key, and HMAC.
The API creation to API deployment steps are explained to understand the system completely. How to use components like Developer portal, Apps, and Product are explained with examples.