While the request and response encapsulate your API’s data, URIs provide the path to that data. But different API design patterns use URIs in different ways. In some, the API paths are nothing more than the address all data flows to and from. In others they communicate far more, describing relationships and even aspects about the request.

In this session, we’ll explore those differences, and the friction introduced when APIs aren’t consistent about usage. We’ll also consider some patterns and anti-patterns of URI path structure, and how to define a path structure that’s future friendly.


Comments are closed.

Need more details, understandable there weren't with the allotted time. Otherwise good info.

Good talk, but a little confusing at times. We spent a lot of time on idempotent and safe, which could have been shorter... and a couple aspects on the giant whiteboard seemed a little contradictory until we got there (path is the object, the request is the action, then vice versa; an "OR" on the whiteboard would have helped). But all in all, good, definitely useful and important.