REST-ful URI design best practices | Mike's Random Thoughts |

What are the criteria for a good REST-ful URI?

- Short (as possible). This makes them easy to write down or spell or remember.

- Hackable ‘up the tree’. The user should be able to remove the leaf path and get an expected page back. e.g. you could remove the gt bit and expect to get back all the alfa-romeos.

- Meaningful. Describes the resource. I should have a hint at the type of resource I am looking at (a blog post, or a conversation). Ideally I would have a clue about the actual content of the URI (e.g. a uri like uri-design-essay)

- Predictable. Human-guessable. If your URLs are meaningful they may also be predictable. If your users understand them and can predict what a url for a given resource is then may be able to go ‘straight there’ without having to find a hyperlink on a page. If your URIs are predictable, then your developers will argue less over what should be used for new resource types.


Via Nicolas Weil