MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"parse": {
"title": "API",
"pageid": 0,
"text": {
"*": "<div class=\"mw-content-ltr mw-parser-output\" lang=\"en\" dir=\"ltr\"><div class=\"shortdescription nomobile noexcerpt noprint searchaux\" style=\"display:none\">Connection between computers or programs</div>\n<style data-mw-deduplicate=\"TemplateStyles:r1236090951\">.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}</style><div role=\"note\" class=\"hatnote navigation-not-searchable\">For other uses, see <a href=\"/wiki/API_(disambiguation)\" class=\"mw-disambig\" title=\"API (disambiguation)\">API (disambiguation)</a>.</div>\n<link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1236090951\" /><div role=\"note\" class=\"hatnote navigation-not-searchable selfref\">\"Api.php\" redirects here. For the Wikipedia API, see <span class=\"plainlinks\"><a href=\"/wiki/Special:ApiHelp\" title=\"Special:ApiHelp\">Special:ApiHelp</a></span>.</div>\n<p>An <b>application programming interface</b> (<b>API</b>) is a connection between <a href=\"/wiki/Computer\" title=\"Computer\">computers</a> or between <a href=\"/wiki/Computer_program\" title=\"Computer program\">computer programs</a>. It is a type of software <a href=\"/wiki/Interface_(computing)\" title=\"Interface (computing)\">interface</a>, offering a service to other pieces of <a href=\"/wiki/Software\" title=\"Software\">software</a>.<sup id=\"cite_ref-:0_1-0\" class=\"reference\"><a href=\"#cite_note-:0-1\"><span class=\"cite-bracket\">[</span>1<span class=\"cite-bracket\">]</span></a></sup> A document or standard that describes how to build such a connection or interface is called an <i>API specification</i>. A computer system that meets this standard is said to <i>implement</i> or <i>expose</i> an API. The term API may refer either to the specification or to the implementation.\n</p><p>In contrast to a <a href=\"/wiki/User_interface\" title=\"User interface\">user interface</a>, which connects a computer to a person, an application programming interface connects computers or pieces of software to each other. It is not intended to be used directly by a person (the <a href=\"/wiki/End_user\" title=\"End user\">end user</a>) other than a <a href=\"/wiki/Computer_programmer\" class=\"mw-redirect\" title=\"Computer programmer\">computer programmer</a><sup id=\"cite_ref-:0_1-1\" class=\"reference\"><a href=\"#cite_note-:0-1\"><span class=\"cite-bracket\">[</span>1<span class=\"cite-bracket\">]</span></a></sup> who is incorporating it into software. An API is often made up of different parts which act as tools or services that are available to the programmer. A program or a programmer that uses one of these parts is said to <i>call</i> that portion of the API. The calls that make up the API are also known as <a href=\"/wiki/Subroutine\" class=\"mw-redirect\" title=\"Subroutine\">subroutines</a>, methods, requests, or <a href=\"/wiki/Communication_endpoint\" title=\"Communication endpoint\">endpoints</a>. An API specification <i>defines</i> these calls, meaning that it explains how to use or implement them.\n</p><p>One purpose of APIs is to <a href=\"/wiki/Information_hiding\" title=\"Information hiding\">hide the internal details</a> of how a system works, exposing only those parts a programmer will find useful and keeping them consistent even if the internal details later change. An API may be custom-built for a particular pair of systems, or it may be a shared standard allowing <a href=\"/wiki/Interoperability\" title=\"Interoperability\">interoperability</a> among many systems.\n</p><p>The term API is often used to refer to <a href=\"/wiki/Web_API\" title=\"Web API\">web APIs</a>,<sup id=\"cite_ref-Lane2019_2-0\" class=\"reference\"><a href=\"#cite_note-Lane2019-2\"><span class=\"cite-bracket\">[</span>2<span class=\"cite-bracket\">]</span></a></sup> which allow communication between computers that are joined by the <a href=\"/wiki/Internet\" title=\"Internet\">internet</a>. There are also APIs for <a href=\"/wiki/Programming_language\" title=\"Programming language\">programming languages</a>, <a href=\"/wiki/Library_(computing)\" title=\"Library (computing)\">software libraries</a>, computer <a href=\"/wiki/Operating_system\" title=\"Operating system\">operating systems</a>, and <a href=\"/wiki/Computer_hardware\" title=\"Computer hardware\">computer hardware</a>. APIs originated in the 1940s, though the term did not emerge until the 1960s and 70s.\n</p>\n<meta property=\"mw:PageProp/toc\" />\n<div class=\"mw-heading mw-heading2\"><h2 id=\"Purpose\">Purpose</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=1\" title=\"Edit section: Purpose\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>An API opens a software system to interactions from the outside. It allows two software systems to communicate across a boundary \u2014 an interface \u2014 using mutually agreed-upon signals.<sup id=\"cite_ref-Pedro2024_3-0\" class=\"reference\"><a href=\"#cite_note-Pedro2024-3\"><span class=\"cite-bracket\">[</span>3<span class=\"cite-bracket\">]</span></a></sup> In other words, an API connects software entities together. Unlike a <a href=\"/wiki/User_interface\" title=\"User interface\">user interface</a>, an API is typically not visible to users. It is an \"under the hood\" portion of a software system, used for machine-to-machine communication.<sup id=\"cite_ref-4\" class=\"reference\"><a href=\"#cite_note-4\"><span class=\"cite-bracket\">[</span>4<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>A well-designed API exposes only objects or actions needed by software or software developers. It hides details that have no use. This <a href=\"/wiki/Abstraction_(software_engineering)\" class=\"mw-redirect\" title=\"Abstraction (software engineering)\">abstraction</a> simplifies programming.<sup id=\"cite_ref-Clarke4_5-0\" class=\"reference\"><a href=\"#cite_note-Clarke4-5\"><span class=\"cite-bracket\">[</span>5<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<figure class=\"mw-default-size\" typeof=\"mw:File/Thumb\"><a href=\"/wiki/File:LEGO-kompatiblo.jpg\" class=\"mw-file-description\"><img src=\"//upload.wikimedia.org/wikipedia/commons/thumb/0/04/LEGO-kompatiblo.jpg/220px-LEGO-kompatiblo.jpg\" decoding=\"async\" width=\"220\" height=\"187\" class=\"mw-file-element\" srcset=\"//upload.wikimedia.org/wikipedia/commons/0/04/LEGO-kompatiblo.jpg 1.5x\" data-file-width=\"300\" data-file-height=\"255\" /></a><figcaption>Metaphorically, APIs connect software like interlocking blocks. </figcaption></figure>\n<p>Building software using APIs has been compared to using building-block toys, such as <a href=\"/wiki/Lego\" title=\"Lego\">Lego</a> bricks. Software services or software libraries are analogous to the bricks; they may be joined together via their APIs, composing a new software product.<sup id=\"cite_ref-6\" class=\"reference\"><a href=\"#cite_note-6\"><span class=\"cite-bracket\">[</span>6<span class=\"cite-bracket\">]</span></a></sup> The process of joining is called <i>integration</i>.<sup id=\"cite_ref-Pedro2024_3-1\" class=\"reference\"><a href=\"#cite_note-Pedro2024-3\"><span class=\"cite-bracket\">[</span>3<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>As an example, consider a weather sensor that offers an API. When a certain message is transmitted to the sensor, it will detect the current weather conditions and reply with a weather report. The message that activates the sensor is an API <i>call</i>, and the weather report is an API <i>response</i>.<sup id=\"cite_ref-7\" class=\"reference\"><a href=\"#cite_note-7\"><span class=\"cite-bracket\">[</span>7<span class=\"cite-bracket\">]</span></a></sup> A weather forecasting app might integrate with a number of weather sensor APIs, gathering weather data from throughout a geographical area.\n</p><p>An API is often compared to a <a href=\"/wiki/Contract\" title=\"Contract\">contract</a>. It represents an agreement between parties: a service provider who offers the API and the software developers who rely upon it. If the API remains stable, or if it changes only in predictable ways, developers' confidence in the API will increase. This may increase their use of the API.<sup id=\"cite_ref-8\" class=\"reference\"><a href=\"#cite_note-8\"><span class=\"cite-bracket\">[</span>8<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"History_of_the_term\">History of the term</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=2\" title=\"Edit section: History of the term\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<figure class=\"mw-default-size mw-halign-left\" typeof=\"mw:File/Thumb\"><a href=\"/wiki/File:Database_management_system_diagram_from_1978_workshop.png\" class=\"mw-file-description\"><img src=\"//upload.wikimedia.org/wikipedia/commons/thumb/4/41/Database_management_system_diagram_from_1978_workshop.png/220px-Database_management_system_diagram_from_1978_workshop.png\" decoding=\"async\" width=\"220\" height=\"348\" class=\"mw-file-element\" srcset=\"//upload.wikimedia.org/wikipedia/commons/thumb/4/41/Database_management_system_diagram_from_1978_workshop.png/330px-Database_management_system_diagram_from_1978_workshop.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/4/41/Database_management_system_diagram_from_1978_workshop.png/440px-Database_management_system_diagram_from_1978_workshop.png 2x\" data-file-width=\"474\" data-file-height=\"750\" /></a><figcaption>A diagram from 1978 proposing the expansion of the idea of the API to become a general programming interface, beyond <a href=\"/wiki/Application_program\" class=\"mw-redirect\" title=\"Application program\">application programs</a> alone<sup id=\"cite_ref-NBS1981_9-0\" class=\"reference\"><a href=\"#cite_note-NBS1981-9\"><span class=\"cite-bracket\">[</span>9<span class=\"cite-bracket\">]</span></a></sup></figcaption></figure>\n<p>The term <i>API</i> initially described an interface only for end-user-facing programs, known as <a href=\"/wiki/Application_program\" class=\"mw-redirect\" title=\"Application program\">application programs</a>. This origin is still reflected in the name \"application programming interface.\" Today, the term is broader, including also <a href=\"/wiki/Utility_software\" title=\"Utility software\">utility software</a> and even <a href=\"/wiki/Hardware_interface_design\" title=\"Hardware interface design\">hardware interfaces</a>.<sup id=\"cite_ref-Bloch2018_10-0\" class=\"reference\"><a href=\"#cite_note-Bloch2018-10\"><span class=\"cite-bracket\">[</span>10<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>The idea of the API is much older than the term itself. British computer scientists <a href=\"/wiki/Maurice_Wilkes\" title=\"Maurice Wilkes\">Maurice Wilkes</a> and <a href=\"/wiki/David_Wheeler_(computer_scientist)\" title=\"David Wheeler (computer scientist)\">David Wheeler</a> worked on a modular <a href=\"/wiki/Software_library\" class=\"mw-redirect\" title=\"Software library\">software library</a> in the 1940s for <a href=\"/wiki/EDSAC\" title=\"EDSAC\">EDSAC</a>, an early computer. The <a href=\"/wiki/Subroutine\" class=\"mw-redirect\" title=\"Subroutine\">subroutines</a> in this library were stored on <a href=\"/wiki/Punched_paper_tape\" class=\"mw-redirect\" title=\"Punched paper tape\">punched paper tape</a> organized in a <a href=\"/wiki/Filing_cabinet\" title=\"Filing cabinet\">filing cabinet</a>. This cabinet also contained what Wilkes and Wheeler called a \"library catalog\" of notes about each subroutine and how to incorporate it into a program. Today, such a catalog would be called an API (or an API specification or API documentation) because it instructs a programmer on how to use (or \"call\") each subroutine that the programmer needs.<sup id=\"cite_ref-Bloch2018_10-1\" class=\"reference\"><a href=\"#cite_note-Bloch2018-10\"><span class=\"cite-bracket\">[</span>10<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>Wilkes and Wheeler's book <i><a href=\"/wiki/The_Preparation_of_Programs_for_an_Electronic_Digital_Computer\" title=\"The Preparation of Programs for an Electronic Digital Computer\">The Preparation of Programs for an Electronic Digital Computer</a></i> contains the first published API specification. <a href=\"/wiki/Joshua_Bloch\" title=\"Joshua Bloch\">Joshua Bloch</a> considers that Wilkes and Wheeler \"latently invented\" the API, because it is more of a concept that is discovered than invented.<sup id=\"cite_ref-Bloch2018_10-2\" class=\"reference\"><a href=\"#cite_note-Bloch2018-10\"><span class=\"cite-bracket\">[</span>10<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<figure typeof=\"mw:File/Thumb\"><a href=\"/wiki/File:Univac_1108_Census_Bureau.jpg\" class=\"mw-file-description\"><img src=\"//upload.wikimedia.org/wikipedia/commons/thumb/8/85/Univac_1108_Census_Bureau.jpg/300px-Univac_1108_Census_Bureau.jpg\" decoding=\"async\" width=\"300\" height=\"195\" class=\"mw-file-element\" srcset=\"//upload.wikimedia.org/wikipedia/commons/thumb/8/85/Univac_1108_Census_Bureau.jpg/450px-Univac_1108_Census_Bureau.jpg 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/8/85/Univac_1108_Census_Bureau.jpg/600px-Univac_1108_Census_Bureau.jpg 2x\" data-file-width=\"1799\" data-file-height=\"1172\" /></a><figcaption>Although the people who coined the term API were implementing software on a <a href=\"/wiki/UNIVAC_1100/2200_series#1108\" title=\"UNIVAC 1100/2200 series\">Univac 1108</a>, the goal of their API was to make <a href=\"/wiki/Hardware_independent\" class=\"mw-redirect\" title=\"Hardware independent\">hardware independent</a> programs possible.<sup id=\"cite_ref-CottonGreatorex1968_11-0\" class=\"reference\"><a href=\"#cite_note-CottonGreatorex1968-11\"><span class=\"cite-bracket\">[</span>11<span class=\"cite-bracket\">]</span></a></sup></figcaption></figure>\n<p>The term \"application program interface\" (without an <i>-ing</i> suffix) is first recorded in a paper called <i>Data structures and techniques for remote <a href=\"/wiki/Computer_graphics\" title=\"Computer graphics\">computer graphics</a></i> presented at an <a href=\"/wiki/AFIPS\" class=\"mw-redirect\" title=\"AFIPS\">AFIPS</a> conference in 1968.<sup id=\"cite_ref-12\" class=\"reference\"><a href=\"#cite_note-12\"><span class=\"cite-bracket\">[</span>12<span class=\"cite-bracket\">]</span></a></sup><sup id=\"cite_ref-Bloch2018_10-3\" class=\"reference\"><a href=\"#cite_note-Bloch2018-10\"><span class=\"cite-bracket\">[</span>10<span class=\"cite-bracket\">]</span></a></sup> The authors of this paper use the term to describe the interaction of an <a href=\"/wiki/Application_software\" title=\"Application software\">application</a>\u2014a graphics program in this case\u2014with the rest of the computer system. A consistent application interface (consisting of <a href=\"/wiki/Fortran\" title=\"Fortran\">Fortran</a> subroutine calls) was intended to free the programmer from dealing with idiosyncrasies of the graphics display device, and to provide <a href=\"/wiki/Hardware_independence\" class=\"mw-redirect\" title=\"Hardware independence\">hardware independence</a> if the computer or the display were replaced.<sup id=\"cite_ref-CottonGreatorex1968_11-1\" class=\"reference\"><a href=\"#cite_note-CottonGreatorex1968-11\"><span class=\"cite-bracket\">[</span>11<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>The term was introduced to the field of <a href=\"/wiki/Database\" title=\"Database\">databases</a> by <a href=\"/wiki/Christopher_J._Date\" title=\"Christopher J. Date\">C. J. Date</a><sup id=\"cite_ref-13\" class=\"reference\"><a href=\"#cite_note-13\"><span class=\"cite-bracket\">[</span>13<span class=\"cite-bracket\">]</span></a></sup> in a 1974 paper called <i>The <a href=\"/wiki/Relational_database\" title=\"Relational database\">Relational</a> and <a href=\"/wiki/Network_model\" title=\"Network model\">Network</a> Approaches: Comparison of the Application Programming Interface</i>.<sup id=\"cite_ref-14\" class=\"reference\"><a href=\"#cite_note-14\"><span class=\"cite-bracket\">[</span>14<span class=\"cite-bracket\">]</span></a></sup> An API became a part of the <a href=\"/wiki/ANSI-SPARC_Architecture\" title=\"ANSI-SPARC Architecture\">ANSI/SPARC framework</a> for <a href=\"/wiki/Database_management_system\" class=\"mw-redirect\" title=\"Database management system\">database management systems</a>. This framework treated the application programming interface separately from other interfaces, such as the query interface. Database professionals in the 1970s observed these different interfaces could be combined; a sufficiently rich application interface could support the other interfaces as well.<sup id=\"cite_ref-NBS1981_9-1\" class=\"reference\"><a href=\"#cite_note-NBS1981-9\"><span class=\"cite-bracket\">[</span>9<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>This observation led to APIs that supported all types of programming, not just application programming. By 1990, the API was defined simply as \"a set of services available to a programmer for performing certain tasks\" by technologist <a href=\"/wiki/Carl_Malamud\" title=\"Carl Malamud\">Carl Malamud</a>.<sup id=\"cite_ref-15\" class=\"reference\"><a href=\"#cite_note-15\"><span class=\"cite-bracket\">[</span>15<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<figure class=\"mw-default-size\" typeof=\"mw:File/Thumb\"><a href=\"/wiki/File:Screenshot_of_NASA_API_documentation.png\" class=\"mw-file-description\"><img src=\"//upload.wikimedia.org/wikipedia/commons/thumb/c/c0/Screenshot_of_NASA_API_documentation.png/220px-Screenshot_of_NASA_API_documentation.png\" decoding=\"async\" width=\"220\" height=\"328\" class=\"mw-file-element\" srcset=\"//upload.wikimedia.org/wikipedia/commons/thumb/c/c0/Screenshot_of_NASA_API_documentation.png/330px-Screenshot_of_NASA_API_documentation.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/c/c0/Screenshot_of_NASA_API_documentation.png/440px-Screenshot_of_NASA_API_documentation.png 2x\" data-file-width=\"1026\" data-file-height=\"1530\" /></a><figcaption>Screenshot of <a href=\"/wiki/Web_API\" title=\"Web API\">Web API</a> documentation written by <a href=\"/wiki/NASA\" title=\"NASA\">NASA</a></figcaption></figure>\n<p>The idea of the API was expanded again with the dawn of <a href=\"/wiki/Remote_procedure_calls\" class=\"mw-redirect\" title=\"Remote procedure calls\">remote procedure calls</a> and <a href=\"/wiki/Web_API\" title=\"Web API\">web APIs</a>. As <a href=\"/wiki/Computer_network\" title=\"Computer network\">computer networks</a> became common in the 1970s and 80s, programmers wanted to call libraries located not only on their local computers, but on computers located elsewhere. These remote procedure calls were well supported by the <a href=\"/wiki/Java_(programming_language)\" title=\"Java (programming language)\">Java</a> language in particular. In the 1990s, with the spread of the <a href=\"/wiki/Internet\" title=\"Internet\">internet</a>, standards like <a href=\"/wiki/CORBA\" class=\"mw-redirect\" title=\"CORBA\">CORBA</a>, <a href=\"/wiki/Component_Object_Model\" title=\"Component Object Model\">COM</a>, and <a href=\"/wiki/Distributed_Component_Object_Model\" title=\"Distributed Component Object Model\">DCOM</a> competed to become the most common way to expose API services.<sup id=\"cite_ref-JinSahniShevat2018_16-0\" class=\"reference\"><a href=\"#cite_note-JinSahniShevat2018-16\"><span class=\"cite-bracket\">[</span>16<span class=\"cite-bracket\">]</span></a></sup>\n</p><p><a href=\"/wiki/Roy_Fielding\" title=\"Roy Fielding\">Roy Fielding</a>'s dissertation <i>Architectural Styles and the Design of Network-based Software Architectures</i> at <a href=\"/wiki/UC_Irvine\" class=\"mw-redirect\" title=\"UC Irvine\">UC Irvine</a> in 2000 outlined <a href=\"/wiki/Representational_state_transfer\" class=\"mw-redirect\" title=\"Representational state transfer\">Representational state transfer</a> (REST) and described the idea of a \"network-based Application Programming Interface\" that Fielding contrasted with traditional \"library-based\" APIs.<sup id=\"cite_ref-17\" class=\"reference\"><a href=\"#cite_note-17\"><span class=\"cite-bracket\">[</span>17<span class=\"cite-bracket\">]</span></a></sup> <a href=\"/wiki/XML\" title=\"XML\">XML</a> and <a href=\"/wiki/JSON\" title=\"JSON\">JSON</a> web APIs saw widespread commercial adoption beginning in 2000 and continuing as of 2021. The web API is now the most common meaning of the term API.<sup id=\"cite_ref-Lane2019_2-1\" class=\"reference\"><a href=\"#cite_note-Lane2019-2\"><span class=\"cite-bracket\">[</span>2<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>The <a href=\"/wiki/Semantic_Web\" title=\"Semantic Web\">Semantic Web</a> proposed by <a href=\"/wiki/Tim_Berners-Lee\" title=\"Tim Berners-Lee\">Tim Berners-Lee</a> in 2001 included \"semantic APIs\" that recast the API as an <a href=\"/wiki/Open_innovation\" title=\"Open innovation\">open</a>, distributed data interface rather than a software behavior interface.<sup id=\"cite_ref-18\" class=\"reference\"><a href=\"#cite_note-18\"><span class=\"cite-bracket\">[</span>18<span class=\"cite-bracket\">]</span></a></sup> <a href=\"/wiki/Proprietary_software\" title=\"Proprietary software\">Proprietary</a> interfaces and agents became more widespread than open ones, but the idea of the API as a data interface took hold. Because web APIs are widely used to exchange data of all kinds online, API has become a broad term describing much of the communication on the internet.<sup id=\"cite_ref-JinSahniShevat2018_16-1\" class=\"reference\"><a href=\"#cite_note-JinSahniShevat2018-16\"><span class=\"cite-bracket\">[</span>16<span class=\"cite-bracket\">]</span></a></sup> When used in this way, the term API has overlap in meaning with the term <a href=\"/wiki/Communication_protocol\" title=\"Communication protocol\">communication protocol</a>.\n</p>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"Types\">Types</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=3\" title=\"Edit section: Types\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<div class=\"mw-heading mw-heading3\"><h3 id=\"Libraries_and_frameworks\">Libraries and frameworks</h3><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=4\" title=\"Edit section: Libraries and frameworks\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>The interface to a <a href=\"/wiki/Library_(computing)\" title=\"Library (computing)\">software library</a> is one type of API. The API describes and prescribes the \"expected behavior\" (a specification) while the library is an \"actual implementation\" of this set of rules.\n</p><p>A single API can have multiple implementations (or none, being abstract) in the form of different libraries that share the same programming interface.\n</p><p>The separation of the API from its implementation can allow programs written in one language to use a library written in another. For example, because <a href=\"/wiki/Scala_(programming_language)\" title=\"Scala (programming language)\">Scala</a> and <a href=\"/wiki/Java_(programming_language)\" title=\"Java (programming language)\">Java</a> compile to compatible <a href=\"/wiki/Bytecode\" title=\"Bytecode\">bytecode</a>, Scala developers can take advantage of any Java API.<sup id=\"cite_ref-OderskySpoonVenners8_19-0\" class=\"reference\"><a href=\"#cite_note-OderskySpoonVenners8-19\"><span class=\"cite-bracket\">[</span>19<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>API use can vary depending on the type of programming language involved.\nAn API for a <a href=\"/wiki/Procedural_programming\" title=\"Procedural programming\">procedural language</a> such as <a href=\"/wiki/Lua_(programming_language)\" title=\"Lua (programming language)\">Lua</a> could consist primarily of basic routines to execute code, manipulate data or handle errors while an API for an <a href=\"/wiki/Object-oriented_programming\" title=\"Object-oriented programming\">object-oriented language</a>, such as Java, would provide a specification of classes and its <a href=\"/wiki/Class_method\" class=\"mw-redirect\" title=\"Class method\">class methods</a>.<sup id=\"cite_ref-20\" class=\"reference\"><a href=\"#cite_note-20\"><span class=\"cite-bracket\">[</span>20<span class=\"cite-bracket\">]</span></a></sup><sup id=\"cite_ref-Sintes16_21-0\" class=\"reference\"><a href=\"#cite_note-Sintes16-21\"><span class=\"cite-bracket\">[</span>21<span class=\"cite-bracket\">]</span></a></sup> <style data-mw-deduplicate=\"TemplateStyles:r1238216509\">.mw-parser-output .vanchor>:target~.vanchor-text{background-color:#b1d2ff}@media screen{html.skin-theme-clientpref-night .mw-parser-output .vanchor>:target~.vanchor-text{background-color:#0f4dc9}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .vanchor>:target~.vanchor-text{background-color:#0f4dc9}}</style><span class=\"vanchor\"><span id=\"Hyrums\"></span><span class=\"vanchor-text\">Hyrum's law states that \"With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody.\"</span></span><sup id=\"cite_ref-22\" class=\"reference\"><a href=\"#cite_note-22\"><span class=\"cite-bracket\">[</span>22<span class=\"cite-bracket\">]</span></a></sup> Meanwhile, several studies show that most applications that use an API tend to use a small part of the API.<sup id=\"cite_ref-23\" class=\"reference\"><a href=\"#cite_note-23\"><span class=\"cite-bracket\">[</span>23<span class=\"cite-bracket\">]</span></a></sup>\n</p><p><a href=\"/wiki/Language_binding\" title=\"Language binding\">Language bindings</a> are also APIs. By mapping the features and capabilities of one language to an interface implemented in another language, a language binding allows a library or service written in one language to be used when developing in another language.<sup id=\"cite_ref-Emery_24-0\" class=\"reference\"><a href=\"#cite_note-Emery-24\"><span class=\"cite-bracket\">[</span>24<span class=\"cite-bracket\">]</span></a></sup> Tools such as <a href=\"/wiki/SWIG\" title=\"SWIG\">SWIG</a> and F2PY, a <a href=\"/wiki/Fortran\" title=\"Fortran\">Fortran</a>-to-<a href=\"/wiki/Python_(programming_language)\" title=\"Python (programming language)\">Python</a> interface generator, facilitate the creation of such interfaces.<sup id=\"cite_ref-25\" class=\"reference\"><a href=\"#cite_note-25\"><span class=\"cite-bracket\">[</span>25<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>An API can also be related to a <a href=\"/wiki/Framework_(computer_science)\" class=\"mw-redirect\" title=\"Framework (computer science)\">software framework</a>: a framework can be based on several libraries implementing several APIs, but unlike the normal use of an API, the access to the behavior built into the framework is mediated by extending its content with new classes plugged into the framework itself.\n</p><p>Moreover, the overall program flow of control can be out of the control of the caller and in the framework's hands by <a href=\"/wiki/Inversion_of_control\" title=\"Inversion of control\">inversion of control</a> or a similar mechanism.<sup id=\"cite_ref-26\" class=\"reference\"><a href=\"#cite_note-26\"><span class=\"cite-bracket\">[</span>26<span class=\"cite-bracket\">]</span></a></sup><sup id=\"cite_ref-27\" class=\"reference\"><a href=\"#cite_note-27\"><span class=\"cite-bracket\">[</span>27<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<div class=\"mw-heading mw-heading3\"><h3 id=\"Operating_systems\">Operating systems</h3><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=5\" title=\"Edit section: Operating systems\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>An API can specify the interface between an application and the <a href=\"/wiki/Operating_system\" title=\"Operating system\">operating system</a>.<sup id=\"cite_ref-Oreilly91_28-0\" class=\"reference\"><a href=\"#cite_note-Oreilly91-28\"><span class=\"cite-bracket\">[</span>28<span class=\"cite-bracket\">]</span></a></sup> <a href=\"/wiki/POSIX\" title=\"POSIX\">POSIX</a>, for example, specifies a set of common APIs that aim to enable an application written for a POSIX conformant operating system to be <a href=\"/wiki/Compiler\" title=\"Compiler\">compiled</a> for another POSIX conformant operating system.\n</p><p><a href=\"/wiki/Linux\" title=\"Linux\">Linux</a> and <a href=\"/wiki/Berkeley_Software_Distribution\" title=\"Berkeley Software Distribution\">Berkeley Software Distribution</a> are examples of operating systems that implement the POSIX APIs.<sup id=\"cite_ref-WestDedrick16_29-0\" class=\"reference\"><a href=\"#cite_note-WestDedrick16-29\"><span class=\"cite-bracket\">[</span>29<span class=\"cite-bracket\">]</span></a></sup>\n</p><p><a href=\"/wiki/Microsoft\" title=\"Microsoft\">Microsoft</a> has shown a strong commitment to a backward-compatible API, particularly within its <a href=\"/wiki/Windows_API\" title=\"Windows API\">Windows API</a> (Win32) library, so older applications may run on newer versions of Windows using an executable-specific setting called \"Compatibility Mode\".<sup id=\"cite_ref-30\" class=\"reference\"><a href=\"#cite_note-30\"><span class=\"cite-bracket\">[</span>30<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>An API differs from an <a href=\"/wiki/Application_binary_interface\" title=\"Application binary interface\">application binary interface</a> (ABI) in that an API is source code based while an ABI is <a href=\"/wiki/Binary_file\" title=\"Binary file\">binary</a> based. For instance, <a href=\"/wiki/POSIX\" title=\"POSIX\">POSIX</a> provides APIs while the <a href=\"/wiki/Linux_Standard_Base\" title=\"Linux Standard Base\">Linux Standard Base</a> provides an ABI.<sup id=\"cite_ref-31\" class=\"reference\"><a href=\"#cite_note-31\"><span class=\"cite-bracket\">[</span>31<span class=\"cite-bracket\">]</span></a></sup><sup id=\"cite_ref-32\" class=\"reference\"><a href=\"#cite_note-32\"><span class=\"cite-bracket\">[</span>32<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<div class=\"mw-heading mw-heading3\"><h3 id=\"Remote_APIs\">Remote APIs</h3><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=6\" title=\"Edit section: Remote APIs\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>Remote APIs allow developers to manipulate remote resources through <a href=\"/wiki/Communications_protocol\" class=\"mw-redirect\" title=\"Communications protocol\">protocols</a>, specific standards for communication that allow different technologies to work together, regardless of language or platform.\nFor example, the Java Database Connectivity API allows developers to query many different types of <a href=\"/wiki/Database\" title=\"Database\">databases</a> with the same set of functions, while the <a href=\"/wiki/Java_remote_method_invocation\" title=\"Java remote method invocation\">Java remote method invocation</a> API uses the Java Remote Method Protocol to allow <a href=\"/wiki/Remote_procedure_call\" title=\"Remote procedure call\">invocation</a> of functions that operate remotely, but appear local to the developer.<sup id=\"cite_ref-Bierhoff9_33-0\" class=\"reference\"><a href=\"#cite_note-Bierhoff9-33\"><span class=\"cite-bracket\">[</span>33<span class=\"cite-bracket\">]</span></a></sup><sup id=\"cite_ref-Wilson16_34-0\" class=\"reference\"><a href=\"#cite_note-Wilson16-34\"><span class=\"cite-bracket\">[</span>34<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>Therefore, remote APIs are useful in maintaining the object abstraction in <a href=\"/wiki/Object-oriented_programming\" title=\"Object-oriented programming\">object-oriented programming</a>; a <a href=\"/wiki/Method_call\" class=\"mw-redirect\" title=\"Method call\">method call</a>, executed locally on a <a href=\"/wiki/Proxy_pattern\" title=\"Proxy pattern\">proxy</a> object, invokes the corresponding method on the remote object, using the remoting protocol, and acquires the result to be used locally as a return value.\n</p><p>A modification of the proxy object will also result in a corresponding modification of the remote object.<sup id=\"cite_ref-AdvancedCorba_35-0\" class=\"reference\"><a href=\"#cite_note-AdvancedCorba-35\"><span class=\"cite-bracket\">[</span>35<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<div class=\"mw-heading mw-heading3\"><h3 id=\"Web_APIs\">Web APIs</h3><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=7\" title=\"Edit section: Web APIs\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1236090951\" /><div role=\"note\" class=\"hatnote navigation-not-searchable\">Main article: <a href=\"/wiki/Web_API\" title=\"Web API\">Web API</a></div>\n<p>Web APIs are the defined interfaces through which interactions happen between an enterprise and applications that use its assets, which also is a <a href=\"/wiki/Service-level_agreement\" title=\"Service-level agreement\">Service Level Agreement</a> (SLA) to specify the functional provider and expose the service path or URL for its API users. An API approach is an architectural approach that revolves around providing a program interface to a set of services to different applications serving different types of consumers.<sup id=\"cite_ref-36\" class=\"reference\"><a href=\"#cite_note-36\"><span class=\"cite-bracket\">[</span>36<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>When used in the context of <a href=\"/wiki/Web_development_tools\" title=\"Web development tools\">web development</a>, an API is typically defined as a set of specifications, such as <a href=\"/wiki/Hypertext_Transfer_Protocol\" class=\"mw-redirect\" title=\"Hypertext Transfer Protocol\">Hypertext Transfer Protocol</a> (HTTP) request messages, along with a definition of the structure of response messages, usually in an Extensible Markup Language (<a href=\"/wiki/XML\" title=\"XML\">XML</a>) or JavaScript Object Notation (<a href=\"/wiki/JSON\" title=\"JSON\">JSON</a>) format. An example might be a shipping company API that can be added to an eCommerce-focused website to facilitate ordering shipping services and automatically include current shipping rates, without the site developer having to enter the shipper's rate table into a web database. While \"web API\" historically has been virtually synonymous with <a href=\"/wiki/Web_service\" title=\"Web service\">web service</a>, the recent trend (so-called <a href=\"/wiki/Web_2.0\" title=\"Web 2.0\">Web 2.0</a>) has been moving away from Simple Object Access Protocol (<a href=\"/wiki/SOAP\" title=\"SOAP\">SOAP</a>) based web services and <a href=\"/wiki/Service-oriented_architecture\" title=\"Service-oriented architecture\">service-oriented architecture</a> (SOA) towards more direct <a href=\"/wiki/Representational_state_transfer\" class=\"mw-redirect\" title=\"Representational state transfer\">representational state transfer</a> (REST) style <a href=\"/wiki/Web_resource\" title=\"Web resource\">web resources</a> and <a href=\"/wiki/Resource-oriented_architecture\" title=\"Resource-oriented architecture\">resource-oriented architecture</a> (ROA).<sup id=\"cite_ref-37\" class=\"reference\"><a href=\"#cite_note-37\"><span class=\"cite-bracket\">[</span>37<span class=\"cite-bracket\">]</span></a></sup> Part of this trend is related to the <a href=\"/wiki/Semantic_Web\" title=\"Semantic Web\">Semantic Web</a> movement toward <a href=\"/wiki/Resource_Description_Framework\" title=\"Resource Description Framework\">Resource Description Framework</a> (RDF), a concept to promote web-based <a href=\"/wiki/Ontology_engineering\" title=\"Ontology engineering\">ontology engineering</a> technologies. Web APIs allow the combination of multiple APIs into new applications known as <a href=\"/wiki/Mashup_(web_application_hybrid)\" title=\"Mashup (web application hybrid)\">mashups</a>.<sup id=\"cite_ref-38\" class=\"reference\"><a href=\"#cite_note-38\"><span class=\"cite-bracket\">[</span>38<span class=\"cite-bracket\">]</span></a></sup>\nIn the social media space, web APIs have allowed web communities to facilitate sharing content and data between communities and applications. In this way, content that is created in one place dynamically can be posted and updated to multiple locations on the web.<sup id=\"cite_ref-Parr16_39-0\" class=\"reference\"><a href=\"#cite_note-Parr16-39\"><span class=\"cite-bracket\">[</span>39<span class=\"cite-bracket\">]</span></a></sup> For example, Twitter's REST API allows developers to access core Twitter data and the Search API provides methods for developers to interact with Twitter Search and trends data.<sup id=\"cite_ref-40\" class=\"reference\"><a href=\"#cite_note-40\"><span class=\"cite-bracket\">[</span>40<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"Design\">Design</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=8\" title=\"Edit section: Design\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>The design of an API has significant impact on its usage.<sup id=\"cite_ref-Clarke4_5-1\" class=\"reference\"><a href=\"#cite_note-Clarke4-5\"><span class=\"cite-bracket\">[</span>5<span class=\"cite-bracket\">]</span></a></sup> The principle of <a href=\"/wiki/Information_hiding\" title=\"Information hiding\">information hiding</a> describes the role of programming interfaces as enabling <a href=\"/wiki/Modular_programming\" title=\"Modular programming\">modular programming</a> by hiding the implementation details of the modules so that users of modules need not understand the complexities inside the modules.<sup id=\"cite_ref-Parnas72_41-0\" class=\"reference\"><a href=\"#cite_note-Parnas72-41\"><span class=\"cite-bracket\">[</span>41<span class=\"cite-bracket\">]</span></a></sup> Thus, the design of an API attempts to provide only the tools a user would expect.<sup id=\"cite_ref-Clarke4_5-2\" class=\"reference\"><a href=\"#cite_note-Clarke4-5\"><span class=\"cite-bracket\">[</span>5<span class=\"cite-bracket\">]</span></a></sup> The design of programming interfaces represents an important part of <a href=\"/wiki/Software_architecture\" title=\"Software architecture\">software architecture</a>, the organization of a complex piece of software.<sup id=\"cite_ref-GarlanShaw94_42-0\" class=\"reference\"><a href=\"#cite_note-GarlanShaw94-42\"><span class=\"cite-bracket\">[</span>42<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"Release_policies\">Release policies</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=9\" title=\"Edit section: Release policies\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>APIs are one of the more common ways technology companies integrate. Those that provide and use APIs are considered as being members of a business ecosystem.<sup id=\"cite_ref-43\" class=\"reference\"><a href=\"#cite_note-43\"><span class=\"cite-bracket\">[</span>43<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>The main policies for releasing an API are:<sup id=\"cite_ref-Boyd16_44-0\" class=\"reference\"><a href=\"#cite_note-Boyd16-44\"><span class=\"cite-bracket\">[</span>44<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<ul><li><u>Private</u>: The API is for internal company use only.</li>\n<li><u>Partner</u>: Only specific business partners can use the API. For example, <a href=\"/wiki/Vehicle_for_hire\" title=\"Vehicle for hire\">vehicle for hire</a> companies such as <a href=\"/wiki/Uber\" title=\"Uber\">Uber</a> and <a href=\"/wiki/Lyft\" title=\"Lyft\">Lyft</a> allow approved third-party developers to directly order rides from within their apps. This allows the companies to exercise quality control by curating which apps have access to the API, and provides them with an additional revenue stream.<sup id=\"cite_ref-45\" class=\"reference\"><a href=\"#cite_note-45\"><span class=\"cite-bracket\">[</span>45<span class=\"cite-bracket\">]</span></a></sup></li>\n<li><u>Public</u>: The API is available for use by the public. For example, <a href=\"/wiki/Microsoft\" title=\"Microsoft\">Microsoft</a> makes the <a href=\"/wiki/Windows_API\" title=\"Windows API\">Windows API</a> public, and <a href=\"/wiki/Apple_Inc.\" title=\"Apple Inc.\">Apple</a> releases its API <a href=\"/wiki/Cocoa_(API)\" title=\"Cocoa (API)\">Cocoa</a>, so that software can be written for their <a href=\"/wiki/Computing_platform\" title=\"Computing platform\">platforms</a>. Not all public APIs are generally accessible by everybody. For example, Internet service providers like Cloudflare or Voxility, use <a href=\"/wiki/RESTful\" class=\"mw-redirect\" title=\"RESTful\">RESTful</a> APIs to allow customers and resellers access to their infrastructure information, DDoS stats, network performance or dashboard controls.<sup id=\"cite_ref-Cloudflare_46-0\" class=\"reference\"><a href=\"#cite_note-Cloudflare-46\"><span class=\"cite-bracket\">[</span>46<span class=\"cite-bracket\">]</span></a></sup> Access to such APIs is granted either by \u201cAPI tokens\u201d, or customer status validations.<sup id=\"cite_ref-SmashMagazine_47-0\" class=\"reference\"><a href=\"#cite_note-SmashMagazine-47\"><span class=\"cite-bracket\">[</span>47<span class=\"cite-bracket\">]</span></a></sup></li></ul>\n<div class=\"mw-heading mw-heading3\"><h3 id=\"Public_API_implications\">Public API implications</h3><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=10\" title=\"Edit section: Public API implications\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>An important factor when an API becomes public is its \"interface stability\". Changes to the API\u2014for example adding new parameters to a function call\u2014could break compatibility with the clients that depend on that API.<sup id=\"cite_ref-researchgate.net_48-0\" class=\"reference\"><a href=\"#cite_note-researchgate.net-48\"><span class=\"cite-bracket\">[</span>48<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>When parts of a publicly presented API are subject to change and thus not stable, such parts of a particular API should be documented explicitly as \"unstable\". For example, in the <a href=\"/wiki/Google_Guava\" title=\"Google Guava\">Google Guava</a> library, the parts that are considered unstable, and that might change soon, are marked with the <a href=\"/wiki/Java_annotation\" title=\"Java annotation\">Java annotation</a> <code>@Beta</code>.<sup id=\"cite_ref-49\" class=\"reference\"><a href=\"#cite_note-49\"><span class=\"cite-bracket\">[</span>49<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>A public API can sometimes declare parts of itself as <i>deprecated</i> or rescinded. This usually means that part of the API should be considered a candidate for being removed, or modified in a backward incompatible way. Therefore, these changes allow developers to transition away from parts of the API that will be removed or not supported in the future.<sup id=\"cite_ref-OracleDeprecation16_50-0\" class=\"reference\"><a href=\"#cite_note-OracleDeprecation16-50\"><span class=\"cite-bracket\">[</span>50<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>Client code may contain innovative or opportunistic usages that were not intended by the API designers. In other words, for a library with a significant user base, when an element becomes part of the public API, it may be used in diverse ways.<sup id=\"cite_ref-MendezBaudry2013_51-0\" class=\"reference\"><a href=\"#cite_note-MendezBaudry2013-51\"><span class=\"cite-bracket\">[</span>51<span class=\"cite-bracket\">]</span></a></sup>\nOn February 19, 2020, <a href=\"/wiki/Akamai_Technologies\" title=\"Akamai Technologies\">Akamai</a> published their annual \u201cState of the Internet\u201d report, showcasing the growing trend of cybercriminals targeting public API platforms at financial services worldwide. From December 2017 through November 2019, Akamai witnessed 85.42 billion credential violation attacks. About 20%, or 16.55 billion, were against hostnames defined as API endpoints. Of these, 473.5 million have targeted financial services sector organizations.<sup id=\"cite_ref-VentureBeat_52-0\" class=\"reference\"><a href=\"#cite_note-VentureBeat-52\"><span class=\"cite-bracket\">[</span>52<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"Documentation\">Documentation</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=11\" title=\"Edit section: Documentation\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>API documentation describes what services an API offers and how to use those services, aiming to cover everything a client would need to know for practical purposes.\n</p><p>Documentation is crucial for the development and maintenance of applications using the API.<sup id=\"cite_ref-DekelHerbsleb9_53-0\" class=\"reference\"><a href=\"#cite_note-DekelHerbsleb9-53\"><span class=\"cite-bracket\">[</span>53<span class=\"cite-bracket\">]</span></a></sup>\nAPI documentation is traditionally found in documentation files but can also be found in social media such as blogs, forums, and Q&A websites.<sup id=\"cite_ref-ParninTreude11_54-0\" class=\"reference\"><a href=\"#cite_note-ParninTreude11-54\"><span class=\"cite-bracket\">[</span>54<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>Traditional documentation files are often presented via a documentation system, such as Javadoc or Pydoc, that has a consistent appearance and structure.\nHowever, the types of content included in the documentation differs from API to API.<sup id=\"cite_ref-MaalejRobillard12_55-0\" class=\"reference\"><a href=\"#cite_note-MaalejRobillard12-55\"><span class=\"cite-bracket\">[</span>55<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>In the interest of clarity, API documentation may include a description of classes and methods in the API as well as \"typical usage scenarios, code snippets, design rationales, performance discussions, and contracts\", but implementation details of the API services themselves are usually omitted. It can take a number of forms, including instructional documents, tutorials, and reference works. It'll also include a variety of information types, including guides and functionalities.\n</p><p>Restrictions and limitations on how the API can be used are also covered by the documentation. For instance, documentation for an API function could note that its parameters cannot be null, that the function itself is not <a href=\"/wiki/Thread_safety\" title=\"Thread safety\">thread safe</a>.<sup id=\"cite_ref-MonperrusEichberg11_56-0\" class=\"reference\"><a href=\"#cite_note-MonperrusEichberg11-56\"><span class=\"cite-bracket\">[</span>56<span class=\"cite-bracket\">]</span></a></sup> Because API documentation tends to be comprehensive, it is a challenge for writers to keep the documentation updated and for users to read it carefully, potentially yielding bugs.<sup id=\"cite_ref-researchgate.net_48-1\" class=\"reference\"><a href=\"#cite_note-researchgate.net-48\"><span class=\"cite-bracket\">[</span>48<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>API documentation can be enriched with metadata information like <a href=\"/wiki/Java_annotation\" title=\"Java annotation\">Java annotations</a>. This metadata can be used by the compiler, tools, and by the <i>run-time</i> environment to implement custom behaviors or custom handling.<sup id=\"cite_ref-57\" class=\"reference\"><a href=\"#cite_note-57\"><span class=\"cite-bracket\">[</span>57<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>It is possible to generate API documentation in a data-driven manner. By observing many programs that use a given API, it is possible to infer the typical usages, as well the required contracts and directives.<sup id=\"cite_ref-58\" class=\"reference\"><a href=\"#cite_note-58\"><span class=\"cite-bracket\">[</span>58<span class=\"cite-bracket\">]</span></a></sup> Then, templates can be used to generate natural language from the mined data.\n</p>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"Dispute_over_copyright_protection_for_APIs\">Dispute over copyright protection for APIs</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=12\" title=\"Edit section: Dispute over copyright protection for APIs\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1236090951\" /><div role=\"note\" class=\"hatnote navigation-not-searchable\">Main article: <a href=\"/wiki/Google_LLC_v._Oracle_America,_Inc.\" title=\"Google LLC v. Oracle America, Inc.\">Google LLC v. Oracle America, Inc.</a></div>\n<p>In 2010, Oracle Corporation sued Google for having distributed a new implementation of Java embedded in the Android operating system.<sup id=\"cite_ref-59\" class=\"reference\"><a href=\"#cite_note-59\"><span class=\"cite-bracket\">[</span>59<span class=\"cite-bracket\">]</span></a></sup> Google had not acquired any permission to reproduce the Java API, although permission had been given to the similar OpenJDK project. Judge <a href=\"/wiki/William_Alsup\" title=\"William Alsup\">William Alsup</a> ruled in the <i>Oracle v. Google</i> case that APIs cannot be <a href=\"/wiki/Copyrighted\" class=\"mw-redirect\" title=\"Copyrighted\">copyrighted</a> in the U.S. and that a victory for Oracle would have widely expanded copyright protection to a \"functional set of symbols\" and allowed the copyrighting of simple software commands:\n</p>\n<style data-mw-deduplicate=\"TemplateStyles:r1244412712\">.mw-parser-output .templatequote{overflow:hidden;margin:1em 0;padding:0 32px}.mw-parser-output .templatequotecite{line-height:1.5em;text-align:left;margin-top:0}@media(min-width:500px){.mw-parser-output .templatequotecite{padding-left:1.6em}}</style><blockquote class=\"templatequote\"><p>To accept Oracle's claim would be to allow anyone to copyright one version of code to carry out a system of commands and thereby bar all others from writing its different versions to carry out all or part of the same commands.<sup id=\"cite_ref-60\" class=\"reference\"><a href=\"#cite_note-60\"><span class=\"cite-bracket\">[</span>60<span class=\"cite-bracket\">]</span></a></sup><sup id=\"cite_ref-61\" class=\"reference\"><a href=\"#cite_note-61\"><span class=\"cite-bracket\">[</span>61<span class=\"cite-bracket\">]</span></a></sup></p></blockquote>\n<p>Alsup's ruling was overturned in 2014 on appeal to the <a href=\"/wiki/United_States_Court_of_Appeals_for_the_Federal_Circuit\" title=\"United States Court of Appeals for the Federal Circuit\">Court of Appeals for the Federal Circuit</a>, though the question of whether such use of APIs constitutes <a href=\"/wiki/Fair_use\" title=\"Fair use\">fair use</a> was left unresolved.<sup id=\"cite_ref-62\" class=\"reference\"><a href=\"#cite_note-62\"><span class=\"cite-bracket\">[</span>62<span class=\"cite-bracket\">]</span></a></sup><sup id=\"cite_ref-63\" class=\"reference\"><a href=\"#cite_note-63\"><span class=\"cite-bracket\">[</span>63<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>In 2016, following a two-week trial, a jury determined that Google's reimplementation of the Java API constituted <a href=\"/wiki/Fair_use\" title=\"Fair use\">fair use</a>, but Oracle vowed to appeal the decision.<sup id=\"cite_ref-64\" class=\"reference\"><a href=\"#cite_note-64\"><span class=\"cite-bracket\">[</span>64<span class=\"cite-bracket\">]</span></a></sup> Oracle won on its appeal, with the Court of Appeals for the Federal Circuit ruling that Google's use of the APIs did not qualify for fair use.<sup id=\"cite_ref-bbn_march2018_65-0\" class=\"reference\"><a href=\"#cite_note-bbn_march2018-65\"><span class=\"cite-bracket\">[</span>65<span class=\"cite-bracket\">]</span></a></sup> In 2019, Google appealed to the <a href=\"/wiki/Supreme_Court_of_the_United_States\" title=\"Supreme Court of the United States\">Supreme Court of the United States</a> over both the copyrightability and fair use rulings, and the Supreme Court granted review.<sup id=\"cite_ref-ars_Jan2019_66-0\" class=\"reference\"><a href=\"#cite_note-ars_Jan2019-66\"><span class=\"cite-bracket\">[</span>66<span class=\"cite-bracket\">]</span></a></sup> Due to the <a href=\"/wiki/COVID-19_pandemic\" title=\"COVID-19 pandemic\">COVID-19 pandemic</a>, the oral hearings in the case were delayed until October 2020.<sup id=\"cite_ref-67\" class=\"reference\"><a href=\"#cite_note-67\"><span class=\"cite-bracket\">[</span>67<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>The case was decided by the Supreme Court in Google's favor.<sup id=\"cite_ref-68\" class=\"reference\"><a href=\"#cite_note-68\"><span class=\"cite-bracket\">[</span>68<span class=\"cite-bracket\">]</span></a></sup>\n</p>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"API_security_and_emerging_threats\">API security and emerging threats</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=13\" title=\"Edit section: API security and emerging threats\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>In recent years, APIs have become integral to modern digital ecosystems, enabling seamless communication between applications.<sup id=\"cite_ref-69\" class=\"reference\"><a href=\"#cite_note-69\"><span class=\"cite-bracket\">[</span>69<span class=\"cite-bracket\">]</span></a></sup> However, as APIs gain prominence, they also become prime targets for cyberattacks.\n</p>\n<div class=\"mw-heading mw-heading3\"><h3 id=\"Evolving_API_threat_landscape\">Evolving API threat landscape</h3><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=14\" title=\"Edit section: Evolving API threat landscape\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>API security was traditionally focused on preventing embedded attacks, such as <a href=\"/wiki/SQL_injection\" title=\"SQL injection\">SQL injection</a> (SQLi), <a href=\"/wiki/Cross-site_scripting\" title=\"Cross-site scripting\">cross-site scripting</a> (XSS), and authentication bypass.<sup id=\"cite_ref-70\" class=\"reference\"><a href=\"#cite_note-70\"><span class=\"cite-bracket\">[</span>70<span class=\"cite-bracket\">]</span></a></sup> These attacks exploit technical <a href=\"/wiki/Vulnerability\" title=\"Vulnerability\">vulnerabilities</a> and are often mitigated using web application firewalls (WAFs) and API gateways.<sup id=\"cite_ref-71\" class=\"reference\"><a href=\"#cite_note-71\"><span class=\"cite-bracket\">[</span>71<span class=\"cite-bracket\">]</span></a></sup>\n</p><p>However, attackers have adapted their methods, leading to the rise of <i>business logic attacks</i> (BLAs).<sup id=\"cite_ref-72\" class=\"reference\"><a href=\"#cite_note-72\"><span class=\"cite-bracket\">[</span>72<span class=\"cite-bracket\">]</span></a></sup> Unlike embedded attacks, BLAs manipulate an API\u2019s legitimate functions to achieve unauthorized access or financial gain.\n</p>\n<div class=\"mw-heading mw-heading4\"><h4 id=\"Types_of_API_attacks\">Types of API attacks</h4><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=15\" title=\"Edit section: Types of API attacks\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<ul><li>Embedded attacks: Exploit known technical weaknesses, often detected by traditional security tools.</li>\n<li>Business logic attacks (BLAs): Exploit flaws in the logic of an API\u2019s workflow, often bypassing conventional security defenses.</li></ul>\n<div class=\"mw-heading mw-heading4\"><h4 id=\"Examples_of_business_logic_attacks\">Examples of business logic attacks</h4><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=16\" title=\"Edit section: Examples of business logic attacks\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<ul><li>Pricing manipulation: Altering API parameters to exploit pricing errors.</li>\n<li>Rate limit bypass: Scraping large volumes of data by evading API restrictions.</li>\n<li>Fraudulent transactions: Abusing authentication workflows to gain unauthorized privileges.</li></ul>\n<div class=\"mw-heading mw-heading3\"><h3 id=\"API_security_strategies\">API security strategies</h3><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=17\" title=\"Edit section: API security strategies\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<p>To mitigate API security risks, organizations implement advanced security measures, including:\n</p>\n<ul><li>Granular API visibility \u2013 Identifying and monitoring all APIs, including undocumented ones.</li>\n<li><a href=\"/wiki/Behavioral_analysis\" class=\"mw-redirect\" title=\"Behavioral analysis\">Behavioral analysis</a> \u2013 Using AI-driven monitoring to detect anomalies in API usage.</li>\n<li>Business logic mapping \u2013 Identifying vulnerabilities in API workflows.</li>\n<li>Real-Time threat mitigation \u2013 Blocking malicious API activity dynamically.</li>\n<li>Security integration \u2013 Cross-correlating API security with bot management and DDoS protection.</li></ul>\n<p>As APIs continue to evolve, security strategies must shift from static defenses to dynamic, behavior-based protections to counter increasingly sophisticated threats.\n</p>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"Examples\">Examples</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=18\" title=\"Edit section: Examples\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1236090951\" /><div role=\"note\" class=\"hatnote navigation-not-searchable\">Main category: <a href=\"/wiki/Category:Application_programming_interfaces\" title=\"Category:Application programming interfaces\">Application programming interfaces</a></div>\n<style data-mw-deduplicate=\"TemplateStyles:r1184024115\">.mw-parser-output .div-col{margin-top:0.3em;column-width:30em}.mw-parser-output .div-col-small{font-size:90%}.mw-parser-output .div-col-rules{column-rule:1px solid #aaa}.mw-parser-output .div-col dl,.mw-parser-output .div-col ol,.mw-parser-output .div-col ul{margin-top:0}.mw-parser-output .div-col li,.mw-parser-output .div-col dd{page-break-inside:avoid;break-inside:avoid-column}</style><div class=\"div-col\">\n<ul><li><a href=\"/wiki/Advanced_SCSI_programming_interface\" class=\"mw-redirect\" title=\"Advanced SCSI programming interface\">ASPI</a> for <a href=\"/wiki/SCSI\" title=\"SCSI\">SCSI</a> device interfacing</li>\n<li><a href=\"/wiki/Cocoa_(API)\" title=\"Cocoa (API)\">Cocoa</a> and <a href=\"/wiki/Carbon_(API)\" title=\"Carbon (API)\">Carbon</a> for the <a href=\"/wiki/Macintosh\" class=\"mw-redirect\" title=\"Macintosh\">Macintosh</a></li>\n<li><a href=\"/wiki/DirectX\" title=\"DirectX\">DirectX</a> for <a href=\"/wiki/Microsoft_Windows\" title=\"Microsoft Windows\">Microsoft Windows</a></li>\n<li><a href=\"/wiki/EHLLAPI\" title=\"EHLLAPI\">EHLLAPI</a></li>\n<li><a href=\"/wiki/List_of_Java_APIs\" title=\"List of Java APIs\">Java APIs</a></li>\n<li><a href=\"/wiki/Open_Database_Connectivity\" title=\"Open Database Connectivity\">ODBC</a> for <a href=\"/wiki/Microsoft_Windows\" title=\"Microsoft Windows\">Microsoft Windows</a></li>\n<li><a href=\"/wiki/OpenAL\" title=\"OpenAL\">OpenAL</a> cross-platform sound API</li>\n<li><a href=\"/wiki/OpenCL\" title=\"OpenCL\">OpenCL</a> cross-platform API for general-purpose computing for CPUs & GPUs</li>\n<li><a href=\"/wiki/OpenGL\" title=\"OpenGL\">OpenGL</a> cross-platform graphics API</li>\n<li><a href=\"/wiki/OpenMP\" title=\"OpenMP\">OpenMP</a> API that supports multi-platform shared memory multiprocessing programming in C, C++, and Fortran on many architectures, including Unix and Microsoft Windows platforms.</li>\n<li><a href=\"/wiki/Server_Application_Programming_Interface\" class=\"mw-redirect\" title=\"Server Application Programming Interface\">Server Application Programming Interface</a> (SAPI)</li>\n<li><a href=\"/wiki/Simple_DirectMedia_Layer\" title=\"Simple DirectMedia Layer\">Simple DirectMedia Layer</a> (SDL)</li></ul>\n</div>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"See_also\">See also</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=19\" title=\"Edit section: See also\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1184024115\" /><div class=\"div-col\" style=\"column-width: 22em;\">\n<ul><li><a href=\"/wiki/API_testing\" title=\"API testing\">API testing</a></li>\n<li><a href=\"/wiki/API_writer\" title=\"API writer\">API writer</a></li>\n<li><a href=\"/wiki/Augmented_web\" class=\"mw-redirect\" title=\"Augmented web\">Augmented web</a></li>\n<li><a href=\"/wiki/Calling_convention\" title=\"Calling convention\">Calling convention</a></li>\n<li><a href=\"/wiki/Common_Object_Request_Broker_Architecture\" title=\"Common Object Request Broker Architecture\">Common Object Request Broker Architecture</a> (CORBA)</li>\n<li><a href=\"/wiki/Comparison_of_application_virtual_machines\" class=\"mw-redirect\" title=\"Comparison of application virtual machines\">Comparison of application virtual machines</a></li>\n<li><a href=\"/wiki/Document_Object_Model\" title=\"Document Object Model\">Document Object Model</a> (DOM)</li>\n<li><a href=\"/wiki/Double-chance_function\" title=\"Double-chance function\">Double-chance function</a></li>\n<li><a href=\"/wiki/Foreign_function_interface\" title=\"Foreign function interface\">Foreign function interface</a></li>\n<li><a href=\"/wiki/Front_and_back_ends\" class=\"mw-redirect\" title=\"Front and back ends\">Front and back ends</a></li>\n<li><a href=\"/wiki/Interface_(computing)\" title=\"Interface (computing)\">Interface (computing)</a></li>\n<li><a href=\"/wiki/Interface_control_document\" title=\"Interface control document\">Interface control document</a></li>\n<li><a href=\"/wiki/List_of_3D_graphics_APIs\" class=\"mw-redirect\" title=\"List of 3D graphics APIs\">List of 3D graphics APIs</a></li>\n<li><a href=\"/wiki/Microservices\" title=\"Microservices\">Microservices</a></li>\n<li><a href=\"/wiki/Name_mangling\" title=\"Name mangling\">Name mangling</a></li>\n<li><a href=\"/wiki/Open_API\" title=\"Open API\">Open API</a></li>\n<li><a href=\"/wiki/Open_Service_Interface_Definitions\" class=\"mw-redirect\" title=\"Open Service Interface Definitions\">Open Service Interface Definitions</a></li>\n<li><a href=\"/wiki/Parsing\" title=\"Parsing\">Parsing</a></li>\n<li><a href=\"/wiki/Plug-in_(computing)\" title=\"Plug-in (computing)\">Plugin</a></li>\n<li><a href=\"/wiki/RAML_(software)\" title=\"RAML (software)\">RAML (software)</a></li>\n<li><a href=\"/wiki/Software_development_kit\" title=\"Software development kit\">Software development kit</a> (SDK)</li>\n<li><a href=\"/wiki/Web_API\" title=\"Web API\">Web API</a></li>\n<li><a href=\"/wiki/Web_content_vendor\" class=\"mw-redirect\" title=\"Web content vendor\">Web content vendor</a></li>\n<li><a href=\"/wiki/XPCOM\" title=\"XPCOM\">XPCOM</a></li></ul>\n</div>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"References\">References</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=20\" title=\"Edit section: References\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<style data-mw-deduplicate=\"TemplateStyles:r1239543626\">.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}</style><div class=\"reflist\">\n<div class=\"mw-references-wrap mw-references-columns\"><ol class=\"references\">\n<li id=\"cite_note-:0-1\"><span class=\"mw-cite-backlink\">^ <a href=\"#cite_ref-:0_1-0\"><sup><i><b>a</b></i></sup></a> <a href=\"#cite_ref-:0_1-1\"><sup><i><b>b</b></i></sup></a></span> <span class=\"reference-text\"><style data-mw-deduplicate=\"TemplateStyles:r1238218222\">.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:\"\\\"\"\"\\\"\"\"'\"\"'\"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url(\"//upload.wikimedia.org/wikipedia/commons/6/65/Lock-green.svg\")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url(\"//upload.wikimedia.org/wikipedia/commons/d/d6/Lock-gray-alt-2.svg\")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url(\"//upload.wikimedia.org/wikipedia/commons/a/aa/Lock-red-alt-2.svg\")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url(\"//upload.wikimedia.org/wikipedia/commons/4/4c/Wikisource-logo.svg\")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}</style><cite id=\"CITEREFReddy2011\" class=\"citation book cs1\">Reddy, Martin (2011). <a rel=\"nofollow\" class=\"external text\" href=\"https://books.google.com/books?id=IY29LylT85wC\"><i>API Design for C++</i></a>. Elsevier Science. p. 1. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/9780123850041\" title=\"Special:BookSources/9780123850041\"><bdi>9780123850041</bdi></a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=API+Design+for+C%2B%2B&rft.pages=1&rft.pub=Elsevier+Science&rft.date=2011&rft.isbn=9780123850041&rft.aulast=Reddy&rft.aufirst=Martin&rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3DIY29LylT85wC&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Lane2019-2\"><span class=\"mw-cite-backlink\">^ <a href=\"#cite_ref-Lane2019_2-0\"><sup><i><b>a</b></i></sup></a> <a href=\"#cite_ref-Lane2019_2-1\"><sup><i><b>b</b></i></sup></a></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFLane2019\" class=\"citation web cs1\">Lane, Kin (October 10, 2019). <a rel=\"nofollow\" class=\"external text\" href=\"https://blog.postman.com/intro-to-apis-history-of-apis/\">\"Intro to APIs: History of APIs\"</a>. <i>Postman</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">September 18,</span> 2020</span>. <q>When you hear the acronym \"API\" or its expanded version \"Application Programming Interface,\" it is almost always in reference to our modern approach, in that we use HTTP to provide access to machine readable data in a JSON or XML format, often simply referred to as \"web APIs.\" APIs have been around almost as long as computing, but modern web APIs began taking shape in the early 2000s.</q></cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Postman&rft.atitle=Intro+to+APIs%3A+History+of+APIs&rft.date=2019-10-10&rft.aulast=Lane&rft.aufirst=Kin&rft_id=https%3A%2F%2Fblog.postman.com%2Fintro-to-apis-history-of-apis%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Pedro2024-3\"><span class=\"mw-cite-backlink\">^ <a href=\"#cite_ref-Pedro2024_3-0\"><sup><i><b>a</b></i></sup></a> <a href=\"#cite_ref-Pedro2024_3-1\"><sup><i><b>b</b></i></sup></a></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFPedro2024\" class=\"citation book cs1\">Pedro, Bruno (2024). <a rel=\"nofollow\" class=\"external text\" href=\"https://books.google.com/books?id=JfbuEAAAQBAJ\"><i>Building an API Product: Design, Implement, Release, and Maintain API Products that Meet User Needs</i></a>. Packt Publishing. p. 4. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/9781837638536\" title=\"Special:BookSources/9781837638536\"><bdi>9781837638536</bdi></a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Building+an+API+Product%3A+Design%2C+Implement%2C+Release%2C+and+Maintain+API+Products+that+Meet+User+Needs&rft.pages=4&rft.pub=Packt+Publishing&rft.date=2024&rft.isbn=9781837638536&rft.aulast=Pedro&rft.aufirst=Bruno&rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3DJfbuEAAAQBAJ&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-4\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-4\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFBiehl2016\" class=\"citation book cs1\">Biehl, Matthias (2016). <i>RESTful API Design</i>. API-University Press. p. 10. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/9781514735169\" title=\"Special:BookSources/9781514735169\"><bdi>9781514735169</bdi></a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=RESTful+API+Design&rft.pages=10&rft.pub=API-University+Press&rft.date=2016&rft.isbn=9781514735169&rft.aulast=Biehl&rft.aufirst=Matthias&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Clarke4-5\"><span class=\"mw-cite-backlink\">^ <a href=\"#cite_ref-Clarke4_5-0\"><sup><i><b>a</b></i></sup></a> <a href=\"#cite_ref-Clarke4_5-1\"><sup><i><b>b</b></i></sup></a> <a href=\"#cite_ref-Clarke4_5-2\"><sup><i><b>c</b></i></sup></a></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFClarke2004\" class=\"citation web cs1\">Clarke, Steven (2004). <a rel=\"nofollow\" class=\"external text\" href=\"http://www.drdobbs.com/windows/measuring-api-usability/184405654\">\"Measuring API Usability\"</a>. <i>Dr. Dobb's</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">29 July</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Dr.+Dobb%27s&rft.atitle=Measuring+API+Usability&rft.date=2004&rft.aulast=Clarke&rft.aufirst=Steven&rft_id=http%3A%2F%2Fwww.drdobbs.com%2Fwindows%2Fmeasuring-api-usability%2F184405654&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-6\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-6\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFJinSahniShevat2018\" class=\"citation book cs1\">Jin, Brenda; Sahni, Saurabh; Shevat, Amir (2018). \"Preface\". <a rel=\"nofollow\" class=\"external text\" href=\"https://books.google.com/books?id=Dg1rDwAAQBAJ\"><i>Designing Web APIs: Building APIs That Developers Love</i></a>. O'Reilly Media. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/9781492026877\" title=\"Special:BookSources/9781492026877\"><bdi>9781492026877</bdi></a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=bookitem&rft.atitle=Preface&rft.btitle=Designing+Web+APIs%3A+Building+APIs+That+Developers+Love&rft.pub=O%27Reilly+Media&rft.date=2018&rft.isbn=9781492026877&rft.aulast=Jin&rft.aufirst=Brenda&rft.au=Sahni%2C+Saurabh&rft.au=Shevat%2C+Amir&rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3DDg1rDwAAQBAJ&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-7\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-7\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFGeewax2021\" class=\"citation book cs1\">Geewax, JJ (2021). <a rel=\"nofollow\" class=\"external text\" href=\"https://books.google.com/books?id=ato2EAAAQBAJ\"><i>API Design Patterns</i></a>. Manning. p. 6. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/9781638350330\" title=\"Special:BookSources/9781638350330\"><bdi>9781638350330</bdi></a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=API+Design+Patterns&rft.pages=6&rft.pub=Manning&rft.date=2021&rft.isbn=9781638350330&rft.aulast=Geewax&rft.aufirst=JJ&rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3Dato2EAAAQBAJ&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-8\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-8\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFJacobsonBrailWoods2011\" class=\"citation book cs1\">Jacobson, Daniel; Brail, Greg; Woods, Dan (2011). <a rel=\"nofollow\" class=\"external text\" href=\"https://books.google.com/books?id=om5tNwKW4xkC\"><i>APIs: A Strategy Guide</i></a>. O'Reilly Media. p. 4. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/9781449321642\" title=\"Special:BookSources/9781449321642\"><bdi>9781449321642</bdi></a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=APIs%3A+A+Strategy+Guide&rft.pages=4&rft.pub=O%27Reilly+Media&rft.date=2011&rft.isbn=9781449321642&rft.aulast=Jacobson&rft.aufirst=Daniel&rft.au=Brail%2C+Greg&rft.au=Woods%2C+Dan&rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3Dom5tNwKW4xkC&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-NBS1981-9\"><span class=\"mw-cite-backlink\">^ <a href=\"#cite_ref-NBS1981_9-0\"><sup><i><b>a</b></i></sup></a> <a href=\"#cite_ref-NBS1981_9-1\"><sup><i><b>b</b></i></sup></a></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation report cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://hdl.handle.net/2027/mdp.39015077587742?urlappend=%3Bseq=53\">Database architectures \u2013 a feasibility workshop</a> (Report). Washington, DC: U.S. Department of Commerce, National Bureau of Standards. April 1981. pp. <span class=\"nowrap\">45\u2013</span>47. <a href=\"/wiki/Hdl_(identifier)\" class=\"mw-redirect\" title=\"Hdl (identifier)\">hdl</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://hdl.handle.net/2027%2Fmdp.39015077587742?urlappend=%3Bseq=53\">2027/mdp.39015077587742</a>. <a href=\"/wiki/LCCN_(identifier)\" class=\"mw-redirect\" title=\"LCCN (identifier)\">LCCN</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://lccn.loc.gov/81600004\">81600004</a>. NBS special publication 500-76<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">September 18,</span> 2020</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=report&rft.btitle=Database+architectures+%E2%80%93+a+feasibility+workshop&rft.place=Washington%2C+DC&rft.pages=%3Cspan+class%3D%22nowrap%22%3E45-%3C%2Fspan%3E47&rft.pub=U.S.+Department+of+Commerce%2C+National+Bureau+of+Standards&rft.date=1981-04&rft_id=info%3Ahdl%2F2027%2Fmdp.39015077587742%3Furlappend%3D%253Bseq%3D53&rft_id=info%3Alccn%2F81600004&rft_id=https%3A%2F%2Fhdl.handle.net%2F2027%2Fmdp.39015077587742%3Furlappend%3D%253Bseq%3D53&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Bloch2018-10\"><span class=\"mw-cite-backlink\">^ <a href=\"#cite_ref-Bloch2018_10-0\"><sup><i><b>a</b></i></sup></a> <a href=\"#cite_ref-Bloch2018_10-1\"><sup><i><b>b</b></i></sup></a> <a href=\"#cite_ref-Bloch2018_10-2\"><sup><i><b>c</b></i></sup></a> <a href=\"#cite_ref-Bloch2018_10-3\"><sup><i><b>d</b></i></sup></a></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFBloch2018\" class=\"citation speech cs1\"><a href=\"/wiki/Joshua_Bloch\" title=\"Joshua Bloch\">Bloch, Joshua</a> (August 8, 2018). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.infoq.com/presentations/history-api/\"><i>A Brief, Opinionated History of the API</i></a> (Speech). QCon. San Francisco: InfoQ<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">September 18,</span> 2020</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=A+Brief%2C+Opinionated+History+of+the+API&rft.place=San+Francisco&rft.pub=InfoQ&rft.date=2018-08-08&rft.aulast=Bloch&rft.aufirst=Joshua&rft_id=https%3A%2F%2Fwww.infoq.com%2Fpresentations%2Fhistory-api%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-CottonGreatorex1968-11\"><span class=\"mw-cite-backlink\">^ <a href=\"#cite_ref-CottonGreatorex1968_11-0\"><sup><i><b>a</b></i></sup></a> <a href=\"#cite_ref-CottonGreatorex1968_11-1\"><sup><i><b>b</b></i></sup></a></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFCottonGreatorex1968\" class=\"citation conference cs1\">Cotton, Ira W.; Greatorex, Frank S. (December 1968). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.computer.org/csdl/pds/api/csdl/proceedings/download-article/12OmNyRPgFZ/pdf\">\"Data structures and techniques for remote computer graphics\"</a>. <i>AFIPS '68: Proceedings of the December 9\u201311, 1968, Fall Joint Computer Conference</i>. AFIPS 1968 Fall Joint Computer Conference. Vol. I. San Francisco, California: Association for Computing Machinery. pp. <span class=\"nowrap\">533\u2013</span>544. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1145%2F1476589.1476661\">10.1145/1476589.1476661</a>. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/978-1450378994\" title=\"Special:BookSources/978-1450378994\"><bdi>978-1450378994</bdi></a>. <a href=\"/wiki/OCLC_(identifier)\" class=\"mw-redirect\" title=\"OCLC (identifier)\">OCLC</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://search.worldcat.org/oclc/1175621908\">1175621908</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=conference&rft.atitle=Data+structures+and+techniques+for+remote+computer+graphics&rft.btitle=AFIPS+%2768%3A+Proceedings+of+the+December+9%E2%80%9311%2C+1968%2C+Fall+Joint+Computer+Conference&rft.place=San+Francisco%2C+California&rft.pages=%3Cspan+class%3D%22nowrap%22%3E533-%3C%2Fspan%3E544&rft.pub=Association+for+Computing+Machinery&rft.date=1968-12&rft_id=info%3Aoclcnum%2F1175621908&rft_id=info%3Adoi%2F10.1145%2F1476589.1476661&rft.isbn=978-1450378994&rft.aulast=Cotton&rft.aufirst=Ira+W.&rft.au=Greatorex%2C+Frank+S.&rft_id=https%3A%2F%2Fwww.computer.org%2Fcsdl%2Fpds%2Fapi%2Fcsdl%2Fproceedings%2Fdownload-article%2F12OmNyRPgFZ%2Fpdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-12\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-12\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFReference-OED-application_program_interface\" class=\"citation encyclopaedia cs1\"><span class=\"id-lock-subscription\" title=\"Paid subscription required\"><a rel=\"nofollow\" class=\"external text\" href=\"https://www.oed.com/search/dictionary/?q=application+program+interface\">\"application program interface\"</a></span>. <i><a href=\"/wiki/Oxford_English_Dictionary\" title=\"Oxford English Dictionary\">Oxford English Dictionary</a></i> (Online ed.). <a href=\"/wiki/Oxford_University_Press\" title=\"Oxford University Press\">Oxford University Press</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=bookitem&rft.atitle=application+program+interface&rft.btitle=Oxford+English+Dictionary&rft.edition=Online&rft.pub=Oxford+University+Press&rft_id=https%3A%2F%2Fwww.oed.com%2Fsearch%2Fdictionary%2F%3Fq%3Dapplication%2Bprogram%2Binterface&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span> <span style=\"font-size:0.95em; font-size:95%; color: var( --color-subtle, #555 )\">(Subscription or <a rel=\"nofollow\" class=\"external text\" href=\"https://www.oed.com/public/login/loggingin#withyourlibrary\">participating institution membership</a> required.)</span></span>\n</li>\n<li id=\"cite_note-13\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-13\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFDate2019\" class=\"citation book cs1\"><a href=\"/wiki/Christopher_J._Date\" title=\"Christopher J. Date\">Date, C. J.</a> (2019). <a rel=\"nofollow\" class=\"external text\" href=\"https://books.google.com/books?id=2Sy4DwAAQBAJ&pg=PA135\"><i>E. F. Codd and Relational Theory: A Detailed Review and Analysis of Codd's Major Database Writings</i></a>. Lulu.com. p. 135. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/978-1684705276\" title=\"Special:BookSources/978-1684705276\"><bdi>978-1684705276</bdi></a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=E.+F.+Codd+and+Relational+Theory%3A+A+Detailed+Review+and+Analysis+of+Codd%27s+Major+Database+Writings&rft.pages=135&rft.pub=Lulu.com&rft.date=2019&rft.isbn=978-1684705276&rft.aulast=Date&rft.aufirst=C.+J.&rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3D2Sy4DwAAQBAJ%26pg%3DPA135&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-14\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-14\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFDateCodd1975\" class=\"citation conference cs1\">Date, C. J.; Codd, E. F. (January 1975). <a rel=\"nofollow\" class=\"external text\" href=\"https://dl.acm.org/doi/pdf/10.1145/800297.811532\">\"The relational and network approaches: Comparison of the application programming interfaces\"</a>. In Randall Rustin (ed.). <i>Proceedings of 1974 ACM-SIGMOD Workshop on Data Description, Access and Control</i>. SIGMOD Workshop 1974. Vol. 2. Ann Arbor, Michigan: Association for Computing Machinery. pp. <span class=\"nowrap\">83\u2013</span>113. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1145%2F800297.811532\">10.1145/800297.811532</a>. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/978-1450374187\" title=\"Special:BookSources/978-1450374187\"><bdi>978-1450374187</bdi></a>. <a href=\"/wiki/OCLC_(identifier)\" class=\"mw-redirect\" title=\"OCLC (identifier)\">OCLC</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://search.worldcat.org/oclc/1175623233\">1175623233</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=conference&rft.atitle=The+relational+and+network+approaches%3A+Comparison+of+the+application+programming+interfaces&rft.btitle=Proceedings+of+1974+ACM-SIGMOD+Workshop+on+Data+Description%2C+Access+and+Control&rft.place=Ann+Arbor%2C+Michigan&rft.pages=%3Cspan+class%3D%22nowrap%22%3E83-%3C%2Fspan%3E113&rft.pub=Association+for+Computing+Machinery&rft.date=1975-01&rft_id=info%3Aoclcnum%2F1175623233&rft_id=info%3Adoi%2F10.1145%2F800297.811532&rft.isbn=978-1450374187&rft.aulast=Date&rft.aufirst=C.+J.&rft.au=Codd%2C+E.+F.&rft_id=https%3A%2F%2Fdl.acm.org%2Fdoi%2Fpdf%2F10.1145%2F800297.811532&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-15\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-15\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFCarl1990\" class=\"citation book cs1\"><a href=\"/wiki/Carl_Malamud\" title=\"Carl Malamud\">Carl, Malamud</a> (1990). <a rel=\"nofollow\" class=\"external text\" href=\"https://babel.hathitrust.org/cgi/pt?id=mdp.39015018454903&seq=314\"><i>Analyzing Novell Networks</i></a>. Van Nostrand Reinhold. p. 294. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/978-0442003647\" title=\"Special:BookSources/978-0442003647\"><bdi>978-0442003647</bdi></a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Analyzing+Novell+Networks&rft.pages=294&rft.pub=Van+Nostrand+Reinhold&rft.date=1990&rft.isbn=978-0442003647&rft.aulast=Carl&rft.aufirst=Malamud&rft_id=https%3A%2F%2Fbabel.hathitrust.org%2Fcgi%2Fpt%3Fid%3Dmdp.39015018454903%26seq%3D314&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-JinSahniShevat2018-16\"><span class=\"mw-cite-backlink\">^ <a href=\"#cite_ref-JinSahniShevat2018_16-0\"><sup><i><b>a</b></i></sup></a> <a href=\"#cite_ref-JinSahniShevat2018_16-1\"><sup><i><b>b</b></i></sup></a></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFJinSahniShevat2018\" class=\"citation book cs1\">Jin, Brenda; Sahni, Saurabh; Shevat, Amir (2018). <a rel=\"nofollow\" class=\"external text\" href=\"https://books.google.com/books?id=Dg1rDwAAQBAJ\"><i>Designing Web APIs</i></a>. O'Reilly Media. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/9781492026877\" title=\"Special:BookSources/9781492026877\"><bdi>9781492026877</bdi></a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Designing+Web+APIs&rft.pub=O%27Reilly+Media&rft.date=2018&rft.isbn=9781492026877&rft.aulast=Jin&rft.aufirst=Brenda&rft.au=Sahni%2C+Saurabh&rft.au=Shevat%2C+Amir&rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3DDg1rDwAAQBAJ&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-17\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-17\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFFielding2000\" class=\"citation thesis cs1\">Fielding, Roy (2000). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm\"><i>Architectural Styles and the Design of Network-based Software Architectures</i></a> (PhD)<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">September 18,</span> 2020</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adissertation&rft.title=Architectural+Styles+and+the+Design+of+Network-based+Software+Architectures&rft.date=2000&rft.aulast=Fielding&rft.aufirst=Roy&rft_id=https%3A%2F%2Fwww.ics.uci.edu%2F~fielding%2Fpubs%2Fdissertation%2Ftop.htm&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-18\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-18\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFDotsika2010\" class=\"citation journal cs1\">Dotsika, Fefie (August 2010). \"Semantic APIs: Scaling up towards the Semantic Web\". <i>International Journal of Information Management</i>. <b>30</b> (4): <span class=\"nowrap\">335\u2013</span>342. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1016%2Fj.ijinfomgt.2009.12.003\">10.1016/j.ijinfomgt.2009.12.003</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=International+Journal+of+Information+Management&rft.atitle=Semantic+APIs%3A+Scaling+up+towards+the+Semantic+Web&rft.volume=30&rft.issue=4&rft.pages=%3Cspan+class%3D%22nowrap%22%3E335-%3C%2Fspan%3E342&rft.date=2010-08&rft_id=info%3Adoi%2F10.1016%2Fj.ijinfomgt.2009.12.003&rft.aulast=Dotsika&rft.aufirst=Fefie&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-OderskySpoonVenners8-19\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-OderskySpoonVenners8_19-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFOderskySpoonVenners2008\" class=\"citation web cs1\">Odersky, Martin; Spoon, Lex; Venners, Bill (10 December 2008). <a rel=\"nofollow\" class=\"external text\" href=\"http://www.artima.com/pins1ed/combining-scala-and-java.html\">\"Combining Scala and Java\"</a>. <i>www.artima.com</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">29 July</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=www.artima.com&rft.atitle=Combining+Scala+and+Java&rft.date=2008-12-10&rft.aulast=Odersky&rft.aufirst=Martin&rft.au=Spoon%2C+Lex&rft.au=Venners%2C+Bill&rft_id=http%3A%2F%2Fwww.artima.com%2Fpins1ed%2Fcombining-scala-and-java.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-20\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-20\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFde_FigueiredoIerusalimschyFilho1994\" class=\"citation conference cs1\">de Figueiredo, Luiz Henrique; <a href=\"/wiki/Roberto_Ierusalimschy\" title=\"Roberto Ierusalimschy\">Ierusalimschy, Roberto</a>; Filho, Waldemar Celes (1994). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.lua.org/semish94.html\">\"The design and implementation of a language for extending applications\"</a>. <i>Proceedings of XXI Brazilian Seminar on Software and Hardware</i>. pp. <span class=\"nowrap\">273\u2013</span>284. <a href=\"/wiki/CiteSeerX_(identifier)\" class=\"mw-redirect\" title=\"CiteSeerX (identifier)\">CiteSeerX</a> <span class=\"id-lock-free\" title=\"Freely accessible\"><a rel=\"nofollow\" class=\"external text\" href=\"https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.47.5194\">10.1.1.47.5194</a></span>. <a href=\"/wiki/S2CID_(identifier)\" class=\"mw-redirect\" title=\"S2CID (identifier)\">S2CID</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://api.semanticscholar.org/CorpusID:59833827\">59833827</a><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">29 July</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=conference&rft.atitle=The+design+and+implementation+of+a+language+for+extending+applications&rft.btitle=Proceedings+of+XXI+Brazilian+Seminar+on+Software+and+Hardware&rft.pages=%3Cspan+class%3D%22nowrap%22%3E273-%3C%2Fspan%3E284&rft.date=1994&rft_id=https%3A%2F%2Fciteseerx.ist.psu.edu%2Fviewdoc%2Fsummary%3Fdoi%3D10.1.1.47.5194%23id-name%3DCiteSeerX&rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A59833827%23id-name%3DS2CID&rft.aulast=de+Figueiredo&rft.aufirst=Luiz+Henrique&rft.au=Ierusalimschy%2C+Roberto&rft.au=Filho%2C+Waldemar+Celes&rft_id=https%3A%2F%2Fwww.lua.org%2Fsemish94.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Sintes16-21\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-Sintes16_21-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFSintes2001\" class=\"citation web cs1\">Sintes, Tony (13 July 2001). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.infoworld.com/article/2077392/just-what-is-the-java-api-anyway.html\">\"Just what is the Java API anyway?\"</a>. <i><a href=\"/wiki/JavaWorld\" class=\"mw-redirect\" title=\"JavaWorld\">JavaWorld</a></i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2020-07-18</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=JavaWorld&rft.atitle=Just+what+is+the+Java+API+anyway%3F&rft.date=2001-07-13&rft.aulast=Sintes&rft.aufirst=Tony&rft_id=https%3A%2F%2Fwww.infoworld.com%2Farticle%2F2077392%2Fjust-what-is-the-java-api-anyway.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-22\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-22\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFWintersTom_ManshreckHyrum_Wright2020\" class=\"citation book cs1\">Winters, Titus; Tom Manshreck; Hyrum Wright, eds. (2020). <i>Software engineering at Google: lessons learned from programming over time</i>. Sebastopol, CA: O'Reilly Media. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/9781492082798\" title=\"Special:BookSources/9781492082798\"><bdi>9781492082798</bdi></a>. <a href=\"/wiki/OCLC_(identifier)\" class=\"mw-redirect\" title=\"OCLC (identifier)\">OCLC</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://search.worldcat.org/oclc/1144086840\">1144086840</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Software+engineering+at+Google%3A+lessons+learned+from+programming+over+time&rft.place=Sebastopol%2C+CA&rft.pub=O%27Reilly+Media&rft.date=2020&rft_id=info%3Aoclcnum%2F1144086840&rft.isbn=9781492082798&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-23\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-23\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFMastrangeloPonzanelliMocciLanza2015\" class=\"citation conference cs1\">Mastrangelo, Luis; Ponzanelli, Luca; Mocci, Andrea; Lanza, Michele; Hauswirth, Matthias; Nystrom, Nathaniel (2015-10-23). \"Use at your own risk: the Java unsafe API in the wild\". <i>Proceedings of the 2015 ACM SIGPLAN International Conference on Object-Oriented Programming, Systems, Languages, and Applications</i>. New York, New York, U.S.: Association for Computing Machinery. pp. <span class=\"nowrap\">695\u2013</span>710. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1145%2F2814270.2814313\">10.1145/2814270.2814313</a>. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/978-1-4503-3689-5\" title=\"Special:BookSources/978-1-4503-3689-5\"><bdi>978-1-4503-3689-5</bdi></a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=conference&rft.atitle=Use+at+your+own+risk%3A+the+Java+unsafe+API+in+the+wild&rft.btitle=Proceedings+of+the+2015+ACM+SIGPLAN+International+Conference+on+Object-Oriented+Programming%2C+Systems%2C+Languages%2C+and+Applications&rft.place=New+York%2C+New+York%2C+U.S.&rft.pages=%3Cspan+class%3D%22nowrap%22%3E695-%3C%2Fspan%3E710&rft.pub=Association+for+Computing+Machinery&rft.date=2015-10-23&rft_id=info%3Adoi%2F10.1145%2F2814270.2814313&rft.isbn=978-1-4503-3689-5&rft.aulast=Mastrangelo&rft.aufirst=Luis&rft.au=Ponzanelli%2C+Luca&rft.au=Mocci%2C+Andrea&rft.au=Lanza%2C+Michele&rft.au=Hauswirth%2C+Matthias&rft.au=Nystrom%2C+Nathaniel&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Emery-24\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-Emery_24-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFEmery\" class=\"citation web cs1\">Emery, David. <a rel=\"nofollow\" class=\"external text\" href=\"https://web.archive.org/web/20150116081559/http://www.acm.org/tsc/apis.html\">\"Standards, APIs, Interfaces and Bindings\"</a>. Acm.org. Archived from <a rel=\"nofollow\" class=\"external text\" href=\"http://www.acm.org/tsc/apis.html\">the original</a> on 2015-01-16<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2016-08-08</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Standards%2C+APIs%2C+Interfaces+and+Bindings&rft.pub=Acm.org&rft.aulast=Emery&rft.aufirst=David&rft_id=http%3A%2F%2Fwww.acm.org%2Ftsc%2Fapis.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-25\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-25\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"http://www.f2py.org/\">\"F2PY.org\"</a>. F2PY.org<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2011-12-18</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=F2PY.org&rft.pub=F2PY.org&rft_id=http%3A%2F%2Fwww.f2py.org%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-26\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-26\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFFowler\" class=\"citation web cs1\">Fowler, Martin. <a rel=\"nofollow\" class=\"external text\" href=\"http://martinfowler.com/bliki/InversionOfControl.html\">\"Inversion Of Control\"</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Inversion+Of+Control&rft.aulast=Fowler&rft.aufirst=Martin&rft_id=http%3A%2F%2Fmartinfowler.com%2Fbliki%2FInversionOfControl.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-27\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-27\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFFayad\" class=\"citation web cs1\">Fayad, Mohamed. <a rel=\"nofollow\" class=\"external text\" href=\"http://www.dre.vanderbilt.edu/~schmidt/CACM-frameworks.html\">\"Object-Oriented Application Frameworks\"</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Object-Oriented+Application+Frameworks&rft.aulast=Fayad&rft.aufirst=Mohamed&rft_id=http%3A%2F%2Fwww.dre.vanderbilt.edu%2F~schmidt%2FCACM-frameworks.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Oreilly91-28\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-Oreilly91_28-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFLewine1991\" class=\"citation book cs1\">Lewine, Donald A. (1991). <a rel=\"nofollow\" class=\"external text\" href=\"http://shop.oreilly.com/product/9780937175736.do\"><i>POSIX Programmer's Guide</i></a>. O'Reilly & Associates, Inc. p. 1. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/9780937175736\" title=\"Special:BookSources/9780937175736\"><bdi>9780937175736</bdi></a><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2 August</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=POSIX+Programmer%27s+Guide&rft.pages=1&rft.pub=O%27Reilly+%26+Associates%2C+Inc.&rft.date=1991&rft.isbn=9780937175736&rft.aulast=Lewine&rft.aufirst=Donald+A.&rft_id=http%3A%2F%2Fshop.oreilly.com%2Fproduct%2F9780937175736.do&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-WestDedrick16-29\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-WestDedrick16_29-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFWestDedrick2001\" class=\"citation journal cs1\">West, Joel; Dedrick, Jason (2001). <a rel=\"nofollow\" class=\"external text\" href=\"http://www.joelwest.org/Papers/WestDedrick2001b.pdf\">\"Open source standardization: the rise of Linux in the network era\"</a> <span class=\"cs1-format\">(PDF)</span>. <i>Knowledge, Technology & Policy</i>. <b>14</b> (2): <span class=\"nowrap\">88\u2013</span>112. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1007%2FPL00022278\">10.1007/PL00022278</a><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2 August</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Knowledge%2C+Technology+%26+Policy&rft.atitle=Open+source+standardization%3A+the+rise+of+Linux+in+the+network+era&rft.volume=14&rft.issue=2&rft.pages=%3Cspan+class%3D%22nowrap%22%3E88-%3C%2Fspan%3E112&rft.date=2001&rft_id=info%3Adoi%2F10.1007%2FPL00022278&rft.aulast=West&rft.aufirst=Joel&rft.au=Dedrick%2C+Jason&rft_id=http%3A%2F%2Fwww.joelwest.org%2FPapers%2FWestDedrick2001b.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-30\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-30\">^</a></b></span> <span class=\"reference-text\">\n<link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFMicrosoft2001\" class=\"citation web cs1\">Microsoft (October 2001). <a rel=\"nofollow\" class=\"external text\" href=\"https://web.archive.org/web/20090926235439/http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/appcompat.mspx\">\"Support for Windows XP\"</a>. Microsoft. p. 4. Archived from <a rel=\"nofollow\" class=\"external text\" href=\"http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/appcompat.mspx\">the original</a> on 2009-09-26.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Support+for+Windows+XP&rft.pages=4&rft.pub=Microsoft&rft.date=2001-10&rft.au=Microsoft&rft_id=http%3A%2F%2Fwww.microsoft.com%2Fwindowsxp%2Fusing%2Fhelpandsupport%2Flearnmore%2Fappcompat.mspx&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-31\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-31\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://web.archive.org/web/20150402094250/http://www.linuxfoundation.org/collaborate/workgroups/lsb/lsb-introduction\">\"LSB Introduction\"</a>. Linux Foundation. 21 June 2012. Archived from <a rel=\"nofollow\" class=\"external text\" href=\"http://www.linuxfoundation.org/collaborate/workgroups/lsb/lsb-introduction\">the original</a> on 2015-04-02<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2015-03-27</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=LSB+Introduction&rft.pub=Linux+Foundation&rft.date=2012-06-21&rft_id=http%3A%2F%2Fwww.linuxfoundation.org%2Fcollaborate%2Fworkgroups%2Flsb%2Flsb-introduction&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-32\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-32\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFStoughton2005\" class=\"citation web cs1\">Stoughton, Nick (April 2005). <a rel=\"nofollow\" class=\"external text\" href=\"https://db.usenix.org/publications/login/2005-04/openpdfs/standards2004.pdf\">\"Update on Standards\"</a> <span class=\"cs1-format\">(PDF)</span>. <a href=\"/wiki/USENIX\" title=\"USENIX\">USENIX</a><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2009-06-04</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Update+on+Standards&rft.pub=USENIX&rft.date=2005-04&rft.aulast=Stoughton&rft.aufirst=Nick&rft_id=https%3A%2F%2Fdb.usenix.org%2Fpublications%2Flogin%2F2005-04%2Fopenpdfs%2Fstandards2004.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Bierhoff9-33\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-Bierhoff9_33-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFBierhoff2009\" class=\"citation journal cs1\">Bierhoff, Kevin (23 April 2009). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.cs.cmu.edu/~kbierhof/thesis/bierhoff-thesis.pdf\">\"API Protocol Compliance in Object-Oriented Software\"</a> <span class=\"cs1-format\">(PDF)</span>. <i>CMU Institute for Software Research</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">29 July</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=CMU+Institute+for+Software+Research&rft.atitle=API+Protocol+Compliance+in+Object-Oriented+Software&rft.date=2009-04-23&rft.aulast=Bierhoff&rft.aufirst=Kevin&rft_id=https%3A%2F%2Fwww.cs.cmu.edu%2F~kbierhof%2Fthesis%2Fbierhoff-thesis.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Wilson16-34\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-Wilson16_34-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFWilson2000\" class=\"citation web cs1\">Wilson, M. Jeff (10 November 2000). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.infoworld.com/article/2076234/get-smart-with-proxies-and-rmi.html\">\"Get smart with proxies and RMI\"</a>. <i><a href=\"/wiki/JavaWorld\" class=\"mw-redirect\" title=\"JavaWorld\">JavaWorld</a></i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2020-07-18</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=JavaWorld&rft.atitle=Get+smart+with+proxies+and+RMI&rft.date=2000-11-10&rft.aulast=Wilson&rft.aufirst=M.+Jeff&rft_id=https%3A%2F%2Fwww.infoworld.com%2Farticle%2F2076234%2Fget-smart-with-proxies-and-rmi.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-AdvancedCorba-35\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-AdvancedCorba_35-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFHenningVinoski1999\" class=\"citation book cs1\">Henning, Michi; Vinoski, Steve (1999). <span class=\"id-lock-registration\" title=\"Free registration required\"><a rel=\"nofollow\" class=\"external text\" href=\"https://archive.org/details/advancedcorbapro00henn\"><i>Advanced CORBA Programming with C++</i></a></span>. <a href=\"/wiki/Addison-Wesley\" title=\"Addison-Wesley\">Addison-Wesley</a>. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/978-0201379273\" title=\"Special:BookSources/978-0201379273\"><bdi>978-0201379273</bdi></a><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">16 June</span> 2015</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Advanced+CORBA+Programming+with+C%2B%2B&rft.pub=Addison-Wesley&rft.date=1999&rft.isbn=978-0201379273&rft.aulast=Henning&rft.aufirst=Michi&rft.au=Vinoski%2C+Steve&rft_id=https%3A%2F%2Farchive.org%2Fdetails%2Fadvancedcorbapro00henn&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-36\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-36\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://www.hcltech.com/sites/default/files/documents/resources/whitepaper/files/apis_for_dsi.pdf\">\"API-fication\"</a> <span class=\"cs1-format\">(PDF)</span>. <i>www.hcltech.com</i>. August 2014.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=www.hcltech.com&rft.atitle=API-fication&rft.date=2014-08&rft_id=https%3A%2F%2Fwww.hcltech.com%2Fsites%2Fdefault%2Ffiles%2Fdocuments%2Fresources%2Fwhitepaper%2Ffiles%2Fapis_for_dsi.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-37\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-37\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFBenslimaneSchahram_DustdarAmit_Sheth2008\" class=\"citation journal cs1\">Benslimane, Djamal; Schahram Dustdar; Amit Sheth (2008). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.computer.org/csdl/magazine/ic/2008/05/mic2008050013/13rRUytWFdu\">\"Services Mashups: The New Generation of Web Applications\"</a>. <i>IEEE Internet Computing</i>. <b>12</b> (5). IEEE: <span class=\"nowrap\">13\u2013</span>15. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1109%2FMIC.2008.110\">10.1109/MIC.2008.110</a><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2019-10-01</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=IEEE+Internet+Computing&rft.atitle=Services+Mashups%3A+The+New+Generation+of+Web+Applications&rft.volume=12&rft.issue=5&rft.pages=%3Cspan+class%3D%22nowrap%22%3E13-%3C%2Fspan%3E15&rft.date=2008&rft_id=info%3Adoi%2F10.1109%2FMIC.2008.110&rft.aulast=Benslimane&rft.aufirst=Djamal&rft.au=Schahram+Dustdar&rft.au=Amit+Sheth&rft_id=https%3A%2F%2Fwww.computer.org%2Fcsdl%2Fmagazine%2Fic%2F2008%2F05%2Fmic2008050013%2F13rRUytWFdu&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-38\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-38\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFNiccolai2008\" class=\"citation cs2\">Niccolai, James (2008-04-23), <a rel=\"nofollow\" class=\"external text\" href=\"https://web.archive.org/web/20171010045104/https://www.pcworld.com/article/145039/article.html\">\"So What Is an Enterprise Mashup, Anyway?\"</a>, <i><a href=\"/wiki/PC_World_(magazine)\" class=\"mw-redirect\" title=\"PC World (magazine)\">PC World</a></i>, archived from <a rel=\"nofollow\" class=\"external text\" href=\"https://www.pcworld.com/article/145039/so_what_is_an_enterprise_mashup_anyway.html\">the original</a> on 2017-10-10<span class=\"reference-accessdate\">, retrieved <span class=\"nowrap\">2017-09-17</span></span></cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=PC+World&rft.atitle=So+What+Is+an+Enterprise+Mashup%2C+Anyway%3F&rft.date=2008-04-23&rft.aulast=Niccolai&rft.aufirst=James&rft_id=https%3A%2F%2Fwww.pcworld.com%2Farticle%2F145039%2Fso_what_is_an_enterprise_mashup_anyway.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Parr16-39\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-Parr16_39-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFParr2009\" class=\"citation web cs1\">Parr, Ben (21 May 2009). <a rel=\"nofollow\" class=\"external text\" href=\"http://mashable.com/2009/05/21/social-media-api/\">\"The Evolution of the Social Media API\"</a>. <i>Mashable</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">26 July</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Mashable&rft.atitle=The+Evolution+of+the+Social+Media+API&rft.date=2009-05-21&rft.aulast=Parr&rft.aufirst=Ben&rft_id=http%3A%2F%2Fmashable.com%2F2009%2F05%2F21%2Fsocial-media-api%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-40\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-40\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://developer.twitter.com/en/docs/trends/trends-for-location/api-reference/get-trends-place\">\"GET trends/place\"</a>. <i>developer.twitter.com</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2020-04-30</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=developer.twitter.com&rft.atitle=GET+trends%2Fplace&rft_id=https%3A%2F%2Fdeveloper.twitter.com%2Fen%2Fdocs%2Ftrends%2Ftrends-for-location%2Fapi-reference%2Fget-trends-place&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Parnas72-41\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-Parnas72_41-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFParnas1972\" class=\"citation journal cs1\">Parnas, D.L. (1972). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.win.tue.nl/~wstomv/edu/2ip30/references/criteria_for_modularization.pdf\">\"On the Criteria To Be Used in Decomposing Systems into Modules\"</a> <span class=\"cs1-format\">(PDF)</span>. <i>Communications of the ACM</i>. <b>15</b> (12): <span class=\"nowrap\">1053\u2013</span>1058. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1145%2F361598.361623\">10.1145/361598.361623</a>. <a href=\"/wiki/S2CID_(identifier)\" class=\"mw-redirect\" title=\"S2CID (identifier)\">S2CID</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://api.semanticscholar.org/CorpusID:53856438\">53856438</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Communications+of+the+ACM&rft.atitle=On+the+Criteria+To+Be+Used+in+Decomposing+Systems+into+Modules&rft.volume=15&rft.issue=12&rft.pages=%3Cspan+class%3D%22nowrap%22%3E1053-%3C%2Fspan%3E1058&rft.date=1972&rft_id=info%3Adoi%2F10.1145%2F361598.361623&rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A53856438%23id-name%3DS2CID&rft.aulast=Parnas&rft.aufirst=D.L.&rft_id=https%3A%2F%2Fwww.win.tue.nl%2F~wstomv%2Fedu%2F2ip30%2Freferences%2Fcriteria_for_modularization.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-GarlanShaw94-42\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-GarlanShaw94_42-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFGarlanShaw1994\" class=\"citation journal cs1\">Garlan, David; Shaw, Mary (January 1994). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.cs.cmu.edu/afs/cs/project/able/ftp/intro_softarch/intro_softarch.pdf\">\"An Introduction to Software Architecture\"</a> <span class=\"cs1-format\">(PDF)</span>. <i>Advances in Software Engineering and Knowledge Engineering</i>. <b>1</b><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">8 August</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Advances+in+Software+Engineering+and+Knowledge+Engineering&rft.atitle=An+Introduction+to+Software+Architecture&rft.volume=1&rft.date=1994-01&rft.aulast=Garlan&rft.aufirst=David&rft.au=Shaw%2C+Mary&rft_id=https%3A%2F%2Fwww.cs.cmu.edu%2Fafs%2Fcs%2Fproject%2Fable%2Fftp%2Fintro_softarch%2Fintro_softarch.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-43\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-43\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFde_Ternay2015\" class=\"citation web cs1\">de Ternay, Guerric (Oct 10, 2015). <a rel=\"nofollow\" class=\"external text\" href=\"https://web.archive.org/web/20160917121456/https://boostcompanies.com/business-ecosystem/\">\"Business Ecosystem: Creating an Economic Moat\"</a>. <i>BoostCompanies</i>. Archived from <a rel=\"nofollow\" class=\"external text\" href=\"http://boostcompanies.com/business-ecosystem\">the original</a> on 2016-09-17<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2016-02-01</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=BoostCompanies&rft.atitle=Business+Ecosystem%3A+Creating+an+Economic+Moat&rft.date=2015-10-10&rft.aulast=de+Ternay&rft.aufirst=Guerric&rft_id=http%3A%2F%2Fboostcompanies.com%2Fbusiness-ecosystem&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Boyd16-44\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-Boyd16_44-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFBoyd2014\" class=\"citation web cs1\">Boyd, Mark (2014-02-21). <a rel=\"nofollow\" class=\"external text\" href=\"http://www.programmableweb.com/news/private-partner-or-public-which-api-strategy-best-business/2014/02/21\">\"Private, Partner or Public: Which API Strategy Is Best for Business?\"</a>. <i>ProgrammableWeb</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2 August</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=ProgrammableWeb&rft.atitle=Private%2C+Partner+or+Public%3A+Which+API+Strategy+Is+Best+for+Business%3F&rft.date=2014-02-21&rft.aulast=Boyd&rft.aufirst=Mark&rft_id=http%3A%2F%2Fwww.programmableweb.com%2Fnews%2Fprivate-partner-or-public-which-api-strategy-best-business%2F2014%2F02%2F21&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-45\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-45\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFWeissbrot2016\" class=\"citation web cs1\">Weissbrot, Alison (7 July 2016). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.adexchanger.com/mobile/car-service-apis-everywhere-whats-partner-apps/\">\"Car Service APIs Are Everywhere, But What's In It For Partner Apps?\"</a>. <i>AdExchanger</i>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=AdExchanger&rft.atitle=Car+Service+APIs+Are+Everywhere%2C+But+What%27s+In+It+For+Partner+Apps%3F&rft.date=2016-07-07&rft.aulast=Weissbrot&rft.aufirst=Alison&rft_id=https%3A%2F%2Fwww.adexchanger.com%2Fmobile%2Fcar-service-apis-everywhere-whats-partner-apps%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-Cloudflare-46\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-Cloudflare_46-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://api.cloudflare.com/\">\"Cloudflare API v4 Documentation\"</a>. <i>cloudflare</i>. 25 February 2020<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">27 February</span> 2020</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=cloudflare&rft.atitle=Cloudflare+API+v4+Documentation&rft.date=2020-02-25&rft_id=https%3A%2F%2Fapi.cloudflare.com%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-SmashMagazine-47\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-SmashMagazine_47-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFLiew2018\" class=\"citation web cs1\">Liew, Zell (17 January 2018). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.smashingmagazine.com/2018/01/understanding-using-rest-api/\">\"Car Service APIs Are Everywhere, But What's In It For Partner Apps\"</a>. <i>Smashing Magazine</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">27 February</span> 2020</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Smashing+Magazine&rft.atitle=Car+Service+APIs+Are+Everywhere%2C+But+What%27s+In+It+For+Partner+Apps&rft.date=2018-01-17&rft.aulast=Liew&rft.aufirst=Zell&rft_id=https%3A%2F%2Fwww.smashingmagazine.com%2F2018%2F01%2Funderstanding-using-rest-api%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-researchgate.net-48\"><span class=\"mw-cite-backlink\">^ <a href=\"#cite_ref-researchgate.net_48-0\"><sup><i><b>a</b></i></sup></a> <a href=\"#cite_ref-researchgate.net_48-1\"><sup><i><b>b</b></i></sup></a></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFShiZhongXieLi2011\" class=\"citation conference cs1\">Shi, Lin; Zhong, Hao; Xie, Tao; Li, Mingshu (2011). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.researchgate.net/publication/225147411\"><i>An Empirical Study on Evolution of API Documentation</i></a>. International Conference on Fundamental Approaches to Software Engineering. Lecture Notes in Computer Science. Vol. 6603. pp. <span class=\"nowrap\">416\u2013</span>431. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1007%2F978-3-642-19811-3_29\">10.1007/978-3-642-19811-3_29</a>. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/978-3-642-19810-6\" title=\"Special:BookSources/978-3-642-19810-6\"><bdi>978-3-642-19810-6</bdi></a><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">22 July</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=conference&rft.btitle=An+Empirical+Study+on+Evolution+of+API+Documentation&rft.series=Lecture+Notes+in+Computer+Science&rft.pages=%3Cspan+class%3D%22nowrap%22%3E416-%3C%2Fspan%3E431&rft.date=2011&rft_id=info%3Adoi%2F10.1007%2F978-3-642-19811-3_29&rft.isbn=978-3-642-19810-6&rft.aulast=Shi&rft.aufirst=Lin&rft.au=Zhong%2C+Hao&rft.au=Xie%2C+Tao&rft.au=Li%2C+Mingshu&rft_id=https%3A%2F%2Fwww.researchgate.net%2Fpublication%2F225147411&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-49\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-49\">^</a></b></span> <span class=\"reference-text\"><a rel=\"nofollow\" class=\"external text\" href=\"https://github.com/google/guava\">google/guava: Google Core Libraries for Java</a> on <a href=\"/wiki/GitHub\" title=\"GitHub\">GitHub</a></span>\n</li>\n<li id=\"cite_note-OracleDeprecation16-50\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-OracleDeprecation16_50-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFOracle\" class=\"citation web cs1\">Oracle. <a rel=\"nofollow\" class=\"external text\" href=\"http://docs.oracle.com/javase/7/docs/technotes/guides/javadoc/deprecation/deprecation.html\">\"How and When to Deprecate APIs\"</a>. <i>Java SE Documentation</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2 August</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Java+SE+Documentation&rft.atitle=How+and+When+to+Deprecate+APIs&rft.au=Oracle&rft_id=http%3A%2F%2Fdocs.oracle.com%2Fjavase%2F7%2Fdocs%2Ftechnotes%2Fguides%2Fjavadoc%2Fdeprecation%2Fdeprecation.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-MendezBaudry2013-51\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-MendezBaudry2013_51-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFMendezBaudryMonperrus2013\" class=\"citation conference cs1\">Mendez, Diego; Baudry, Benoit; Monperrus, Martin (2013). <a rel=\"nofollow\" class=\"external text\" href=\"https://hal.archives-ouvertes.fr/hal-00844753/document\"><i>Empirical evidence of large-scale diversity in API usage of object-oriented software</i></a>. 2013 IEEE 13th International Working Conference on Source Code Analysis and Manipulation (SCAM). pp. <span class=\"nowrap\">43\u2013</span>52. <a href=\"/wiki/ArXiv_(identifier)\" class=\"mw-redirect\" title=\"ArXiv (identifier)\">arXiv</a>:<span class=\"id-lock-free\" title=\"Freely accessible\"><a rel=\"nofollow\" class=\"external text\" href=\"https://arxiv.org/abs/1307.4062\">1307.4062</a></span>. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1109%2FSCAM.2013.6648183\">10.1109/SCAM.2013.6648183</a>. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/978-1-4673-5739-5\" title=\"Special:BookSources/978-1-4673-5739-5\"><bdi>978-1-4673-5739-5</bdi></a>. <a href=\"/wiki/S2CID_(identifier)\" class=\"mw-redirect\" title=\"S2CID (identifier)\">S2CID</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://api.semanticscholar.org/CorpusID:6890739\">6890739</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=conference&rft.btitle=Empirical+evidence+of+large-scale+diversity+in+API+usage+of+object-oriented+software&rft.pages=%3Cspan+class%3D%22nowrap%22%3E43-%3C%2Fspan%3E52&rft.date=2013&rft_id=info%3Aarxiv%2F1307.4062&rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A6890739%23id-name%3DS2CID&rft_id=info%3Adoi%2F10.1109%2FSCAM.2013.6648183&rft.isbn=978-1-4673-5739-5&rft.aulast=Mendez&rft.aufirst=Diego&rft.au=Baudry%2C+Benoit&rft.au=Monperrus%2C+Martin&rft_id=https%3A%2F%2Fhal.archives-ouvertes.fr%2Fhal-00844753%2Fdocument&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-VentureBeat-52\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-VentureBeat_52-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFTakanashi2020\" class=\"citation web cs1\">Takanashi, Dean (19 February 2020). <a rel=\"nofollow\" class=\"external text\" href=\"https://venturebeat.com/2020/02/19/akamai-cybercriminals-are-attacking-apis-at-financial-services-firms/\">\"Akamai: Cybercriminals are attacking APIs at financial services firms\"</a>. <i>Venture Beat</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">27 February</span> 2020</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Venture+Beat&rft.atitle=Akamai%3A+Cybercriminals+are+attacking+APIs+at+financial+services+firms&rft.date=2020-02-19&rft.aulast=Takanashi&rft.aufirst=Dean&rft_id=https%3A%2F%2Fventurebeat.com%2F2020%2F02%2F19%2Fakamai-cybercriminals-are-attacking-apis-at-financial-services-firms%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-DekelHerbsleb9-53\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-DekelHerbsleb9_53-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFDekelHerbsleb2009\" class=\"citation journal cs1\">Dekel, Uri; Herbsleb, James D. (May 2009). \"Improving API Documentation Usability with Knowledge Pushing\". <i>Institute for Software Research, School of Computer Science</i>. <a href=\"/wiki/CiteSeerX_(identifier)\" class=\"mw-redirect\" title=\"CiteSeerX (identifier)\">CiteSeerX</a> <span class=\"id-lock-free\" title=\"Freely accessible\"><a rel=\"nofollow\" class=\"external text\" href=\"https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.446.4214\">10.1.1.446.4214</a></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Institute+for+Software+Research%2C+School+of+Computer+Science&rft.atitle=Improving+API+Documentation+Usability+with+Knowledge+Pushing&rft.date=2009-05&rft_id=https%3A%2F%2Fciteseerx.ist.psu.edu%2Fviewdoc%2Fsummary%3Fdoi%3D10.1.1.446.4214%23id-name%3DCiteSeerX&rft.aulast=Dekel&rft.aufirst=Uri&rft.au=Herbsleb%2C+James+D.&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-ParninTreude11-54\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-ParninTreude11_54-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFParninTreude2011\" class=\"citation conference cs1\">Parnin, Chris; Treude, Cristoph (May 2011). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.xmedo.com/measuring-api-documentation-web/\">\"Measuring API documentation on the web\"</a>. <i>Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering</i>. pp. <span class=\"nowrap\">25\u2013</span>30. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1145%2F1984701.1984706\">10.1145/1984701.1984706</a>. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/9781450305952\" title=\"Special:BookSources/9781450305952\"><bdi>9781450305952</bdi></a>. <a href=\"/wiki/S2CID_(identifier)\" class=\"mw-redirect\" title=\"S2CID (identifier)\">S2CID</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://api.semanticscholar.org/CorpusID:17751901\">17751901</a><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">22 July</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=conference&rft.atitle=Measuring+API+documentation+on+the+web&rft.btitle=Proceedings+of+the+2nd+International+Workshop+on+Web+2.0+for+Software+Engineering&rft.pages=%3Cspan+class%3D%22nowrap%22%3E25-%3C%2Fspan%3E30&rft.date=2011-05&rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A17751901%23id-name%3DS2CID&rft_id=info%3Adoi%2F10.1145%2F1984701.1984706&rft.isbn=9781450305952&rft.aulast=Parnin&rft.aufirst=Chris&rft.au=Treude%2C+Cristoph&rft_id=https%3A%2F%2Fwww.xmedo.com%2Fmeasuring-api-documentation-web%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-MaalejRobillard12-55\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-MaalejRobillard12_55-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFMaalejRobillard2012\" class=\"citation journal cs1\">Maalej, Waleed; Robillard, Martin P. (September 2012). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.cs.mcgill.ca/~martin/papers/tse2013a.pdf\">\"Patterns of Knowledge in API Reference Documentation\"</a> <span class=\"cs1-format\">(PDF)</span>. <i>IEEE Transactions on Software Engineering</i>. <b>39</b> (9): <span class=\"nowrap\">1264\u2013</span>1282. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1109%2FTSE.2013.12\">10.1109/TSE.2013.12</a><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">22 July</span> 2016</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=IEEE+Transactions+on+Software+Engineering&rft.atitle=Patterns+of+Knowledge+in+API+Reference+Documentation&rft.volume=39&rft.issue=9&rft.pages=%3Cspan+class%3D%22nowrap%22%3E1264-%3C%2Fspan%3E1282&rft.date=2012-09&rft_id=info%3Adoi%2F10.1109%2FTSE.2013.12&rft.aulast=Maalej&rft.aufirst=Waleed&rft.au=Robillard%2C+Martin+P.&rft_id=https%3A%2F%2Fwww.cs.mcgill.ca%2F~martin%2Fpapers%2Ftse2013a.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-MonperrusEichberg11-56\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-MonperrusEichberg11_56-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFMonperrusEichbergTekesMezini2011\" class=\"citation journal cs1\">Monperrus, Martin; Eichberg, Michael; Tekes, Elif; Mezini, Mira (3 December 2011). \"What should developers be aware of? An empirical study on the directives of API documentation\". <i>Empirical Software Engineering</i>. <b>17</b> (6): <span class=\"nowrap\">703\u2013</span>737. <a href=\"/wiki/ArXiv_(identifier)\" class=\"mw-redirect\" title=\"ArXiv (identifier)\">arXiv</a>:<span class=\"id-lock-free\" title=\"Freely accessible\"><a rel=\"nofollow\" class=\"external text\" href=\"https://arxiv.org/abs/1205.6363\">1205.6363</a></span>. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1007%2Fs10664-011-9186-4\">10.1007/s10664-011-9186-4</a>. <a href=\"/wiki/S2CID_(identifier)\" class=\"mw-redirect\" title=\"S2CID (identifier)\">S2CID</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://api.semanticscholar.org/CorpusID:8174618\">8174618</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Empirical+Software+Engineering&rft.atitle=What+should+developers+be+aware+of%3F+An+empirical+study+on+the+directives+of+API+documentation&rft.volume=17&rft.issue=6&rft.pages=%3Cspan+class%3D%22nowrap%22%3E703-%3C%2Fspan%3E737&rft.date=2011-12-03&rft_id=info%3Aarxiv%2F1205.6363&rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A8174618%23id-name%3DS2CID&rft_id=info%3Adoi%2F10.1007%2Fs10664-011-9186-4&rft.aulast=Monperrus&rft.aufirst=Martin&rft.au=Eichberg%2C+Michael&rft.au=Tekes%2C+Elif&rft.au=Mezini%2C+Mira&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-57\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-57\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://web.archive.org/web/20110925021948/http://download.oracle.com/javase/1,5.0/docs/guide/language/annotations.html\">\"Annotations\"</a>. <a href=\"/wiki/Sun_Microsystems\" title=\"Sun Microsystems\">Sun Microsystems</a>. Archived from <a rel=\"nofollow\" class=\"external text\" href=\"http://download.oracle.com/javase/1,5.0/docs/guide/language/annotations.html\">the original</a> on 2011-09-25<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2011-09-30</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Annotations&rft.pub=Sun+Microsystems&rft_id=http%3A%2F%2Fdownload.oracle.com%2Fjavase%2F1%2C5.0%2Fdocs%2Fguide%2Flanguage%2Fannotations.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span>.</span>\n</li>\n<li id=\"cite_note-58\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-58\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFBruchMeziniMonperrus2010\" class=\"citation conference cs1\">Bruch, Marcel; Mezini, Mira; Monperrus, Martin (2010). <i>Mining subclassing directives to improve framework reuse</i>. 2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010). pp. <span class=\"nowrap\">141\u2013</span>150. <a href=\"/wiki/CiteSeerX_(identifier)\" class=\"mw-redirect\" title=\"CiteSeerX (identifier)\">CiteSeerX</a> <span class=\"id-lock-free\" title=\"Freely accessible\"><a rel=\"nofollow\" class=\"external text\" href=\"https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.434.15\">10.1.1.434.15</a></span>. <a href=\"/wiki/Doi_(identifier)\" class=\"mw-redirect\" title=\"Doi (identifier)\">doi</a>:<a rel=\"nofollow\" class=\"external text\" href=\"https://doi.org/10.1109%2Fmsr.2010.5463347\">10.1109/msr.2010.5463347</a>. <a href=\"/wiki/ISBN_(identifier)\" class=\"mw-redirect\" title=\"ISBN (identifier)\">ISBN</a> <a href=\"/wiki/Special:BookSources/978-1-4244-6802-7\" title=\"Special:BookSources/978-1-4244-6802-7\"><bdi>978-1-4244-6802-7</bdi></a>. <a href=\"/wiki/S2CID_(identifier)\" class=\"mw-redirect\" title=\"S2CID (identifier)\">S2CID</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://api.semanticscholar.org/CorpusID:1026918\">1026918</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=conference&rft.btitle=Mining+subclassing+directives+to+improve+framework+reuse&rft.pages=%3Cspan+class%3D%22nowrap%22%3E141-%3C%2Fspan%3E150&rft.date=2010&rft_id=https%3A%2F%2Fciteseerx.ist.psu.edu%2Fviewdoc%2Fsummary%3Fdoi%3D10.1.1.434.15%23id-name%3DCiteSeerX&rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A1026918%23id-name%3DS2CID&rft_id=info%3Adoi%2F10.1109%2Fmsr.2010.5463347&rft.isbn=978-1-4244-6802-7&rft.aulast=Bruch&rft.aufirst=Marcel&rft.au=Mezini%2C+Mira&rft.au=Monperrus%2C+Martin&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-59\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-59\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"http://www.drdobbs.com/jvm/232901227\">\"Oracle and the End of Programming As We Know It\"</a>. DrDobbs. 2012-05-01<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2012-05-09</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Oracle+and+the+End+of+Programming+As+We+Know+It&rft.pub=DrDobbs&rft.date=2012-05-01&rft_id=http%3A%2F%2Fwww.drdobbs.com%2Fjvm%2F232901227&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-60\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-60\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://tgdaily.com/business/business-law-features/63756-apis-cant-be-copyrighted-says-judge-in-oracle-case/\">\"APIs Can't be Copyrighted Says Judge in Oracle Case\"</a>. TGDaily. 2012-06-01<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2012-12-06</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=APIs+Can%27t+be+Copyrighted+Says+Judge+in+Oracle+Case&rft.pub=TGDaily&rft.date=2012-06-01&rft_id=https%3A%2F%2Ftgdaily.com%2Fbusiness%2Fbusiness-law-features%2F63756-apis-cant-be-copyrighted-says-judge-in-oracle-case%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-61\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-61\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://www.wired.com/wiredenterprise/wp-content/uploads/2012/05/Judge-Alsup-Ruling-on-Copyrightability-of-APIs.pdf\">\"Oracle America, Inc. vs. Google Inc\"</a> <span class=\"cs1-format\">(PDF)</span>. <a href=\"/wiki/Wired_(magazine)\" title=\"Wired (magazine)\">Wired</a>. 2012-05-31<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2013-09-22</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Oracle+America%2C+Inc.+vs.+Google+Inc.&rft.pub=Wired&rft.date=2012-05-31&rft_id=https%3A%2F%2Fwww.wired.com%2Fwiredenterprise%2Fwp-content%2Fuploads%2F2012%2F05%2FJudge-Alsup-Ruling-on-Copyrightability-of-APIs.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-62\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-62\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://law.justia.com/cases/federal/appellate-courts/cafc/13-1021/13-1021-2014-05-09.html\">\"Oracle Am., Inc. v. Google Inc., No. 13-1021, Fed. Cir. 2014\"</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Oracle+Am.%2C+Inc.+v.+Google+Inc.%2C+No.+13-1021%2C+Fed.+Cir.+2014&rft_id=https%3A%2F%2Flaw.justia.com%2Fcases%2Ffederal%2Fappellate-courts%2Fcafc%2F13-1021%2F13-1021-2014-05-09.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-63\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-63\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFRosenblatt,_Seth2014\" class=\"citation news cs1\">Rosenblatt, Seth (May 9, 2014). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.cnet.com/news/court-sides-with-oracle-over-android-in-java-patent-appeal/\">\"Court sides with Oracle over Android in Java patent appeal\"</a>. <i>CNET</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2014-05-10</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=CNET&rft.atitle=Court+sides+with+Oracle+over+Android+in+Java+patent+appeal&rft.date=2014-05-09&rft.au=Rosenblatt%2C+Seth&rft_id=https%3A%2F%2Fwww.cnet.com%2Fnews%2Fcourt-sides-with-oracle-over-android-in-java-patent-appeal%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-64\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-64\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://arstechnica.com/tech-policy/2016/05/google-wins-trial-against-oracle-as-jury-finds-android-is-fair-use/\">\"Google beats Oracle \u2013 Android makes \"fair use\" of Java APIs\"</a>. <i>Ars Technica</i>. 2016-05-26<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2016-07-28</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Ars+Technica&rft.atitle=Google+beats+Oracle+%E2%80%93+Android+makes+%22fair+use%22+of+Java+APIs&rft.date=2016-05-26&rft_id=https%3A%2F%2Farstechnica.com%2Ftech-policy%2F2016%2F05%2Fgoogle-wins-trial-against-oracle-as-jury-finds-android-is-fair-use%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-bbn_march2018-65\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-bbn_march2018_65-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFDecker2018\" class=\"citation web cs1\">Decker, Susan (March 27, 2018). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.bloomberg.com/news/articles/2018-03-27/oracle-wins-revival-of-billion-dollar-case-against-google\">\"Oracle Wins Revival of Billion-Dollar Case Against Google\"</a>. <i><a href=\"/wiki/Bloomberg_Businessweek\" title=\"Bloomberg Businessweek\">Bloomberg Businessweek</a></i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">March 27,</span> 2018</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Bloomberg+Businessweek&rft.atitle=Oracle+Wins+Revival+of+Billion-Dollar+Case+Against+Google&rft.date=2018-03-27&rft.aulast=Decker&rft.aufirst=Susan&rft_id=https%3A%2F%2Fwww.bloomberg.com%2Fnews%2Farticles%2F2018-03-27%2Foracle-wins-revival-of-billion-dollar-case-against-google&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-ars_Jan2019-66\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-ars_Jan2019_66-0\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFLee2019\" class=\"citation web cs1\">Lee, Timothy (January 25, 2019). <a rel=\"nofollow\" class=\"external text\" href=\"https://arstechnica.com/tech-policy/2019/01/google-asks-supreme-court-to-overrule-disastrous-ruling-on-api-copyrights/\">\"Google asks Supreme Court to overrule disastrous ruling on API copyrights\"</a>. <i><a href=\"/wiki/Ars_Technica\" title=\"Ars Technica\">Ars Technica</a></i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">February 8,</span> 2019</span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Ars+Technica&rft.atitle=Google+asks+Supreme+Court+to+overrule+disastrous+ruling+on+API+copyrights&rft.date=2019-01-25&rft.aulast=Lee&rft.aufirst=Timothy&rft_id=https%3A%2F%2Farstechnica.com%2Ftech-policy%2F2019%2F01%2Fgoogle-asks-supreme-court-to-overrule-disastrous-ruling-on-api-copyrights%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-67\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-67\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFvkimber2020\" class=\"citation web cs1\">vkimber (2020-09-28). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.law.cornell.edu/supct/cert/18-956\">\"Google LLC v. Oracle America, Inc\"</a>. <i>LII / Legal Information Institute</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2021-03-06</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=LII+%2F+Legal+Information+Institute&rft.atitle=Google+LLC+v.+Oracle+America%2C+Inc.&rft.date=2020-09-28&rft.au=vkimber&rft_id=https%3A%2F%2Fwww.law.cornell.edu%2Fsupct%2Fcert%2F18-956&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-68\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-68\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://www.supremecourt.gov/opinions/20pdf/18-956_d18f.pdf\">\"Supreme Court of the United States, No. 18\u2013956, GOOGLE LLC, PETITIONER v. ORACLE AMERICA, INC\"</a> <span class=\"cs1-format\">(PDF)</span>. April 5, 2021.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Supreme+Court+of+the+United+States%2C+No.+18%E2%80%93956%2C+GOOGLE+LLC%2C+PETITIONER+v.+ORACLE+AMERICA%2C+INC.&rft.date=2021-04-05&rft_id=https%3A%2F%2Fwww.supremecourt.gov%2Fopinions%2F20pdf%2F18-956_d18f.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-69\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-69\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://www.radware.com/blog/application-protection/protecting-apis-in-the-age-of-business-logic-attacks/\">\"Protecting APIs in the Age of Business Logic Attacks\"</a>. <i>www.radware.com</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2025-03-01</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=www.radware.com&rft.atitle=Protecting+APIs+in+the+Age+of+Business+Logic+Attacks&rft_id=https%3A%2F%2Fwww.radware.com%2Fblog%2Fapplication-protection%2Fprotecting-apis-in-the-age-of-business-logic-attacks%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-70\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-70\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation web cs1\"><a rel=\"nofollow\" class=\"external text\" href=\"https://blog.zerodefendsecurity.com/2025/03/01/the-silent-api-threat-how-business-logic-attacks-are-changing-cybersecurity/\">\"The Silent API Threat: How Business Logic Attacks Are Changing Cybersecurity \u2013 Zero Defend Security\"</a>. 2025-03-01<span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2025-03-01</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=The+Silent+API+Threat%3A+How+Business+Logic+Attacks+Are+Changing+Cybersecurity+%E2%80%93+Zero+Defend+Security&rft.date=2025-03-01&rft_id=https%3A%2F%2Fblog.zerodefendsecurity.com%2F2025%2F03%2F01%2Fthe-silent-api-threat-how-business-logic-attacks-are-changing-cybersecurity%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-71\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-71\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFMari\u01072022\" class=\"citation web cs1\">Mari\u0107, Nedim (2022-04-04). <a rel=\"nofollow\" class=\"external text\" href=\"https://brightsec.com/blog/api-security/\">\"What Is API security? The Complete Guide\"</a><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2025-03-01</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=What+Is+API+security%3F+The+Complete+Guide&rft.date=2022-04-04&rft.aulast=Mari%C4%87&rft.aufirst=Nedim&rft_id=https%3A%2F%2Fbrightsec.com%2Fblog%2Fapi-security%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n<li id=\"cite_note-72\"><span class=\"mw-cite-backlink\"><b><a href=\"#cite_ref-72\">^</a></b></span> <span class=\"reference-text\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite id=\"CITEREFRichardson2023\" class=\"citation web cs1\">Richardson, Luke (2023-06-23). <a rel=\"nofollow\" class=\"external text\" href=\"https://www.imperva.com/blog/understanding-business-logic-attacks/\">\"Business Logic Attacks: Why Should You Care? | Understanding Business Logic Attacks & Their Impact | Imperva\"</a>. <i>Blog</i><span class=\"reference-accessdate\">. Retrieved <span class=\"nowrap\">2025-03-01</span></span>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Blog&rft.atitle=Business+Logic+Attacks%3A+Why+Should+You+Care%3F+%7C+Understanding+Business+Logic+Attacks+%26+Their+Impact+%7C+Imperva&rft.date=2023-06-23&rft.aulast=Richardson&rft.aufirst=Luke&rft_id=https%3A%2F%2Fwww.imperva.com%2Fblog%2Funderstanding-business-logic-attacks%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span></span>\n</li>\n</ol></div></div>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"Further_reading\">Further reading</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=21\" title=\"Edit section: Further reading\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<ul><li><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1238218222\" /><cite class=\"citation journal cs1\">Taina Bucher (16 November 2013). <a rel=\"nofollow\" class=\"external text\" href=\"http://computationalculture.net/article/objects-of-intense-feeling-the-case-of-the-twitter-api\">\"Objects of Intense Feeling: The Case of the Twitter API\"</a>. <i>Computational Culture</i> (3). <a href=\"/wiki/ISSN_(identifier)\" class=\"mw-redirect\" title=\"ISSN (identifier)\">ISSN</a> <a rel=\"nofollow\" class=\"external text\" href=\"https://search.worldcat.org/issn/2047-2390\">2047-2390</a>.</cite><span title=\"ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Computational+Culture&rft.atitle=Objects+of+Intense+Feeling%3A+The+Case+of+the+Twitter+API&rft.issue=3&rft.date=2013-11-16&rft.issn=2047-2390&rft.au=Taina+Bucher&rft_id=http%3A%2F%2Fcomputationalculture.net%2Farticle%2Fobjects-of-intense-feeling-the-case-of-the-twitter-api&rfr_id=info%3Asid%2Fen.wikipedia.org%3AAPI\" class=\"Z3988\"></span> Argues that \"APIs are far from neutral tools\" and form a key part of contemporary programming, understood as a fundamental part of culture.</li>\n<li><a rel=\"nofollow\" class=\"external text\" href=\"https://www.supremecourt.gov/opinions/20pdf/18-956_d18f.pdf\">What is an API?</a> \u2013 in the U.S. Supreme <a href=\"/wiki/Court_opinion\" class=\"mw-redirect\" title=\"Court opinion\">Court opinion</a>, <a href=\"/wiki/Google_LLC_v._Oracle_America,_Inc.\" title=\"Google LLC v. Oracle America, Inc.\">Google v. Oracle 2021</a>, pp. 3\u20137 \u2013 \"For each task, there is <a href=\"/wiki/Source_code\" title=\"Source code\">computer code</a>; API (also known as Application Program Interface) is the method for calling that 'computer code' (instruction \u2013 like a <a href=\"/wiki/Recipe\" title=\"Recipe\">recipe</a> \u2013 rather than cooking instruction, this is <a href=\"/wiki/Computer\" title=\"Computer\">machine</a> instruction) to be carry out\"</li>\n<li><a rel=\"nofollow\" class=\"external text\" href=\"http://ondrejka.net/history/2014/02/28/maury.html\">Maury, Innovation and Change</a> \u2013 Cory Ondrejka \\ February 28, 2014 \\ \" ...proposed a public API to let computers talk to each other\". (<a rel=\"nofollow\" class=\"external text\" href=\"https://web.archive.org/web/20211018221509/https://www.textise.net/showText.aspx?strURL=http://ondrejka.net/history/2014/02/28/maury.html\">Textise</a> URL)</li></ul>\n<div class=\"mw-heading mw-heading2\"><h2 id=\"External_links\">External links</h2><span class=\"mw-editsection\"><span class=\"mw-editsection-bracket\">[</span><a href=\"/w/index.php?title=API&action=edit&section=22\" title=\"Edit section: External links\"><span>edit</span></a><span class=\"mw-editsection-bracket\">]</span></span></div>\n<ul><li><a rel=\"nofollow\" class=\"external text\" href=\"https://go.forrester.com/what-it-means/ep218-google-oracle-api-case/\">Forrester : IT industry : API Case : Google v. Oracle</a> \u2013 May 20, 2021 \u2013 content format: Audio with text \u2013 length 26:41</li></ul>\n<div class=\"navbox-styles\"><style data-mw-deduplicate=\"TemplateStyles:r1129693374\">.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:\": \"}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:\" \u00b7 \";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:\" (\";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:\")\";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:\" \"counter(listitem)\"\\a0 \"}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:\" (\"counter(listitem)\"\\a0 \"}</style><style data-mw-deduplicate=\"TemplateStyles:r1236075235\">.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}</style></div><div role=\"navigation\" class=\"navbox\" aria-labelledby=\"Operating_systems310\" style=\"padding:3px\"><table class=\"nowraplinks mw-collapsible autocollapse navbox-inner\" style=\"border-spacing:0;background:transparent;color:inherit\"><tbody><tr><th scope=\"col\" class=\"navbox-title\" colspan=\"2\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1129693374\" /><style data-mw-deduplicate=\"TemplateStyles:r1239400231\">.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:\"[ \"}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:\" ]\"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}</style><div class=\"navbar plainlinks hlist navbar-mini\"><ul><li class=\"nv-view\"><a href=\"/wiki/Template:Operating_systems\" title=\"Template:Operating systems\"><abbr title=\"View this template\">v</abbr></a></li><li class=\"nv-talk\"><a href=\"/wiki/Template_talk:Operating_systems\" title=\"Template talk:Operating systems\"><abbr title=\"Discuss this template\">t</abbr></a></li><li class=\"nv-edit\"><a href=\"/wiki/Special:EditPage/Template:Operating_systems\" title=\"Special:EditPage/Template:Operating systems\"><abbr title=\"Edit this template\">e</abbr></a></li></ul></div><div id=\"Operating_systems310\" style=\"font-size:114%;margin:0 4em\"><a href=\"/wiki/Operating_system\" title=\"Operating system\">Operating systems</a></div></th></tr><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:1%\">General</th><td class=\"navbox-list-with-group navbox-list navbox-odd hlist\" style=\"width:100%;padding:0\"><div style=\"padding:0 0.25em\">\n<ul><li><a href=\"/wiki/Comparison_of_operating_systems\" title=\"Comparison of operating systems\">Comparison</a></li>\n<li><a href=\"/wiki/Forensic_software_engineering\" title=\"Forensic software engineering\">Forensic engineering</a></li>\n<li><a href=\"/wiki/History_of_operating_systems\" title=\"History of operating systems\">History</a></li>\n<li><a href=\"/wiki/List_of_operating_systems\" title=\"List of operating systems\">List</a></li>\n<li><a href=\"/wiki/Timeline_of_operating_systems\" title=\"Timeline of operating systems\">Timeline</a></li>\n<li><a href=\"/wiki/Usage_share_of_operating_systems\" title=\"Usage share of operating systems\">Usage share</a></li>\n<li><a href=\"/wiki/Comparison_of_user_features_of_operating_systems\" title=\"Comparison of user features of operating systems\">User features comparison</a></li></ul>\n</div></td></tr><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:1%\">Variants</th><td class=\"navbox-list-with-group navbox-list navbox-even hlist\" style=\"width:100%;padding:0\"><div style=\"padding:0 0.25em\">\n<ul><li><a href=\"/wiki/Disk_operating_system\" title=\"Disk operating system\">Disk operating system</a></li>\n<li><a href=\"/wiki/Distributed_operating_system\" title=\"Distributed operating system\">Distributed operating system</a></li>\n<li><a href=\"/wiki/Embedded_operating_system\" title=\"Embedded operating system\">Embedded operating system</a></li>\n<li><a href=\"/wiki/Hobbyist_operating_system\" title=\"Hobbyist operating system\">Hobbyist operating system</a></li>\n<li><a href=\"/wiki/Just_enough_operating_system\" title=\"Just enough operating system\">Just enough operating system</a></li>\n<li><a href=\"/wiki/Mobile_operating_system\" title=\"Mobile operating system\">Mobile operating system</a></li>\n<li><a href=\"/wiki/Network_operating_system\" title=\"Network operating system\">Network operating system</a></li>\n<li><a href=\"/wiki/Object-oriented_operating_system\" title=\"Object-oriented operating system\">Object-oriented operating system</a></li>\n<li><a href=\"/wiki/Real-time_operating_system\" title=\"Real-time operating system\">Real-time operating system</a></li>\n<li><a href=\"/wiki/Supercomputer_operating_system\" title=\"Supercomputer operating system\">Supercomputer operating system</a></li></ul>\n</div></td></tr><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:1%\"><a href=\"/wiki/Kernel_(operating_system)\" title=\"Kernel (operating system)\">Kernel</a></th><td class=\"navbox-list-with-group navbox-list navbox-odd hlist\" style=\"width:100%;padding:0\"><div style=\"padding:0 0.25em\"></div><table class=\"nowraplinks navbox-subgroup\" style=\"border-spacing:0\"><tbody><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:6em\"><a href=\"/wiki/Computer_architecture\" title=\"Computer architecture\">Architectures</a></th><td class=\"navbox-list-with-group navbox-list navbox-odd\" style=\"padding:0\"><div style=\"padding:0 0.25em\">\n<ul><li><a href=\"/wiki/Exokernel\" title=\"Exokernel\">Exokernel</a></li>\n<li><a href=\"/wiki/Hybrid_kernel\" title=\"Hybrid kernel\">Hybrid</a></li>\n<li><a href=\"/wiki/Microkernel\" title=\"Microkernel\">Microkernel</a></li>\n<li><a href=\"/wiki/Monolithic_kernel\" title=\"Monolithic kernel\">Monolithic</a></li>\n<li><a href=\"/wiki/Multikernel\" title=\"Multikernel\">Multikernel</a></li>\n<li><a href=\"/wiki/Vkernel\" title=\"Vkernel\">vkernel</a></li>\n<li><a href=\"/wiki/Rump_kernel\" title=\"Rump kernel\">Rump kernel</a></li>\n<li><a href=\"/wiki/Unikernel\" title=\"Unikernel\">Unikernel</a></li></ul>\n</div></td></tr><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:6em\">Components</th><td class=\"navbox-list-with-group navbox-list navbox-even\" style=\"padding:0\"><div style=\"padding:0 0.25em\">\n<ul><li><a href=\"/wiki/Device_driver\" title=\"Device driver\">Device driver</a></li>\n<li><a href=\"/wiki/Loadable_kernel_module\" title=\"Loadable kernel module\">Loadable kernel module</a></li>\n<li><a href=\"/wiki/User_space_and_kernel_space\" title=\"User space and kernel space\">User space and kernel space</a></li></ul>\n</div></td></tr></tbody></table><div></div></td></tr><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:1%\"><a href=\"/wiki/Process_management_(computing)\" title=\"Process management (computing)\">Process management</a></th><td class=\"navbox-list-with-group navbox-list navbox-odd hlist\" style=\"width:100%;padding:0\"><div style=\"padding:0 0.25em\"></div><table class=\"nowraplinks navbox-subgroup\" style=\"border-spacing:0\"><tbody><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:6em\">Concepts</th><td class=\"navbox-list-with-group navbox-list navbox-odd\" style=\"padding:0\"><div style=\"padding:0 0.25em\">\n<ul><li><a href=\"/wiki/Computer_multitasking\" title=\"Computer multitasking\">Computer multitasking</a> (<a href=\"/wiki/Cooperative_multitasking\" title=\"Cooperative multitasking\">Cooperative</a>, <a href=\"/wiki/Preemption_(computing)\" title=\"Preemption (computing)\">Preemptive</a>)</li>\n<li><a href=\"/wiki/Context_switch\" title=\"Context switch\">Context switch</a></li>\n<li><a href=\"/wiki/Interrupt\" title=\"Interrupt\">Interrupt</a></li>\n<li><a href=\"/wiki/Inter-process_communication\" title=\"Inter-process communication\">IPC</a></li>\n<li><a href=\"/wiki/Process_(computing)\" title=\"Process (computing)\">Process</a></li>\n<li><a href=\"/wiki/Process_control_block\" title=\"Process control block\">Process control block</a></li>\n<li><a href=\"/wiki/Real-time_operating_system\" title=\"Real-time operating system\">Real-time</a></li>\n<li><a href=\"/wiki/Thread_(computing)\" title=\"Thread (computing)\">Thread</a></li>\n<li><a href=\"/wiki/Time-sharing\" title=\"Time-sharing\">Time-sharing</a></li></ul>\n</div></td></tr><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:6em\"><a href=\"/wiki/Scheduling_(computing)\" title=\"Scheduling (computing)\">Scheduling<br />algorithms</a></th><td class=\"navbox-list-with-group navbox-list navbox-even\" style=\"padding:0\"><div style=\"padding:0 0.25em\">\n<ul><li><a href=\"/wiki/Fixed-priority_pre-emptive_scheduling\" title=\"Fixed-priority pre-emptive scheduling\">Fixed-priority preemptive</a></li>\n<li><a href=\"/wiki/Multilevel_feedback_queue\" title=\"Multilevel feedback queue\">Multilevel feedback queue</a></li>\n<li><a href=\"/wiki/Round-robin_scheduling\" title=\"Round-robin scheduling\">Round-robin</a></li>\n<li><a href=\"/wiki/Shortest_job_next\" title=\"Shortest job next\">Shortest job next</a></li></ul>\n</div></td></tr></tbody></table><div></div></td></tr><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:1%\"><a href=\"/wiki/Memory_management_(operating_systems)\" title=\"Memory management (operating systems)\">Memory management</a>,<br /><a href=\"/wiki/System_resource\" title=\"System resource\">resource</a> protection</th><td class=\"navbox-list-with-group navbox-list navbox-odd hlist\" style=\"width:100%;padding:0\"><div style=\"padding:0 0.25em\">\n<ul><li><a href=\"/wiki/Bus_error\" title=\"Bus error\">Bus error</a></li>\n<li><a href=\"/wiki/General_protection_fault\" title=\"General protection fault\">General protection fault</a></li>\n<li><a href=\"/wiki/Memory_paging\" title=\"Memory paging\">Memory paging</a></li>\n<li><a href=\"/wiki/Memory_protection\" title=\"Memory protection\">Memory protection</a></li>\n<li><a href=\"/wiki/Protection_ring\" title=\"Protection ring\">Protection ring</a></li>\n<li><a href=\"/wiki/Segmentation_fault\" title=\"Segmentation fault\">Segmentation fault</a></li>\n<li><a href=\"/wiki/Virtual_memory\" title=\"Virtual memory\">Virtual memory</a></li></ul>\n</div></td></tr><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:1%\"><a href=\"/wiki/Non-volatile_memory\" title=\"Non-volatile memory\">Storage</a> access,<br /><a href=\"/wiki/File_system\" title=\"File system\">file systems</a></th><td class=\"navbox-list-with-group navbox-list navbox-even hlist\" style=\"width:100%;padding:0\"><div style=\"padding:0 0.25em\">\n<ul><li><a href=\"/wiki/Booting#BOOT-LOADER\" title=\"Booting\">Boot loader</a></li>\n<li><a href=\"/wiki/Defragmentation\" title=\"Defragmentation\">Defragmentation</a></li>\n<li><a href=\"/wiki/Device_file\" title=\"Device file\">Device file</a></li>\n<li><a href=\"/wiki/File_attribute\" title=\"File attribute\">File attribute</a></li>\n<li><a href=\"/wiki/Inode\" title=\"Inode\">Inode</a></li>\n<li><a href=\"/wiki/Journaling_file_system\" title=\"Journaling file system\">Journal</a></li>\n<li><a href=\"/wiki/Disk_partitioning\" title=\"Disk partitioning\">Partition</a></li>\n<li><a href=\"/wiki/Virtual_file_system\" title=\"Virtual file system\">Virtual file system</a></li>\n<li><a href=\"/wiki/Virtual_tape_library\" title=\"Virtual tape library\">Virtual tape library</a></li></ul>\n</div></td></tr><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:1%\">Supporting concepts</th><td class=\"navbox-list-with-group navbox-list navbox-odd hlist\" style=\"width:100%;padding:0\"><div style=\"padding:0 0.25em\">\n<ul><li><a class=\"mw-selflink selflink\">API</a></li>\n<li><a href=\"/wiki/Computer_network\" title=\"Computer network\">Computer network</a></li>\n<li><a href=\"/wiki/Hardware_abstraction\" title=\"Hardware abstraction\">HAL</a></li>\n<li><a href=\"/wiki/Live_CD\" title=\"Live CD\">Live CD</a></li>\n<li><a href=\"/wiki/Live_USB\" title=\"Live USB\">Live USB</a></li>\n<li><a href=\"/wiki/Shell_(computing)\" title=\"Shell (computing)\">Shell</a>\n<ul><li><a href=\"/wiki/Command-line_interface\" title=\"Command-line interface\">CLI</a></li>\n<li><a href=\"/wiki/User_interface\" title=\"User interface\">User interface</a></li></ul></li>\n<li><a href=\"/wiki/Preboot_Execution_Environment\" title=\"Preboot Execution Environment\">PXE</a></li></ul>\n</div></td></tr></tbody></table></div>\n<div class=\"navbox-styles\"><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1129693374\" /><link rel=\"mw-deduplicated-inline-style\" href=\"mw-data:TemplateStyles:r1236075235\" /></div><div role=\"navigation\" class=\"navbox authority-control\" aria-label=\"Navbox757\" style=\"padding:3px\"><table class=\"nowraplinks hlist navbox-inner\" style=\"border-spacing:0;background:transparent;color:inherit\"><tbody><tr><th scope=\"row\" class=\"navbox-group\" style=\"width:1%\"><a href=\"/wiki/Help:Authority_control\" title=\"Help:Authority control\">Authority control databases</a>: National <span class=\"mw-valign-text-top noprint\" typeof=\"mw:File/Frameless\"><a href=\"https://www.wikidata.org/wiki/Q165194#identifiers\" title=\"Edit this at Wikidata\"><img alt=\"Edit this at Wikidata\" src=\"//upload.wikimedia.org/wikipedia/en/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/10px-OOjs_UI_icon_edit-ltr-progressive.svg.png\" decoding=\"async\" width=\"10\" height=\"10\" class=\"mw-file-element\" srcset=\"//upload.wikimedia.org/wikipedia/en/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/15px-OOjs_UI_icon_edit-ltr-progressive.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/20px-OOjs_UI_icon_edit-ltr-progressive.svg.png 2x\" data-file-width=\"20\" data-file-height=\"20\" /></a></span></th><td class=\"navbox-list-with-group navbox-list navbox-odd\" style=\"width:100%;padding:0\"><div style=\"padding:0 0.25em\"><ul><li><span class=\"uid\"><a rel=\"nofollow\" class=\"external text\" href=\"https://d-nb.info/gnd/4430243-5\">Germany</a></span></li><li><span class=\"uid\"><a rel=\"nofollow\" class=\"external text\" href=\"https://id.loc.gov/authorities/sh98004527\">United States</a></span></li><li><span class=\"uid\"><a rel=\"nofollow\" class=\"external text\" href=\"https://catalogue.bnf.fr/ark:/12148/cb13337425v\">France</a></span></li><li><span class=\"uid\"><a rel=\"nofollow\" class=\"external text\" href=\"https://data.bnf.fr/ark:/12148/cb13337425v\">BnF data</a></span></li><li><span class=\"uid\"><a rel=\"nofollow\" class=\"external text\" href=\"https://www.nli.org.il/en/authorities/987007534972505171\">Israel</a></span></li></ul></div></td></tr></tbody></table></div>\n<!-- \nNewPP limit report\nParsed by mw\u2010api\u2010ext.eqiad.main\u201059d57ccbc5\u2010m5nz7\nCached time: 20250310153104\nCache expiry: 2592000\nReduced expiry: false\nComplications: [vary\u2010revision\u2010sha1, show\u2010toc]\nCPU time usage: 0.667 seconds\nReal time usage: 0.847 seconds\nPreprocessor visited node count: 4345/1000000\nPost\u2010expand include size: 159769/2097152 bytes\nTemplate argument size: 1641/2097152 bytes\nHighest expansion depth: 13/100\nExpensive parser function count: 4/500\nUnstrip recursion depth: 1/20\nUnstrip post\u2010expand size: 274476/5000000 bytes\nLua time usage: 0.419/10.000 seconds\nLua memory usage: 6048945/52428800 bytes\nNumber of Wikibase entities loaded: 1/400\n-->\n<!--\nTransclusion expansion time report (%,ms,calls,template)\n100.00% 732.858 1 -total\n 59.82% 438.427 1 Template:Reflist\n 17.45% 127.862 12 Template:Cite_book\n 16.99% 124.509 36 Template:Cite_web\n 10.83% 79.363 1 Template:Operating_system\n 10.06% 73.707 3 Template:Navbox\n 9.96% 72.984 1 Template:Short_description\n 6.22% 45.548 8 Template:Cite_conference\n 5.97% 43.719 2 Template:Pagetype\n 5.44% 39.886 10 Template:Cite_journal\n-->\n\n<!-- Saved in parser cache with key enwiki:pcache:27697009:|#|:idhash:canonical and timestamp 20250310153104 and revision id 1279784811. Rendering was triggered because: api-parse\n -->\n</div>"
},
"langlinks": [
{
"lang": "ar",
"url": "https://ar.wikipedia.org/wiki/%D9%88%D8%A7%D8%AC%D9%87%D8%A9_%D8%A8%D8%B1%D9%85%D8%AC%D8%A9_%D8%A7%D9%84%D8%AA%D8%B7%D8%A8%D9%8A%D9%82%D8%A7%D8%AA",
"langname": "Arabic",
"autonym": "\u0627\u0644\u0639\u0631\u0628\u064a\u0629",
"*": "\u0648\u0627\u062c\u0647\u0629 \u0628\u0631\u0645\u062c\u0629 \u0627\u0644\u062a\u0637\u0628\u064a\u0642\u0627\u062a"
},
{
"lang": "ast",
"url": "https://ast.wikipedia.org/wiki/Interfaz_de_programaci%C3%B3n_d%27aplicaciones",
"langname": "Asturian",
"autonym": "asturianu",
"*": "Interfaz de programaci\u00f3n d'aplicaciones"
},
{
"lang": "az",
"url": "https://az.wikipedia.org/wiki/T%C9%99tbiqi_proqramla%C5%9Fd%C4%B1rma_interfeysi",
"langname": "Azerbaijani",
"autonym": "az\u0259rbaycanca",
"*": "T\u0259tbiqi proqramla\u015fd\u0131rma interfeysi"
},
{
"lang": "bn",
"url": "https://bn.wikipedia.org/wiki/%E0%A6%85%E0%A7%8D%E0%A6%AF%E0%A6%BE%E0%A6%AA%E0%A7%8D%E0%A6%B2%E0%A6%BF%E0%A6%95%E0%A7%87%E0%A6%B6%E0%A6%A8_%E0%A6%AA%E0%A7%8D%E0%A6%B0%E0%A7%8B%E0%A6%97%E0%A7%8D%E0%A6%B0%E0%A6%BE%E0%A6%AE%E0%A6%BF%E0%A6%82_%E0%A6%87%E0%A6%A8%E0%A7%8D%E0%A6%9F%E0%A6%BE%E0%A6%B0%E0%A6%AB%E0%A7%87%E0%A6%B8",
"langname": "Bangla",
"autonym": "\u09ac\u09be\u0982\u09b2\u09be",
"*": "\u0985\u09cd\u09af\u09be\u09aa\u09cd\u09b2\u09bf\u0995\u09c7\u09b6\u09a8 \u09aa\u09cd\u09b0\u09cb\u0997\u09cd\u09b0\u09be\u09ae\u09bf\u0982 \u0987\u09a8\u09cd\u099f\u09be\u09b0\u09ab\u09c7\u09b8"
},
{
"lang": "bg",
"url": "https://bg.wikipedia.org/wiki/%D0%9F%D1%80%D0%B8%D0%BB%D0%BE%D0%B6%D0%BD%D0%BE-%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%B5%D0%BD_%D0%B8%D0%BD%D1%82%D0%B5%D1%80%D1%84%D0%B5%D0%B9%D1%81",
"langname": "Bulgarian",
"autonym": "\u0431\u044a\u043b\u0433\u0430\u0440\u0441\u043a\u0438",
"*": "\u041f\u0440\u0438\u043b\u043e\u0436\u043d\u043e-\u043f\u0440\u043e\u0433\u0440\u0430\u043c\u0435\u043d \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441"
},
{
"lang": "bar",
"url": "https://bar.wikipedia.org/wiki/API",
"langname": "Bavarian",
"autonym": "Boarisch",
"*": "API"
},
{
"lang": "bs",
"url": "https://bs.wikipedia.org/wiki/Aplikativni_programski_interfejs",
"langname": "Bosnian",
"autonym": "bosanski",
"*": "Aplikativni programski interfejs"
},
{
"lang": "ca",
"url": "https://ca.wikipedia.org/wiki/Interf%C3%ADcie_de_programaci%C3%B3_d%27aplicacions",
"langname": "Catalan",
"autonym": "catal\u00e0",
"*": "Interf\u00edcie de programaci\u00f3 d'aplicacions"
},
{
"lang": "cs",
"url": "https://cs.wikipedia.org/wiki/API",
"langname": "Czech",
"autonym": "\u010de\u0161tina",
"*": "API"
},
{
"lang": "da",
"url": "https://da.wikipedia.org/wiki/Application_programming_interface",
"langname": "Danish",
"autonym": "dansk",
"*": "Application programming interface"
},
{
"lang": "de",
"url": "https://de.wikipedia.org/wiki/Programmierschnittstelle",
"langname": "German",
"autonym": "Deutsch",
"*": "Programmierschnittstelle"
},
{
"lang": "et",
"url": "https://et.wikipedia.org/wiki/Rakendusliides",
"langname": "Estonian",
"autonym": "eesti",
"*": "Rakendusliides"
},
{
"lang": "el",
"url": "https://el.wikipedia.org/wiki/%CE%94%CE%B9%CE%B5%CF%80%CE%B1%CF%86%CE%AE_%CF%80%CF%81%CE%BF%CE%B3%CF%81%CE%B1%CE%BC%CE%BC%CE%B1%CF%84%CE%B9%CF%83%CE%BC%CE%BF%CF%8D_%CE%B5%CF%86%CE%B1%CF%81%CE%BC%CE%BF%CE%B3%CF%8E%CE%BD",
"langname": "Greek",
"autonym": "\u0395\u03bb\u03bb\u03b7\u03bd\u03b9\u03ba\u03ac",
"*": "\u0394\u03b9\u03b5\u03c0\u03b1\u03c6\u03ae \u03c0\u03c1\u03bf\u03b3\u03c1\u03b1\u03bc\u03bc\u03b1\u03c4\u03b9\u03c3\u03bc\u03bf\u03cd \u03b5\u03c6\u03b1\u03c1\u03bc\u03bf\u03b3\u03ce\u03bd"
},
{
"lang": "es",
"url": "https://es.wikipedia.org/wiki/API",
"langname": "Spanish",
"autonym": "espa\u00f1ol",
"*": "API"
},
{
"lang": "eo",
"url": "https://eo.wikipedia.org/wiki/Aplikprograma_interfaco",
"langname": "Esperanto",
"autonym": "Esperanto",
"*": "Aplikprograma interfaco"
},
{
"lang": "eu",
"url": "https://eu.wikipedia.org/wiki/API",
"langname": "Basque",
"autonym": "euskara",
"*": "API"
},
{
"lang": "fa",
"url": "https://fa.wikipedia.org/wiki/%D9%88%D8%A7%D8%B3%D8%B7_%D8%A8%D8%B1%D9%86%D8%A7%D9%85%D9%87%E2%80%8C%D9%86%D9%88%DB%8C%D8%B3%DB%8C_%DA%A9%D8%A7%D8%B1%D8%A8%D8%B1%D8%AF%DB%8C",
"langname": "Persian",
"autonym": "\u0641\u0627\u0631\u0633\u06cc",
"*": "\u0648\u0627\u0633\u0637 \u0628\u0631\u0646\u0627\u0645\u0647\u200c\u0646\u0648\u06cc\u0633\u06cc \u06a9\u0627\u0631\u0628\u0631\u062f\u06cc"
},
{
"lang": "fr",
"url": "https://fr.wikipedia.org/wiki/Interface_de_programmation",
"langname": "French",
"autonym": "fran\u00e7ais",
"*": "Interface de programmation"
},
{
"lang": "ga",
"url": "https://ga.wikipedia.org/wiki/Comh%C3%A9adan_feidhmchl%C3%A1ir",
"langname": "Irish",
"autonym": "Gaeilge",
"*": "Comh\u00e9adan feidhmchl\u00e1ir"
},
{
"lang": "gl",
"url": "https://gl.wikipedia.org/wiki/Interface_de_programaci%C3%B3n_de_aplicaci%C3%B3n",
"langname": "Galician",
"autonym": "galego",
"*": "Interface de programaci\u00f3n de aplicaci\u00f3n"
},
{
"lang": "ko",
"url": "https://ko.wikipedia.org/wiki/API",
"langname": "Korean",
"autonym": "\ud55c\uad6d\uc5b4",
"*": "API"
},
{
"lang": "ha",
"url": "https://ha.wikipedia.org/wiki/API",
"langname": "Hausa",
"autonym": "Hausa",
"*": "API"
},
{
"lang": "hy",
"url": "https://hy.wikipedia.org/wiki/Application_Programming_Interface_(API)",
"langname": "Armenian",
"autonym": "\u0570\u0561\u0575\u0565\u0580\u0565\u0576",
"*": "Application Programming Interface (API)"
},
{
"lang": "hi",
"url": "https://hi.wikipedia.org/wiki/%E0%A4%8F%E0%A4%AA%E0%A5%80%E0%A4%86%E0%A4%88",
"langname": "Hindi",
"autonym": "\u0939\u093f\u0928\u094d\u0926\u0940",
"*": "\u090f\u092a\u0940\u0906\u0908"
},
{
"lang": "hr",
"url": "https://hr.wikipedia.org/wiki/API",
"langname": "Croatian",
"autonym": "hrvatski",
"*": "API"
},
{
"lang": "io",
"url": "https://io.wikipedia.org/wiki/Aplikala_programif-interkonekto",
"langname": "Ido",
"autonym": "Ido",
"*": "Aplikala programif-interkonekto"
},
{
"lang": "ig",
"url": "https://ig.wikipedia.org/wiki/API",
"langname": "Igbo",
"autonym": "Igbo",
"*": "API"
},
{
"lang": "id",
"url": "https://id.wikipedia.org/wiki/Antarmuka_pemrograman_aplikasi",
"langname": "Indonesian",
"autonym": "Bahasa Indonesia",
"*": "Antarmuka pemrograman aplikasi"
},
{
"lang": "it",
"url": "https://it.wikipedia.org/wiki/Application_programming_interface",
"langname": "Italian",
"autonym": "italiano",
"*": "Application programming interface"
},
{
"lang": "he",
"url": "https://he.wikipedia.org/wiki/%D7%9E%D7%9E%D7%A9%D7%A7_%D7%AA%D7%9B%D7%A0%D7%95%D7%AA_%D7%99%D7%99%D7%A9%D7%95%D7%9E%D7%99%D7%9D",
"langname": "Hebrew",
"autonym": "\u05e2\u05d1\u05e8\u05d9\u05ea",
"*": "\u05de\u05de\u05e9\u05e7 \u05ea\u05db\u05e0\u05d5\u05ea \u05d9\u05d9\u05e9\u05d5\u05de\u05d9\u05dd"
},
{
"lang": "ka",
"url": "https://ka.wikipedia.org/wiki/%E1%83%90%E1%83%9E%E1%83%9A%E1%83%98%E1%83%99%E1%83%90%E1%83%AA%E1%83%98%E1%83%98%E1%83%A1_%E1%83%9E%E1%83%A0%E1%83%9D%E1%83%92%E1%83%A0%E1%83%90%E1%83%9B%E1%83%98%E1%83%A0%E1%83%94%E1%83%91%E1%83%98%E1%83%A1_%E1%83%98%E1%83%9C%E1%83%A2%E1%83%94%E1%83%A0%E1%83%A4%E1%83%94%E1%83%98%E1%83%A1%E1%83%98",
"langname": "Georgian",
"autonym": "\u10e5\u10d0\u10e0\u10d7\u10e3\u10da\u10d8",
"*": "\u10d0\u10de\u10da\u10d8\u10d9\u10d0\u10ea\u10d8\u10d8\u10e1 \u10de\u10e0\u10dd\u10d2\u10e0\u10d0\u10db\u10d8\u10e0\u10d4\u10d1\u10d8\u10e1 \u10d8\u10dc\u10e2\u10d4\u10e0\u10e4\u10d4\u10d8\u10e1\u10d8"
},
{
"lang": "kk",
"url": "https://kk.wikipedia.org/wiki/%D0%9F%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B0%D0%BB%D1%8B%D2%9B_%D0%B8%D0%BD%D1%82%D0%B5%D1%80%D1%84%D0%B5%D0%B9%D1%81",
"langname": "Kazakh",
"autonym": "\u049b\u0430\u0437\u0430\u049b\u0448\u0430",
"*": "\u041f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0430\u043b\u044b\u049b \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441"
},
{
"lang": "lv",
"url": "https://lv.wikipedia.org/wiki/Lietojumprogrammas_saskarne",
"langname": "Latvian",
"autonym": "latvie\u0161u",
"*": "Lietojumprogrammas saskarne"
},
{
"lang": "lt",
"url": "https://lt.wikipedia.org/wiki/Aplikacij%C5%B3_programavimo_s%C4%85saja",
"langname": "Lithuanian",
"autonym": "lietuvi\u0173",
"*": "Aplikacij\u0173 programavimo s\u0105saja"
},
{
"lang": "hu",
"url": "https://hu.wikipedia.org/wiki/Alkalmaz%C3%A1sprogramoz%C3%A1si_fel%C3%BClet",
"langname": "Hungarian",
"autonym": "magyar",
"*": "Alkalmaz\u00e1sprogramoz\u00e1si fel\u00fclet"
},
{
"lang": "ml",
"url": "https://ml.wikipedia.org/wiki/%E0%B4%86%E0%B4%AA%E0%B5%8D%E0%B4%B2%E0%B4%BF%E0%B4%95%E0%B5%8D%E0%B4%95%E0%B5%87%E0%B4%B7%E0%B5%BB_%E0%B4%AA%E0%B5%8D%E0%B4%B0%E0%B5%8B%E0%B4%97%E0%B5%8D%E0%B4%B0%E0%B4%BE%E0%B4%AE%E0%B4%BF%E0%B4%99%E0%B5%8D_%E0%B4%87%E0%B4%A8%E0%B5%8D%E0%B4%B1%E0%B5%BC%E0%B4%AB%E0%B5%87%E0%B4%B8%E0%B5%8D",
"langname": "Malayalam",
"autonym": "\u0d2e\u0d32\u0d2f\u0d3e\u0d33\u0d02",
"*": "\u0d06\u0d2a\u0d4d\u0d32\u0d3f\u0d15\u0d4d\u0d15\u0d47\u0d37\u0d7b \u0d2a\u0d4d\u0d30\u0d4b\u0d17\u0d4d\u0d30\u0d3e\u0d2e\u0d3f\u0d19\u0d4d \u0d07\u0d28\u0d4d\u0d31\u0d7c\u0d2b\u0d47\u0d38\u0d4d"
},
{
"lang": "xmf",
"url": "https://xmf.wikipedia.org/wiki/%E1%83%90%E1%83%9E%E1%83%9A%E1%83%98%E1%83%99%E1%83%90%E1%83%AA%E1%83%98%E1%83%90%E1%83%A8_%E1%83%9E%E1%83%A0%E1%83%9D%E1%83%92%E1%83%A0%E1%83%90%E1%83%9B%E1%83%98%E1%83%A0%E1%83%94%E1%83%91%E1%83%90%E1%83%A8_%E1%83%98%E1%83%9C%E1%83%A2%E1%83%94%E1%83%A0%E1%83%A4%E1%83%94%E1%83%98%E1%83%A1%E1%83%98",
"langname": "Mingrelian",
"autonym": "\u10db\u10d0\u10e0\u10d2\u10d0\u10da\u10e3\u10e0\u10d8",
"*": "\u10d0\u10de\u10da\u10d8\u10d9\u10d0\u10ea\u10d8\u10d0\u10e8 \u10de\u10e0\u10dd\u10d2\u10e0\u10d0\u10db\u10d8\u10e0\u10d4\u10d1\u10d0\u10e8 \u10d8\u10dc\u10e2\u10d4\u10e0\u10e4\u10d4\u10d8\u10e1\u10d8"
},
{
"lang": "ms",
"url": "https://ms.wikipedia.org/wiki/Antara_muka_pengaturcaraan_aplikasi",
"langname": "Malay",
"autonym": "Bahasa Melayu",
"*": "Antara muka pengaturcaraan aplikasi"
},
{
"lang": "mn",
"url": "https://mn.wikipedia.org/wiki/API",
"langname": "Mongolian",
"autonym": "\u043c\u043e\u043d\u0433\u043e\u043b",
"*": "API"
},
{
"lang": "nl",
"url": "https://nl.wikipedia.org/wiki/Application_programming_interface",
"langname": "Dutch",
"autonym": "Nederlands",
"*": "Application programming interface"
},
{
"lang": "ja",
"url": "https://ja.wikipedia.org/wiki/%E3%82%A2%E3%83%97%E3%83%AA%E3%82%B1%E3%83%BC%E3%82%B7%E3%83%A7%E3%83%B3%E3%83%97%E3%83%AD%E3%82%B0%E3%83%A9%E3%83%9F%E3%83%B3%E3%82%B0%E3%82%A4%E3%83%B3%E3%82%BF%E3%83%95%E3%82%A7%E3%83%BC%E3%82%B9",
"langname": "Japanese",
"autonym": "\u65e5\u672c\u8a9e",
"*": "\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u30d7\u30ed\u30b0\u30e9\u30df\u30f3\u30b0\u30a4\u30f3\u30bf\u30d5\u30a7\u30fc\u30b9"
},
{
"lang": "frr",
"url": "https://frr.wikipedia.org/wiki/API",
"langname": "Northern Frisian",
"autonym": "Nordfriisk",
"*": "API"
},
{
"lang": "no",
"url": "https://no.wikipedia.org/wiki/Programmeringsgrensesnitt",
"langname": "Norwegian",
"autonym": "norsk",
"*": "Programmeringsgrensesnitt"
},
{
"lang": "nn",
"url": "https://nn.wikipedia.org/wiki/Programmeringsgrensesnitt",
"langname": "Norwegian Nynorsk",
"autonym": "norsk nynorsk",
"*": "Programmeringsgrensesnitt"
},
{
"lang": "uz",
"url": "https://uz.wikipedia.org/wiki/API",
"langname": "Uzbek",
"autonym": "o\u02bbzbekcha / \u045e\u0437\u0431\u0435\u043a\u0447\u0430",
"*": "API"
},
{
"lang": "pms",
"url": "https://pms.wikipedia.org/wiki/API",
"langname": "Piedmontese",
"autonym": "Piemont\u00e8is",
"*": "API"
},
{
"lang": "pl",
"url": "https://pl.wikipedia.org/wiki/Interfejs_programowania_aplikacji",
"langname": "Polish",
"autonym": "polski",
"*": "Interfejs programowania aplikacji"
},
{
"lang": "pt",
"url": "https://pt.wikipedia.org/wiki/Interface_de_programa%C3%A7%C3%A3o_de_aplica%C3%A7%C3%B5es",
"langname": "Portuguese",
"autonym": "portugu\u00eas",
"*": "Interface de programa\u00e7\u00e3o de aplica\u00e7\u00f5es"
},
{
"lang": "ro",
"url": "https://ro.wikipedia.org/wiki/Application_Programming_Interface",
"langname": "Romanian",
"autonym": "rom\u00e2n\u0103",
"*": "Application Programming Interface"
},
{
"lang": "qu",
"url": "https://qu.wikipedia.org/wiki/API",
"langname": "Quechua",
"autonym": "Runa Simi",
"*": "API"
},
{
"lang": "ru",
"url": "https://ru.wikipedia.org/wiki/API",
"langname": "Russian",
"autonym": "\u0440\u0443\u0441\u0441\u043a\u0438\u0439",
"*": "API"
},
{
"lang": "sq",
"url": "https://sq.wikipedia.org/wiki/Interfejsi_p%C3%ABr_programimin_e_aplikacioneve",
"langname": "Albanian",
"autonym": "shqip",
"*": "Interfejsi p\u00ebr programimin e aplikacioneve"
},
{
"lang": "simple",
"url": "https://simple.wikipedia.org/wiki/Application_programming_interface",
"langname": "Simple English",
"autonym": "Simple English",
"*": "Application programming interface"
},
{
"lang": "sk",
"url": "https://sk.wikipedia.org/wiki/Application_programming_interface",
"langname": "Slovak",
"autonym": "sloven\u010dina",
"*": "Application programming interface"
},
{
"lang": "sl",
"url": "https://sl.wikipedia.org/wiki/Vmesnik_za_namensko_programiranje",
"langname": "Slovenian",
"autonym": "sloven\u0161\u010dina",
"*": "Vmesnik za namensko programiranje"
},
{
"lang": "ckb",
"url": "https://ckb.wikipedia.org/wiki/%D9%86%D8%A7%D9%88%D8%A8%DB%95%D8%B3%D8%AA%DB%8C_%D8%A8%DB%95%D8%B1%D9%86%D8%A7%D9%85%DB%95%D8%B3%D8%A7%D8%B2%DB%8C%DB%8C_%D8%A8%DB%95%D8%B1%D9%86%D8%A7%D9%85%DB%95%DB%8C_%D8%A8%DB%95%DA%A9%D8%A7%D8%B1%D8%A8%DB%95%D8%B1%DB%8C",
"langname": "Central Kurdish",
"autonym": "\u06a9\u0648\u0631\u062f\u06cc",
"*": "\u0646\u0627\u0648\u0628\u06d5\u0633\u062a\u06cc \u0628\u06d5\u0631\u0646\u0627\u0645\u06d5\u0633\u0627\u0632\u06cc\u06cc \u0628\u06d5\u0631\u0646\u0627\u0645\u06d5\u06cc \u0628\u06d5\u06a9\u0627\u0631\u0628\u06d5\u0631\u06cc"
},
{
"lang": "sr",
"url": "https://sr.wikipedia.org/wiki/API",
"langname": "Serbian",
"autonym": "\u0441\u0440\u043f\u0441\u043a\u0438 / srpski",
"*": "API"
},
{
"lang": "sh",
"url": "https://sh.wikipedia.org/wiki/Aplikacijsko_programsko_su%C4%8Delje",
"langname": "Serbo-Croatian",
"autonym": "srpskohrvatski / \u0441\u0440\u043f\u0441\u043a\u043e\u0445\u0440\u0432\u0430\u0442\u0441\u043a\u0438",
"*": "Aplikacijsko programsko su\u010delje"
},
{
"lang": "fi",
"url": "https://fi.wikipedia.org/wiki/Ohjelmointirajapinta",
"langname": "Finnish",
"autonym": "suomi",
"*": "Ohjelmointirajapinta"
},
{
"lang": "sv",
"url": "https://sv.wikipedia.org/wiki/Applikationsprogrammeringsgr%C3%A4nssnitt",
"langname": "Swedish",
"autonym": "svenska",
"*": "Applikationsprogrammeringsgr\u00e4nssnitt"
},
{
"lang": "tl",
"url": "https://tl.wikipedia.org/wiki/Application_programming_interface",
"langname": "Tagalog",
"autonym": "Tagalog",
"*": "Application programming interface"
},
{
"lang": "ta",
"url": "https://ta.wikipedia.org/wiki/%E0%AE%9A%E0%AF%86%E0%AE%AF%E0%AE%B2%E0%AE%BF_%E0%AE%A8%E0%AE%BF%E0%AE%B0%E0%AE%B2%E0%AE%BE%E0%AE%95%E0%AF%8D%E0%AE%95_%E0%AE%87%E0%AE%9F%E0%AF%88%E0%AE%AE%E0%AF%81%E0%AE%95%E0%AE%AE%E0%AF%8D",
"langname": "Tamil",
"autonym": "\u0ba4\u0bae\u0bbf\u0bb4\u0bcd",
"*": "\u0b9a\u0bc6\u0baf\u0bb2\u0bbf \u0ba8\u0bbf\u0bb0\u0bb2\u0bbe\u0b95\u0bcd\u0b95 \u0b87\u0b9f\u0bc8\u0bae\u0bc1\u0b95\u0bae\u0bcd"
},
{
"lang": "th",
"url": "https://th.wikipedia.org/wiki/%E0%B8%AA%E0%B9%88%E0%B8%A7%E0%B8%99%E0%B8%95%E0%B9%88%E0%B8%AD%E0%B8%9B%E0%B8%A3%E0%B8%B0%E0%B8%AA%E0%B8%B2%E0%B8%99%E0%B9%82%E0%B8%9B%E0%B8%A3%E0%B9%81%E0%B8%81%E0%B8%A3%E0%B8%A1%E0%B8%9B%E0%B8%A3%E0%B8%B0%E0%B8%A2%E0%B8%B8%E0%B8%81%E0%B8%95%E0%B9%8C",
"langname": "Thai",
"autonym": "\u0e44\u0e17\u0e22",
"*": "\u0e2a\u0e48\u0e27\u0e19\u0e15\u0e48\u0e2d\u0e1b\u0e23\u0e30\u0e2a\u0e32\u0e19\u0e42\u0e1b\u0e23\u0e41\u0e01\u0e23\u0e21\u0e1b\u0e23\u0e30\u0e22\u0e38\u0e01\u0e15\u0e4c"
},
{
"lang": "tr",
"url": "https://tr.wikipedia.org/wiki/Uygulama_programlama_aray%C3%BCz%C3%BC",
"langname": "Turkish",
"autonym": "T\u00fcrk\u00e7e",
"*": "Uygulama programlama aray\u00fcz\u00fc"
},
{
"lang": "uk",
"url": "https://uk.wikipedia.org/wiki/%D0%9F%D1%80%D0%B8%D0%BA%D0%BB%D0%B0%D0%B4%D0%BD%D0%B8%D0%B9_%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BD%D0%B8%D0%B9_%D1%96%D0%BD%D1%82%D0%B5%D1%80%D1%84%D0%B5%D0%B9%D1%81",
"langname": "Ukrainian",
"autonym": "\u0443\u043a\u0440\u0430\u0457\u043d\u0441\u044c\u043a\u0430",
"*": "\u041f\u0440\u0438\u043a\u043b\u0430\u0434\u043d\u0438\u0439 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043d\u0438\u0439 \u0456\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441"
},
{
"lang": "ur",
"url": "https://ur.wikipedia.org/wiki/%D8%A7%DB%8C%D9%BE%D9%84%DB%8C%DA%A9%DB%8C%D8%B4%D9%86_%D9%BE%D8%B1%D9%88%DA%AF%D8%B1%D8%A7%D9%85%D9%86%DA%AF_%D8%A7%D9%86%D9%B9%D8%B1%D9%81%DB%8C%D8%B3",
"langname": "Urdu",
"autonym": "\u0627\u0631\u062f\u0648",
"*": "\u0627\u06cc\u067e\u0644\u06cc\u06a9\u06cc\u0634\u0646 \u067e\u0631\u0648\u06af\u0631\u0627\u0645\u0646\u06af \u0627\u0646\u0679\u0631\u0641\u06cc\u0633"
},
{
"lang": "vi",
"url": "https://vi.wikipedia.org/wiki/Giao_di%E1%BB%87n_l%E1%BA%ADp_tr%C3%ACnh_%E1%BB%A9ng_d%E1%BB%A5ng",
"langname": "Vietnamese",
"autonym": "Ti\u1ebfng Vi\u1ec7t",
"*": "Giao di\u1ec7n l\u1eadp tr\u00ecnh \u1ee9ng d\u1ee5ng"
},
{
"lang": "wuu",
"url": "https://wuu.wikipedia.org/wiki/%E5%BA%94%E7%94%A8%E7%A8%8B%E5%BA%8F%E6%8E%A5%E5%8F%A3",
"langname": "Wu",
"autonym": "\u5434\u8bed",
"*": "\u5e94\u7528\u7a0b\u5e8f\u63a5\u53e3"
},
{
"lang": "zh-yue",
"url": "https://zh-yue.wikipedia.org/wiki/%E6%87%89%E7%94%A8%E7%A8%8B%E5%BC%8F%E4%BB%8B%E9%9D%A2",
"langname": "Cantonese",
"autonym": "\u7cb5\u8a9e",
"*": "\u61c9\u7528\u7a0b\u5f0f\u4ecb\u9762"
},
{
"lang": "zh",
"url": "https://zh.wikipedia.org/wiki/%E5%BA%94%E7%94%A8%E7%A8%8B%E5%BA%8F%E6%8E%A5%E5%8F%A3",
"langname": "Chinese",
"autonym": "\u4e2d\u6587",
"*": "\u5e94\u7528\u7a0b\u5e8f\u63a5\u53e3"
}
],
"categories": [],
"links": [
{
"ns": 4,
"*": "Project:Sandbox"
}
],
"templates": [
{
"ns": 4,
"*": "Project:Sandbox"
}
],
"images": [],
"externallinks": [],
"sections": [],
"parsewarnings": [],
"displaytitle": "<span class=\"mw-page-title-main\">API</span>",
"iwlinks": [],
"properties": [
{
"name": "unexpectedUnconnectedPage",
"*": 0
}
]
}
}