Never RESTing – RESTful API Best Practices using ASP.NET Web API
summary
Practical rules and concrete tooling: APIs use ASP.NET Web API and C# with DTOs, AutoMapper and Mediator to keep controllers thin, FluentValidation for separate validators, Swagger for docs, OData for filtering/sorting/paging, and SSL via Let’s Encrypt. Prefer URL versioning, use a small set of HTTP status codes (200/201/400/401/403/404), return structured error arrays with per-field codes and docs links, avoid leaking implementation details, run integration tests before deploys, and prefer OAuth tokens over basic auth.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:53Why create a good API
- 1:53API consumption
- 3:28User experience for devs
- 6:10Simplicity and philosophy
- 7:18What is REST
- 12:03Defining restful APIs
- 13:09Pragmatism in design
- 15:29Design principles
- 17:41Using status codes
- 19:09Avoiding common pitfalls
- 21:34Context and clarity
- 23:30Consistency and verbs
- 26:08Resource relationships
- 29:29Sorting, filtering, paging
- 34:11Versioning strategies
- 36:18Error handling
- 39:13Security best practices
- 42:33ASP.NET implementation
- 45:43Validation techniques
- 48:28Documentation importance
- 50:08Maintenance and testing
- 52:32Q&A and conclusion
related talks
49mAn Opinionated, Maintainable REST API Architecture for ASP.NET Core
52mDesigning and Implementing REST APIs For the Long Haul
01h 01mREST - The ignored parts
42mREST API design good practices
50mWhat every developer should know about REST
01h 18mProfessional Web APIs using ASP.NET Core 2.1
42mLet’s Have Some Effective REST!
51mBuilding Web APIs with ASP.NET Core