Talk:Web API

'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)

Convert to a Wikipedia:Disambiguation page?

The article seems to synthesise loosely related concepts described elsewhere:

• various browser client-side JavaScript APIs
• Mozilla's WebAPIs specifically, which are now indistiguishable from the above ()
• Single-page_application#JavaScript_frameworks' APIs (in the lead only)
• a concept of client-server APIs using HTTP as a transport (which is better and sufficiently described in API#Web_APIs). Abovementioned GraphQL would fall here as well, but the article doesn't mention it or a bunch of other related technologies like XML-RPC, WebSockets etc
• HTTP URLs ('Endpoints')
• Web widgets without naming them ('Growth and impact', second paragraph)

I cleaned up some of the more obvious original research, but I'm not convinced that 'web API' refers to a distinct concept (other than being used in a dictionary sense, simply meaning an API used on web) in a way that can be described encyclopaedically without resulting in a WP:COATRACK article. PaulT2022 (talk) 14:19, 10 August 2026 (UTC)