I don't see any problem with it. URL or URI should be opaque to their users by definition. in a properly designed and implemented REST interface you are never r

I don't see any problem with it. URL or URI should be opaque to their users by definition. in a properly designed and implemented REST interface you are never required to construct urls, you are just supposed to extract them from responses. As long as URL uniquely identifies a particular "resource" and as long as you properly use the HTTP verb and 'accept hearer' semantics, how the actual urls look like doesn't matter at all