Add topic
Active discussions
WikiProject Software / Computing  (Rated Start-class, Low-importance)
WikiProject iconThis article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start This article has been rated as Start-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing.

Perhaps this should be merged into the REST article?

I don't know who wrote the above, but personally I don't agree. However, it should be noted somewhere that the concept is not mentioned in Fielding's thesis. It never occurs at all. After reading the thesis and the article I have no idea where it came from. It's not mentioned in the blog posting referred to, either. --LarsMarius (talk) 21:32, 20 May 2011 (UTC)

The blog post says "What needs to be done to make the REST architectural style clear on the notion that hypertext is a constraint? In other words, if the engine of application state (and hence the API) is not being driven by hypertext, then it cannot be RESTful and cannot be a REST API. Period. Is there some broken manual somewhere that needs to be fixed?" - ok it doesnt use the acronym, but seems pretty clear. I wouldnt have any objection to a merge into REST. Justinc (talk) 11:22, 21 May 2011 (UTC)

Link relations that make up a fixed interfaceEdit

"In this way, RESTful interaction is driven by hypermedia, rather than out-of-band information." The source used to support this statement allows "spend[ing] descriptive effort [...] in defining extended relation names". But wouldn't a set of such "extended relation names" make up "a fixed interface shared through documentation", which the lead says is characteristic of a service-oriented architecture? --Damian Yerrick (talk | stalk) 15:28, 11 July 2012 (UTC)

No; Fielding is saying that REST APIs should present navigational / interface disclosure interactively, and exclusively in-band. A good term paper is self-explanatory, and doesn't need an accompanying oral presentation; a good website explicitly and contextually provides links and functionality to the user, without requiring a separate reference guide. So it is for a HATEOAS-constrained REST API; otherwise you're just using an RPC with an HTTP wrapper. (RPCs, in contrast, are very particular in their usage, and if you don't know exactly what you're doing, you're not going anywhere; hence the documentation.) Razordaze (talk) 22:58, 13 September 2015 (UTC)

2 Cents from some one else -- — Preceding unsigned comment added by (talk) 01:35, 12 January 2014 (UTC) This article appears to bogus. It has next to no sources and does not seem to relate to topics discussed in single referenced source. If their was a mark this as spam article I would.

Example links not idempotentEdit

It seems really poor form to use example links which are flatly wrong usage of HTTP. The possible follow-up links of make a deposit, withdrawal, or transfer, or close the account all change the state of the resource being manipulated, but all include GET-style parameters in the URLs. GET is supposed to be idempotent. (talk) 23:25, 21 May 2018 (UTC)

Verb based resources?Edit

The <link> resource names are verbs. This is counter to RESTful guidelines, is it not? -> Yes, in my opinion this page is corrupted. REST is about resources and not about operations. 2001:8D8:1FE:700:0:0:1:3 (talk) 16:41, 10 June 2015 (UTC)

<link> in this context is not a verb, it's just markup to denote an existing location (noun). The server isn't doing anything when it provides that information; it's not related to the LINK / UNLINK HTTP methods of RFC2068. Here's another source that explains HATEOAS a bit more clearly: Razordaze (talk) 23:16, 13 September 2015 (UTC)
The original point still stands (it wasn't about "link" at all, and the point is backed up by the linked article. "close" in "/accounts/12345/close" is not a noun but a verb, and "deposit" in ""/accounts/12345/deposit" is a verb not a noun, unlike "deposits" in "/accounts/12345/deposits". REST being about resources, nouns, not actions, verbs. would agree (talk) 16:17, 22 April 2022 (UTC)


How is HATEOAS supposed to be pronounced? I always pronounced it HATE-O-AS but I think it should be HAT-E-OAS (rhymes with Adiós?). Found

I don't know but I think it's probably the weirdest looking acronym I've seen. It sounds like Cheerios except with hate instead of cheer. :D — Preceding unsigned comment added by (talk) 20:17, 21 August 2015 (UTC)
I think both HAT-E-OAS and HATE-E-OAS are acceptable pronunciations. I've heard both repeatedly over the years. In fact, at the API Strategy Conference a few weeks ago, I won a box of "Honey Nut HATEOAS" in a contest. There's a picture on my post here: Either way, that makes it an acronym instead of an abbreviation. Caseydk (talk) 07:13, 8 December 2015 (UTC)


Who came up with the acronym - it clearly wasn't necessary to preface it with the word HATE. The minter of that one clearly doesn't realize that the powerfully negative suggestion it carries will kill it dead as people strive to avoid it instinctively. Slashdottir (talk) 17:29, 13 February 2016 (UTC)

That cheered me up, thanks! :) (talk) 09:36, 13 July 2018 (UTC)