Talk:Web API

Redirect
I think that this should not redirect to API, since Web APIs are an important topic on their own. Nor should it redirect to the possible synonym Web Services, since the current article defines Web Services as using WSDL and SOAP, and thusly defined Web API is not synonymous with Web Service, since not all Web APIs use these technologies. So in short I think that this should become an article. Boyprose (talk) 00:33, 17 September 2009 (UTC)


 * It occurs to me that this article might better be called API (web). Any comments? Boyprose (talk) 01:40, 17 September 2009 (UTC)


 * I disagree. Its naming is inline with many other articles such as web browser, web service, web cache, etc. 50.53.15.59 (talk) 15:21, 7 March 2013 (UTC)


 * However browser, service and cache are not acronyms. I've added a redirect from API (web) and others, anyway. --Nemo 11:02, 4 April 2013 (UTC)

I believe that this concept is different enough from that of Web API to merit its own page. To me, web API implies a series of specified parameters that a developer uses to store/retrieve data from the back end or manipulate data and objects from the front end. Webhooks seem like more of a way to check for errors through verification processes, or to ensure that data stays 'fresh' 75.182.97.223 (talk) 20:15, 27 December 2013 (UTC)

Space
Web API, WebAPI or Web-API? I found all of them in use. --Nemo 07:55, 12 February 2013 (UTC)


 * I believe the current "web API" is sufficient and its naming is inline with other similar articles. If you want to add redirects named such, that could be useful. 50.53.15.59 (talk) 15:21, 7 March 2013 (UTC)


 * I've moved it because WebAPI was a pseudo-duplicate and had a source for the name itself. --Nemo 11:00, 4 April 2013 (UTC)


 * Actually it was not a duplicate but a different concept. I reversed the redirect and split the server-side concept from the client-side concept (Mozilla's WebAPI is a project for a set of client-side web APIs--W3C actually defines several of these; this is entirely a different thing from server-side web API and web services). Uzume (talk) 00:01, 5 April 2013 (UTC)


 * I think WebAPI deserves it own page. Despite similar names, WebAPI happens inside the browser without any networking.  Mscdancer (talk) 20:09, 14 June 2018 (UTC)


 * I now think that WebAPI is a misnomer and a better name should be JavaScript API as on the W3C site. Mscdancer (talk) 20:18, 14 June 2018 (UTC)

Empty reference
Re "For the Microsoft ASP.NET Web API, see ASP.NET MVC Framework.":

Article "ASP.NET MVC Framework" does not contain any information about Web API (except for some external references), so why this cross reference? --Mortense (talk) 13:03, 5 September 2015 (UTC)
 * There are many references to "Web API" that really are referring to a specific ASP.NET web application framework so we provide a disambiguation link:
 * http://www.asp.net/web-api
 * https://msdn.microsoft.com/en-us/library/hh833994.aspx
 * Notice ASP.NET Web API redirects to ASP.NET MVC Framework. 50.126.125.240 (talk) 03:51, 30 November 2015 (UTC)
 * I recently moved ASP.NET MVC and in so doing that I realized that ASP.NET Web API is a separate framework from ASP.NET MVC (but both are included as a part of ASP.NET) so I updated the redirect and this article's lead dab hatnote to point to ASP.NET. Uzume (talk) 14:41, 1 December 2015 (UTC)
 * I took the liberty of removing the "For the Microsoft ASP.NET Web API..." block at the top. "ASP.NET Web API" apparently doesn't even rate its own page.  More to the point, I very seriously doubt that a significant percentage of people who land on Web API are really looking for "ASP.NET Web API". However, for those few, so it doesn't get lost completely, I added an entry for it in the "See Also" section. That ought to suffice. 199.116.174.62 (talk) 16:08, 28 July 2016 (UTC)

Clarifai
The following is looking somewhat arbitrary and commercial:

As API providers still want to update their web APIs, many have introduced a versioning system in the URI that points to an endpoint, for example the Clarifai API: The endpoint for the tagging functionality within the web API has the following URI: "https://api.clarifai.com/v1/tag/". The "/v1/" part of the URI specifies access to the first version of the web API. If clarifai decides to update to version two, they can do this while still maintaining support for third party software that uses the first version.

Clarifai doesn't even have its own page yet. I'm in favour of a more generic example. &mdash; MaxEnt 18:52, 17 January 2017 (UTC)

Dilling problem
Story not opening Hero1243 (talk) 19:30, 4 February 2019 (UTC)

Dilling problem Hero1243 (talk) 19:31, 4 February 2019 (UTC)

'Endpoints' section
This section is unclear, and seems just to describe URLs. Is there a reason to keep it? Wootery (talk) 19:02, 21 May 2020 (UTC)

Mention GraphQL
At this point in time, GraphQL seems to be a serious contender. Perhaps it should be mentioned alongside REST? Compsciasaur (talk) 00:05, 18 January 2022 (UTC)