Your REST API should come with a client

Re:Your REST API should come with a client by MichaelGG on Monday April 28, 2014 @03:51AM (#7658730)

Is Twilio really rest? Versioning and formatting info in URLs isn't REST-like. Plus the docs suggest you construct URLs, which isn't RESTful.

I love Twilio's API, I just don't understand the REST part. I fail to see how "PATCH /accounts/123/ <postbody>" is better than "POST /accounts/updateaccount <postbody accountid=123 ...>", especially when hidden behind a lovely client.

[ Parent | on HN ]

Re:Your REST API should come with a client by cordite on Monday April 28, 2014 @05:48AM (#7659006)

It seems they try to provide a somewhat hypermedia oriented API.

What I really don't like is they don't accept my accept headers, and I have to change the extension on the end. Going to /.json feels like ilk to me.

[ Parent | on HN ]

Re:Your REST API should come with a client by darrelmiller on Monday April 28, 2014 @08:10PM (#7664001)

For some additional insight on accept based conneg. The guys who created it, really wish they hadn't.

http://www.alvestrand.no/pipermail/ietf-types/2006-April/001...

"Regarding proactive negotiation in HTTP/2, I'll note that Waka strips all negotiation fields. I find the entire feature revolting, from every architectural perspective, and would take the opportunity of 2.x to remove it entirely." Roy Fielding http://lists.w3.org/Archives/Public/ietf-http-wg/2013JanMar/...

[ Parent | on HN ]