To Create An Evolvable API, Stop Thinking About URLs

The author argues that evolvable APIs should be designed as conversations, not fixed URLs. By using a uniform interface where the server controls actions, URLs, and methods, state is stored in the network. The client only needs an entry point and interprets server responses to fill required fields, allowing business changes without breaking clients. This approach avoids versioning and reduces coupling, illustrated with a clinic booking example.