What would you call an API that is HTTP-based, uses URI to name resources and HTTP verbs (PUT, POST, DELETE, GET...) to manipulate those resources? According to Roy Fielding's complaints it is not REST, because there is no hypermedia.Internally, in my team, everyone calls it REST API. I call it REST-like but it is not descriptive and its meaning is fuzzy. I'm quite confused about it, since there is huge disagreement about REST. I don't want take part in flame wars, but just use correct terms.
What to call an HTTP API that is not RESTful?
terminology;rest;api;http