Hi, my name is Ashish. And in this video we will see what is as your API Management. So I'm starting the API Management video series from now. And you will see many videos regarding API Management coming in this video on this is the theory section will let you know what is what are all the things that are associated with Azure API Management. Moving on, we will see a lot of practical stuff, how to configure process develop, so on and so forth, for the coming topics as your API Management. API in management helps organization publish API's to external partner and internal developers to unlock the potential of their data and services.
Business everywhere and I'm looking to extend their operations as a digital platform, creating new channels, finding new customers and trialing deeper engagement with existing Once. API Management provides the core competencies to ensure x successful API program through developer engagement, Business Insights, analytics, security and protection. You can use as your API management to take any back end and launch a full fledged API program based on it. Each API consists of one or more operations. And each API can be added to one or more products. To use an API, developers subscribe to a product that contains that appear.
And then they call the API's operation subject to any usage policies that may be in effect. common scenarios which are associated with this is securing mobile in front of by gaining access with API keys, preventing DoS attacks by using throttling or using advanced security policies like GW p token validation enabling ISV partner ecosystems by offering fast partner onboarding through the developer portal and building an API to decouple from internal implementations that are not ripe for partner consumption for running an internal API program by offering a centralized location for the organization to communicate about the availability, and latest changes to a peers, giving access based on organization accounts, all based on a secure channel between the API key and back end components of the API Management API gateway, API gateway accepts API calls and routes them to your back end. it verifies API keys JW, t tokens, certificates and other credentials.
It enforces usage quotas and rate limits. It transforms your API on the fly without code modifications. If caches canned responses were set up. It blocks called meta data for analytics purposes. Other component is reporting it define or import API schema, package API's into products. A set of policies like quotas or transformations on the API's.
Get insights from analytics. It also manages your users. Another component is developer port. It reads the API documentation, try out an API via the interactive console, create an account and subscribe to get API keys, access analytics on their own usage, API's and operations API's are the foundation of an API Management Service instance. Each API represents a set of operations available to developers. Each API contains a reference to the backend service that implement DPA and its operations map to the operations implemented by the back end service.
Operations in API management are highly configurable with control for URL mapping, query and path parameters, request and response content, and operation response caching. rate limit quotas and IP restrictions policies can also be implemented at the API or individual permission level products, products or how API's are surfaced to developers products in API Management. Have one or more API's and are configured with a title, description and Terms of Use. products can be open or protected. Protected products must be subscribed to before they can be used by an open products can be used without a subscription. When a product is ready for use by developers, it can be published.
Once it is published, it can be viewed and in case of protected products. To buy developers, subscription approval is configured at the product level and can either require administrator approval or be auto approved. Then we have groups, groups are used to manage the visibility of products to the developers. API Management has the following immutable system groups. First one is administrators. As your subscription administrators are member of this group, administrators manage API Management, services trances, creating the API is operations and products that are used by developers, developers group, authenticated developer portal users fall into this group.
We have a separate developer portal, the API portal and the Azure which is to manage and create the API's. And then we have the developer portal as well. Developers are the customers that build applications using the API's that we will develop. Developers are granted access to the developer portal and build applications that calls operation of an API that you will create via the Azure portal. And we have guest group unauthenticated developer portal users, such as prospective customers will, visiting the developer portal of the API Management instance fall into this group, it can be context, certain read only access, such as the ability to view API's would not call them. Then we have developers, developers represent the user accounts.
In an API Management Service instance, developers can be created or invited to join by the administrators, or they can sign up from the developer portal. Each developer is a member of one or more groups, and can subscribe to the poor visibility to those groups policies. Policies are a powerful capability of API management that allow the Azure portal to change the behavior of the API through the configuration. Policies are a collection of statements that are executed sequentially on the request or response of an API. Popular segments, I'm sorry, the statements include format conversion from XML to JSON and call rate limiting to restrict the number of incoming calls from a developer, and many other policies are available. Policy expressions can be as attribute values or text values in any of API management policies, unless the policy specifies otherwise.
Some policies such as control flow, and set variable policies are based on policy expressions. developer, the developer portal is where developers can learn about your API's view and call operations and subscribe to the products. prospective customers can visit the developer portal view API's and operations. You can sign up on that portal. The URL for your developer portal is located on the dashboard in the Azure portal for the API Management Service instance. So now after this video, we will do the lab sessions.
The here in the lab sessions I'll show you the different components that we discussed and the different parts that can be done. I hope you enjoyed this video. I'll see you guys in the next video. Have a good day.