API Management - Revision history

User at 12:39, 2 September 2023

2023-09-02T12:39:49Z

User at 12:39, 2 September 2023

2023-09-02T12:39:35Z

User at 12:39, 2 September 2023

2023-09-02T12:39:22Z

User at 12:38, 2 September 2023

2023-09-02T12:38:03Z

User at 15:24, 17 July 2023

2023-07-17T15:24:43Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T13:25:38Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User at 21:51, 23 September 2019

2019-09-23T21:51:44Z

User: API management is the practice an organization implements to manage the APIs they expose. This is done either internally or externally to ensure that their APIs are consumable, secure, and available to consumers in conditions agreed upon in the APIs terms

2018-11-29T18:43:18Z

New page

API management is the practice an organization implements to manage the APIs they expose. This is done either internally or externally to ensure that their APIs are consumable, secure, and available to consumers in conditions agreed upon in the APIs terms of use. Essential features API management should provide (rather than what specific solutions do) include the following:
*API management should provide a means for organizations to catalog their APIs, incorporating metadata such as the subject matter, description of the API (including different versions of the API that are currently available), human-friendly documentation, a taxonomy of the types of API available, and runtime capabilities (such as maximum requests per second). The catalog should also register the state of a given API, including metadata such as the currently supported versions;
*API management should also provide a means to act on the catalog, exposing the APIs therein to internal and/or external developer communities with the ability to enforce security controls, consumption entitlements (in the form of mechanisms such as rate limits or quotas) and surface multiple versions as required. The distance between an API being catalogued and it being exposed as a consumable endpoint should be as short as possible, with the transition being equally seamless;
*An organization may expose APIs here that do not meet the organization’s API “standards,” or exist in a form that an organization does not want to expose to their consumers (as it closely coupled an external exposed API to an internal system that is sensitive to changes). API management should also provide the ability to transform the inputs and outputs accordingly, exposing a standardized form to the API consumers;
*Finally, API management should be the system of record for API utilization, embellishing the catalog with information regarding the actual runtime behavior and characteristics of a given API in the form of metrics determined against key performance indicators. This information may include the number of API keys registered, average and peak requests per second, and so on: In fact, any data that is meaningful to the organization allows them to understand API utilization and plan accordingly for future enhancements or capacities. The information will also be used to help both monitor and monetize the APIs exposed, with the ability to make the data captured available to the organization’s operational or billing systems as required.<ref>Definition of API Management [http://nordicapis.com/core-principles-api-management/ Nordicapis]</ref>

'''Scope of API Management'''<ref>What is the Scope of API Management? [https://community.apigee.com/articles/19100/what-is-api-management.html|The Scope of API Management]</ref><br />
The scope of API Management includes:
*The process of publishing, promoting, and overseeing APIs in a secure, scalable environment
*Ensuring that developers and partners are productive
*Managing, securing, and mediating your API traffic
*Allowing an organization to grow their API program to meet increasing demands
*Enabling the monetization of APIs
*The intersection of technology, business, organization, and integration concerns

An effective API Management solution manages the use of APIs to open up an organization or a system's data so that it can be utilized by other parts of the organization or possibly third-party organizations in new and useful ways. A for-profit organization would use these capabilities to either create new revenue streams of revenue or enhance/optimize existing revenue streams (monetizing APIs); a non-profit organization or government organization may be trying to cover its operational costs while fulfilling its mission to provide benefit (in this case, in the form of data/information) to the public. API Management should provide an easy, effective, and efficient experience for the development community that is supposed to be using those

APIs. API Management also provides a governance and life-cycle framework for APIs.
From a business perspective, API Management is a revolution; from a technical perspective, it is an evolution of the earlier Service Oriented Architecture (SOA) paradigm. While API management includes much more than the SOA concepts of the early 2000’s, those concepts are still present. If anything, API management is partly a response to the flaws in early SOA strategies.

'''Components of API Management'''<ref>Components of API Management [https://en.wikipedia.org/wiki/API_management Wikipedia]</ref><br />
While solutions vary, the following functionality is typically found in API management products:
*Gateway: servers that act as API front-end, receive API requests, enforce throttling and security policies, pass the calls to the back-end service, and then pass the response back to the invoker. Gateways often include transformation engines to orchestrate and modify the requests and responses on the fly. They can also collect analytics data, provide caching and other functionality.
*Publishing tools: user interface that API providers use to define the APIs and their access and usage policies, debug execution, manage API lifecycle.
*Developer portal / API store: community site for API subscribers that is typically branded by API providers and includes documentation, interactive API console to try the APIs, ability to subscribe to the APIs and manage subscription keys, and get support from the API vendor and community.
*Reporting and analytics: reports on API usage and subscriber behavior that let API publisher optimize their offering.
*Monetization: ability to charge money for commercial APIs.

===References===
<references />

===Further Reading===
*The Definitive Guide to API Management [https://pages.apigee.com/rs/351-WXY-166/images/apigee-ebook-api-mgmt-2015-07.pdf Apigee]
*Five Rules of API Management [https://techcrunch.com/2012/11/11/5-rules-for-api-management/ Techcrunch]
*API Management 101: The Basics of API Management [http://www.apiacademy.co/resources/api-management-101-api-management-basics/ API Academy]
*What is API Management [http://searchmicroservices.techtarget.com/definition/API-management Techtarget]

@@ Line 1: / Line 1: @@
 == What is Application Programming Interface (API) Management? ==
-[[Application Program Interface (API)|API]] management is the practice an [[organization]] implements to manage the APIs they expose. This is done either internally or externally to ensure that their APIs are consumable, secure, and available to consumers in conditions agreed upon in the APIs terms of use. Essential features API management should provide (rather than what specific solutions do) include the following:
+[[Application Program Interface (API)]] management is the practice an [[organization]] implements to manage the APIs they expose. This is done either internally or externally to ensure that their APIs are consumable, secure, and available to consumers in conditions agreed upon in the APIs terms of use. Essential features API management should provide (rather than what specific solutions do) include the following:
 *API management should provide a means for organizations to catalog their APIs, incorporating [[metadata]] such as the subject matter, description of the API (including different versions of the API that are currently available), human-friendly documentation, a [[taxonomy]] of the types of API available, and runtime capabilities (such as maximum requests per second). The catalog should also register the state of a given API, including metadata such as the currently supported versions;
 *API management should also provide a means to act on the catalog, exposing the APIs therein to internal and/or external developer communities with the ability to enforce security controls, consumption entitlements (in the form of mechanisms such as rate limits or quotas) and surface multiple versions as required. The distance between an API being catalogued and it being exposed as a consumable endpoint should be as short as possible, with the transition being equally seamless;

@@ Line 1: / Line 1: @@
 == What is Application Programming Interface (API) Management? ==
-[[Application Program Interface (API)]|API]] management is the practice an [[organization]] implements to manage the APIs they expose. This is done either internally or externally to ensure that their APIs are consumable, secure, and available to consumers in conditions agreed upon in the APIs terms of use. Essential features API management should provide (rather than what specific solutions do) include the following:
+[[Application Program Interface (API)|API]] management is the practice an [[organization]] implements to manage the APIs they expose. This is done either internally or externally to ensure that their APIs are consumable, secure, and available to consumers in conditions agreed upon in the APIs terms of use. Essential features API management should provide (rather than what specific solutions do) include the following:
 *API management should provide a means for organizations to catalog their APIs, incorporating [[metadata]] such as the subject matter, description of the API (including different versions of the API that are currently available), human-friendly documentation, a [[taxonomy]] of the types of API available, and runtime capabilities (such as maximum requests per second). The catalog should also register the state of a given API, including metadata such as the currently supported versions;
 *API management should also provide a means to act on the catalog, exposing the APIs therein to internal and/or external developer communities with the ability to enforce security controls, consumption entitlements (in the form of mechanisms such as rate limits or quotas) and surface multiple versions as required. The distance between an API being catalogued and it being exposed as a consumable endpoint should be as short as possible, with the transition being equally seamless;

@@ Line 1: / Line 1: @@
-API [[management]] is the practice an [[organization]] implements to manage the APIs they expose. This is done either internally or externally to ensure that their APIs are consumable, secure, and available to consumers in conditions agreed upon in the APIs terms of use. Essential features API management should provide (rather than what specific solutions do) include the following:
+== What is Application Programming Interface (API) Management? ==
 *API management should provide a means for organizations to catalog their APIs, incorporating [[metadata]] such as the subject matter, description of the API (including different versions of the API that are currently available), human-friendly documentation, a [[taxonomy]] of the types of API available, and runtime capabilities (such as maximum requests per second). The catalog should also register the state of a given API, including metadata such as the currently supported versions;
 *API management should also provide a means to act on the catalog, exposing the APIs therein to internal and/or external developer communities with the ability to enforce security controls, consumption entitlements (in the form of mechanisms such as rate limits or quotas) and surface multiple versions as required. The distance between an API being catalogued and it being exposed as a consumable endpoint should be as short as possible, with the transition being equally seamless;

← Older revision		Revision as of 12:38, 2 September 2023
Line 43:		Line 43:

	=== See Also ===		=== See Also ===
−	*[[IT Strategy (Information Technology Strategy)\|IT Strategic Planning]]
−	*[[E-Strategy\|e-Business Strategic Planning]]
−	*[[IT Governance\|Governance of Information Technology (ICT)]]
−	*[[Enterprise Architecture\|What is Enterprise Architecture Planning]]
−	*[[IT Sourcing (Information Technology Sourcing)\|Information Technology Sourcing (IT Sourcing)]]
−	*[[IT Operations (Information Technology Operations)\|Information Technology Operations (IT Operations)]]
−	*[[Chief Information Officer (CIO)\|Chief Information Officer (CIO)]]
−	*[[Leadership\|Leadership]]

@@ Line 43: / Line 43: @@
 === See Also ===
-[[IT Strategy (Information Technology Strategy)|IT Strategic Planning]]<br />
+*[[IT Strategy (Information Technology Strategy)|IT Strategic Planning]]
-[[E-Strategy|e-Business Strategic Planning]]<br />
+*[[E-Strategy|e-Business Strategic Planning]]
-[[IT Governance|Governance of Information Technology (ICT)]]<br />
+*[[IT Governance|Governance of Information Technology (ICT)]]
-[[Enterprise Architecture|What is Enterprise Architecture Planning]]<br />
+*[[Enterprise Architecture|What is Enterprise Architecture Planning]]
-[[IT Sourcing (Information Technology Sourcing)|Information Technology Sourcing (IT Sourcing)]]<br />
+*[[IT Sourcing (Information Technology Sourcing)|Information Technology Sourcing (IT Sourcing)]]
-[[IT Operations (Information Technology Operations)|Information Technology Operations (IT Operations)]]<br />
+*[[IT Operations (Information Technology Operations)|Information Technology Operations (IT Operations)]]
-[[Chief Information Officer (CIO)|Chief Information Officer (CIO)]]<br />
+*[[Chief Information Officer (CIO)|Chief Information Officer (CIO)]]
-[[Leadership|Leadership]]<br />
+*[[Leadership|Leadership]]

@@ Line 1: / Line 1: @@
-API management is the practice an organization implements to manage the APIs they expose. This is done either internally or externally to ensure that their APIs are consumable, secure, and available to consumers in conditions agreed upon in the APIs terms of use. Essential features API management should provide (rather than what specific solutions do) include the following:
+API [[management]] is the practice an [[organization]] implements to manage the APIs they expose. This is done either internally or externally to ensure that their APIs are consumable, secure, and available to consumers in conditions agreed upon in the APIs terms of use. Essential features API management should provide (rather than what specific solutions do) include the following:
-*API management should provide a means for organizations to catalog their APIs, incorporating metadata such as the subject matter, description of the API (including different versions of the API that are currently available), human-friendly documentation, a taxonomy of the types of API available, and runtime capabilities (such as maximum requests per second). The catalog should also register the state of a given API, including metadata such as the currently supported versions;
+*API management should provide a means for organizations to catalog their APIs, incorporating [[metadata]] such as the subject matter, description of the API (including different versions of the API that are currently available), human-friendly documentation, a [[taxonomy]] of the types of API available, and runtime capabilities (such as maximum requests per second). The catalog should also register the state of a given API, including metadata such as the currently supported versions;
 *API management should also provide a means to act on the catalog, exposing the APIs therein to internal and/or external developer communities with the ability to enforce security controls, consumption entitlements (in the form of mechanisms such as rate limits or quotas) and surface multiple versions as required. The distance between an API being catalogued and it being exposed as a consumable endpoint should be as short as possible, with the transition being equally seamless;
-*An organization may expose APIs here that do not meet the organization’s API “standards,” or exist in a form that an organization does not want to expose to their consumers (as it closely coupled an external exposed API to an internal system that is sensitive to changes). API management should also provide the ability to transform the inputs and outputs accordingly, exposing a standardized form to the API consumers;
+*An organization may expose APIs here that do not meet the organization’s API “standards,” or exist in a form that an organization does not want to expose to their consumers (as it closely coupled an external exposed API to an internal [[system]] that is sensitive to changes). API management should also provide the ability to transform the inputs and outputs accordingly, exposing a standardized form to the API consumers;
-*Finally, API management should be the system of record for API utilization, embellishing the catalog with information regarding the actual runtime behavior and characteristics of a given API in the form of metrics determined against key performance indicators. This information may include the number of API keys registered, average and peak requests per second, and so on: In fact, any data that is meaningful to the organization allows them to understand API utilization and plan accordingly for future enhancements or capacities. The information will also be used to help both monitor and monetize the APIs exposed, with the ability to make the data captured available to the organization’s operational or billing systems as required.<ref>Definition of API Management [http://nordicapis.com/core-principles-api-management/ Nordicapis]</ref>
+*Finally, API management should be the system of record for API utilization, embellishing the catalog with information regarding the actual runtime behavior and characteristics of a given API in the form of [[metrics]] determined against key performance indicators. This information may include the number of API keys registered, average and peak requests per second, and so on: In fact, any [[data]] that is meaningful to the organization allows them to understand API utilization and plan accordingly for future enhancements or capacities. The information will also be used to help both monitor and monetize the APIs exposed, with the ability to make the data captured available to the organization’s operational or billing systems as required.<ref>Definition of API Management [http://nordicapis.com/core-principles-api-management/ Nordicapis]</ref>
 '''Scope of API Management'''<ref>What is the Scope of API Management? [https://community.apigee.com/articles/19100/what-is-api-management.html|The Scope of API Management]</ref><br />
 The scope of API Management includes:
-*The process of publishing, promoting, and overseeing APIs in a secure, scalable environment
+*The [[process]] of publishing, promoting, and overseeing APIs in a secure, scalable environment
 *Ensuring that developers and partners are productive
 *Managing, securing, and mediating your API traffic
 *Allowing an organization to grow their API program to meet increasing demands
 *Enabling the monetization of APIs
-*The intersection of technology, business, organization, and integration concerns
+*The intersection of technology, [[business]], organization, and integration concerns
-An effective API Management solution manages the use of APIs to open up an organization or a system's data so that it can be utilized by other parts of the organization or possibly third-party organizations in new and useful ways. A for-profit organization would use these capabilities to either create new revenue streams of revenue or enhance/optimize existing revenue streams (monetizing APIs); a non-profit organization or government organization may be trying to cover its operational costs while fulfilling its mission to provide benefit (in this case, in the form of data/information) to the public. API Management should provide an easy, effective, and efficient experience for the development community that is supposed to be using those
+An effective API Management solution manages the use of APIs to open up an organization or a system's data so that it can be utilized by other parts of the organization or possibly third-party organizations in new and useful ways. A for-[[profit]] organization would use these capabilities to either create new revenue streams of revenue or enhance/optimize existing revenue streams (monetizing APIs); a non-profit organization or government organization may be trying to cover its operational costs while fulfilling its [[mission]] to provide benefit (in this case, in the form of data/information) to the public. API Management should provide an easy, effective, and efficient experience for the development community that is supposed to be using those
-APIs. API Management also provides a governance and life-cycle framework for APIs.
+APIs. API Management also provides a [[governance]] and life-cycle [[framework]] for APIs.
-From a business perspective, API Management is a revolution; from a technical perspective, it is an evolution of the earlier Service Oriented Architecture (SOA) paradigm. While API management includes much more than the SOA concepts of the early 2000’s, those concepts are still present. If anything, API management is partly a response to the flaws in early SOA strategies.
+From a business perspective, API Management is a revolution; from a technical perspective, it is an evolution of the earlier [[Service]] Oriented [[Architecture]] (SOA) paradigm. While API management includes much more than the SOA concepts of the early 2000’s, those concepts are still present. If anything, API management is partly a response to the flaws in early SOA strategies.
 '''Components of API Management'''<ref>Components of API Management [https://en.wikipedia.org/wiki/API_management Wikipedia]</ref><br />
 While solutions vary, the following functionality is typically found in API management products:
-*Gateway: servers that act as API front-end, receive API requests, enforce throttling and security policies, pass the calls to the back-end service, and then pass the response back to the invoker. Gateways often include transformation engines to orchestrate and modify the requests and responses on the fly. They can also collect analytics data, provide caching and other functionality.
+*Gateway: servers that act as API front-end, receive API requests, enforce throttling and security policies, pass the calls to the back-end service, and then pass the response back to the invoker. Gateways often include transformation engines to orchestrate and modify the requests and responses on the fly. They can also collect [[analytics]] data, provide caching and other functionality.
 *Publishing tools: user interface that API providers use to define the APIs and their access and usage policies, debug execution, manage API lifecycle.
-*Developer portal / API store: community site for API subscribers that is typically branded by API providers and includes documentation, interactive API console to try the APIs, ability to subscribe to the APIs and manage subscription keys, and get support from the API vendor and community.
+*Developer portal / API store: community site for API subscribers that is typically branded by API providers and includes documentation, interactive API console to try the APIs, ability to subscribe to the APIs and manage subscription keys, and get support from the API [[vendor]] and community.
 *Reporting and analytics: reports on API usage and subscriber behavior that let API publisher optimize their offering.
 *Monetization: ability to charge money for commercial APIs.

← Older revision		Revision as of 21:51, 23 September 2019
Line 39:		Line 39:
	*API Management 101: The Basics of API Management [http://www.apiacademy.co/resources/api-management-101-api-management-basics/ API Academy]		*API Management 101: The Basics of API Management [http://www.apiacademy.co/resources/api-management-101-api-management-basics/ API Academy]
	*What is API Management [http://searchmicroservices.techtarget.com/definition/API-management Techtarget]		*What is API Management [http://searchmicroservices.techtarget.com/definition/API-management Techtarget]
		+
		+
		+
		+	=== See Also ===
		+	[[IT Strategy (Information Technology Strategy)\|IT Strategic Planning]]<br />
		+	[[E-Strategy\|e-Business Strategic Planning]]<br />
		+	[[IT Governance\|Governance of Information Technology (ICT)]]<br />
		+	[[Enterprise Architecture\|What is Enterprise Architecture Planning]]<br />
		+	[[IT Sourcing (Information Technology Sourcing)\|Information Technology Sourcing (IT Sourcing)]]<br />
		+	[[IT Operations (Information Technology Operations)\|Information Technology Operations (IT Operations)]]<br />
		+	[[Chief Information Officer (CIO)\|Chief Information Officer (CIO)]]<br />
		+	[[Leadership\|Leadership]]<br />