Content deleted Content added
Cfwschmidt (talk | contribs) Moved citation from first sentence to end of the paragraph containing multiple claims supported by the source. |
m Reverted edits by 2806:263:482:1794:ADEC:812E:6500:3491 (talk) to last version by Ghent123 |
||
| (19 intermediate revisions by 6 users not shown) | |||
Line 3:
{{Other uses|OpenAPI (disambiguation){{!}}OpenAPI}}
An '''open API''' (often referred to as a public API) is a publicly available [[application programming interface]] that provides developers with programmatic access to a (possibly proprietary) [[Application software|software application]] or [[web service]].<ref>{{Cite web|url = http://readwrite.com/2013/09/19/api-defined|title = What APIs Are And Why They're Important|date = September 19, 2013|access-date = 28 October 2015|website = Readwrite|last = Proffitt|first = Brian}}</ref> Open APIs are APIs that are published on the [[internet]] and are free to access by consumers.<ref>{{Cite web |title=What is open API? - Definition from WhatIs.com |url=http://searchcloudapplications.techtarget.com/definition/open-API |access-date=2015-10-26 |website=SearchCloudApplications |archive-date=2017-04-30 |archive-url=https://web.archive.org/web/20170430125419/http://searchcloudapplications.techtarget.com/definition/open-API |url-status=dead }}</ref>
== Alternative Definitions ==
Line 20:
=== Open API ===
In contrast to a private API, an open API is publicly available for all developers to access. They allow developers, outside of an organization's workforce, to access backend data that can then be used to enhance their own applications. Open APIs can significantly increase revenue without the business having to invest in hiring new developers making them a very profitable software application.<ref>{{Cite web|title = Beat the risks of managing public, private APIs|url = http://searchsoa.techtarget.com/feature/Beat-the-risks-of-managing-public-private-APIs|website = SearchSOA|access-date = 2015-11-04|archive-date = 2015-11-25|archive-url = https://web.archive.org/web/20151125181803/http://searchsoa.techtarget.com/feature/Beat-the-risks-of-managing-public-private-APIs|url-status = dead}}</ref><ref>{{Cite journal |last1=Tündik |first1=Máté Ákos |last2=Szabó |first2=Zsolt |last3=Hilt |first3=Attila |last4=Járó |first4=Gábor |date=2024-11-12 |title=Fusion of Telecommunications and IT Services Boosted by Application Programming Interfaces |journal=Signals |language=en |volume=5 |issue=4 |pages=756–773 |doi=10.3390/signals5040042 |doi-access=free |issn=2624-6120}}</ref> However, opening back end information to the public can create a range of security and management challenges.<ref>{{Cite book|publisher = ACM|date = 2015-01-01|___location = New York, NY, USA|isbn = 978-1-4503-3832-5|pages = 44–56|series = CCS '15|doi = 10.1145/2810103.2813675|first1 = Zhui|last1 = Deng|first2 = Brendan|last2 = Saltaformaggio|first3 = Xiangyu|last3 = Zhang|first4 = Dongyan|last4 = Xu| title=Proceedings of the 22nd ACM SIGSAC Conference on Computer and Communications Security | chapter=IRiS | s2cid=5613038 }}</ref> For example, publishing open APIs can make it harder for organisations to control the experience end users have with their information assets. Open API publishers cannot assume client apps built on their APIs will offer a good user experience. Furthermore, they cannot fully ensure that client apps maintain the look and feel of their corporate branding.
== Open APIs in business ==
Line 49:
== References ==
{{Reflist}}{{Web interfaces}}
[[Category:Application programming interfaces]]
| |||