Comments on: URL Design for RESTful Web Services /2013/04/03/url-design-restful-web-services/?utm_source=rss&utm_medium=rss&utm_campaign=url-design-restful-web-services Everything about API User Experience Tue, 24 May 2016 12:38:58 +0000 hourly 1 https://wordpress.org/?v=5.8.6 By: URL Design for RESTful Web Services | AddThis Blog /2013/04/03/url-design-restful-web-services/#comment-11735 Tue, 24 May 2016 12:38:58 +0000 /?p=233#comment-11735 […] Engineering, Charlie Reverte, posted today at APIUX.com. To read the rest of the blog post, click here to go over to their […]

]]> By: Harry McIntyre (@mcintyre321) /2013/04/03/url-design-restful-web-services/#comment-313 Mon, 16 Dec 2013 21:39:01 +0000 /?p=233#comment-313 http://hadihariri.com/2013/07/29/one-step-guide-on-designing-a-rest-api/

]]> By: Charlie Reverte /2013/04/03/url-design-restful-web-services/#comment-229 Thu, 01 Aug 2013 00:29:56 +0000 /?p=233#comment-229 In reply to Gerson Goulart.

done!

]]> By: Gerson Goulart /2013/04/03/url-design-restful-web-services/#comment-222 Tue, 30 Jul 2013 17:00:59 +0000 /?p=233#comment-222 In reply to Charlie Reverte.

Maybe it would be a good idea to fix the article than, not everyone will read every single comment… Other than that, thanks for the really good post.

]]> By: Review: Google Glass API | API UX /2013/04/03/url-design-restful-web-services/#comment-67 Wed, 17 Apr 2013 16:01:29 +0000 /?p=233#comment-67 […] doesn’t need that you run any code on Glass itself, since all interactions are done via RESTful […]

]]> By: Charlie Reverte /2013/04/03/url-design-restful-web-services/#comment-63 Tue, 16 Apr 2013 03:28:23 +0000 /?p=233#comment-63 In reply to mahemoff.

Ah, good catch. PUT /users/charlie is what I meant to say, error on my part 🙂

]]> By: mahemoff /2013/04/03/url-design-restful-web-services/#comment-51 Mon, 08 Apr 2013 00:15:27 +0000 /?p=233#comment-51 I think POST /users/charlie should be a PUT (more bikeshedding).

Creation can happen by either POSTING to the generic resource /users or PUTting to a specific instance (if it’s allowed for the client to name the resource, as you point out).

]]> By: URL Design for RESTful Web Services | Output Translation /2013/04/03/url-design-restful-web-services/#comment-50 Sun, 07 Apr 2013 12:43:31 +0000 /?p=233#comment-50 […] is a cross-post of a guest post I did for APIUX.  Click here for the […]

]]> By: Adrien Risser /2013/04/03/url-design-restful-web-services/#comment-47 Thu, 04 Apr 2013 08:38:11 +0000 /?p=233#comment-47 What about the best URL designed in REST as is “/”?
API URLs don’t matter when everything is hyperlinked.
(As in a Website, who likes to type every single page link in the browser?)

]]> By: Charlie Reverte /2013/04/03/url-design-restful-web-services/#comment-46 Wed, 03 Apr 2013 21:00:19 +0000 /?p=233#comment-46 In reply to Pete Johanson.

In terms of the API user experience it’s pretty sweet to be able to link users to actual calls from within your online docs. If you have good linking between your endpoints you can do a fair bit of navigation around the API in your browser before you need to reach for curl or fancier clients. It makes for a better first impression which improves the likelihood that someone will implement.

]]>