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.
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.
Hi! Welcome to my blog
.NET, messaging, and distributed systems - the trade-offs the docs leave out.
Form not loading? Subscribe here.