REST API Design: Resources, Versioning, and Auth That Hold Up (Part 2 of 3)
Part 2 of a REST API design series: naming resources so they don't need a manual, versioning without breaking clients, choosing an auth pattern, and structuring errors.
Tagged “versioning”
Hi! Welcome to my blog
Join my newsletter
Distributed systems, .NET, and the tools reshaping how we build them - the trade-offs that don't make it into the docs.
Let's connect
See it on dometrain
See it on dometrain
See it on dometrain
See it on Amazon
See all tags