Learn to provision IBM API Connect version ten in AWS, create and access a trial, and navigate the home page to develop APIs, manage catalogs, resources, and settings.

Learn how a provider organization produces and publishes API products, manages API lifecycles and member access, and supports roles such as owner, developer, api administrator, community manager, administrator, and viewer.

Explore full lifecycle API management with API manager, organizing, publishing, and analyzing APIs, and managing provider and consumer organizations, catalogs, products, and analytics through the API Connect UI.

Publish APIs to a catalog that generates a developer portal URL for external clients to call APIs, and invite a user from your provider organization to become the catalog owner.

Understand how spaces in an IBM API Connect catalog isolate API products for credit card and loan teams, with own lifecycles, analytics, access control, and a shared developer portal.

Learn how to create and manage consumer organizations in IBM API Connect, including owner and developer roles, catalog associations, and access via the developer portal, with two creation methods.

Create and activate a developer portal account, join an organization, and manage user access, apps, and API subscriptions to access catalog APIs.

Create apps in the developer portal, and generate a client key and client secret. Track transactions and subscriptions in API analytics via the API manager.

Explore OpenAPI specification version 3, a machine-readable, vendor-neutral standard for describing REST APIs, including paths, parameters, request bodies, schemas, and how to reference components to build and test endpoints.

Explore the differences between OAS 3 and OAS 2 (swagger), including servers, components versus definitions, and request body handling in the swagger editor.

simulate backend services using API endpoints to fetch customer details via header ID, convert JSON to XML, and receive identical responses. Learn to use Postman collections for lab exercises.

Explore how an API proxy, front end to clients, validates requests, enforces security and rate limits, and enables routing, transformation, and data enrichment with IBM API Connect.

Create an API from a target service using open API 2.0, with a json to xml proxy, a customer object schema, and deploy as a product to the catalog.

Create a target service api proxy using open api specification 3.0 in IBM API Connect, configure json to xml transformation, and reuse a components schema for customer.

Create an API proxy from an existing open API service using Open API 2.0. Import the definition into API manager, validate, and deploy for testing in the developer portal.

Create a new OpenAPI 3.0 API proxy in IBM API Connect by defining paths and a get operation with an id header, deploy, and test in the developer portal.

Create a soap proxy from an existing WSDL service by importing the WSDL in SoapUI and test two operations in API Connect: number to words and number to dollars.

Leverage the invoke policy to call services from an assembly, store response in a message variable or a response object, and reuse it multiple times with xml and json data.

Demonstrate basic authentication in invoke policy by supplying a username and password, encoding them in the authorization header, and accessing a backend API like GitHub through an API proxy.

Learn how to change the http method in invoke policy, using keep or switch options to route get or post calls, and convert json responses to xml for backend endpoints.

Explore header and parameter control in invoke policy, showing how block list and allow list settings govern passing headers and parameters to the target URL.

Create a mock service with the message template policy in IBM API Connect, defining a json response for get customer details and using header id dynamically.

Store the invoke response in a response object variable within the invoke policy to capture the body and header details for use in subsequent calls.

Explore how to use the stop on error option in invoke policy to halt a flow on connection, soap, or operation errors, and observe its effect on subsequent policies.

Explore the json to xml policy converting json to xml with badger fish and relaxed badger fish formats, and apply parse policy to fix json parsing errors in API Connect.

Apply map policy to transform json to another json format within an api proxy by extracting amounts from a shopping cart and producing a new json payload.

Route requests with the operation switch policy to direct get and post calls in a new API proxy, configure endpoints, gateways, and JSON-to-XML transforms, and test via the developer portal.

Configure the api proxy with invoke policy, stop on error, and two catches. Publish the api, create paths, and verify connection and javascript errors in catches.

Build and test a throw policy in api management, defining two cases and an otherwise path, add catch blocks, configure messages, and deploy to a developer portal.

Explain how APIs are packaged into products, move from staged to published states, and are accessed via the developer portal, with plans, rate limits, hard limits, and burst limits.

Configure a rate plan for two apis in a product. Apply five calls per two minutes across credit history api and bill api.

Override plan rate limits for individual operations, such as two calls per two minutes for credit score and seven per two minutes for outstanding bill, independent of the product plan.