With the current (2.0) REST API, there is no way to translate an URL alias into a location or content.
The locations list resource (/content/locations) already supports filtering on id and remoteId:
It therefore makes sense that the location matching a URL aliases can be looked up the same way:
The resource should behave as it does with the other arguments, or without any arguments, and return a reference to the matching location.
- REST specification update
- Functional tests