3 ms·
HATEOAS is the search term you want to use. “Hypermedia as the engine of application state.” PayPal and GitHub APIs tend to work this way. They return a pile
by empthought 4y ago
HATEOAS is the search term you want to use.
“Hypermedia as the engine of application state.”
PayPal and GitHub APIs tend to work this way. They return a pile of hyperlinks.
- LudwigNagasena 4y agoIf by "tend to work that way" you mean that they satisfy around 20% of the requirements in the post by Roy T. Fielding as opposed to other services that satisfy only 10%...
- empthought 4y agoI don't think you are familiar with the GitHub REST API; none of Fielding's points apply to it.
- LudwigNagasena 4y agoI honestly don’t know how someone can design a truly HATEOAS API without breaking everyone’s expectations and making it a chore for people to deal with it. If stuffing a bunch of links into your JSON response is what truly transforms your RPC into REST (I don’t see what else makes GitHub API so different from other APIs), then I don’t even know what’s the point of that. And surely it is only superficially similar to the non-API REST, ie how simple websites usually work.