Building a RESTful API is very different from building just an API. In this course, Building a RESTful API with ASP.NET Core, you'll learn how to build an API that fits the REST architectural style, with ASP.NET Core 1 or 2. That implies that the API should adhere to the constraints enforced by the REST architectural style. First, you'll look into how you can correctly interact with your API by using the correct HTTP methods and status codes. Next, you'll explore validation, logging, and common functionality RESTful APIs. Then, you'll discover how to correctly use media types, and will look into versioning, caching, and handling concurrency. Finally, you'll learn protecting and documenting the API. By the end of this course, you'll have built an API with level 3 maturity, which is the highest possible level of APIs.
Hi, I'm Kevin. Welcome to this Pluralsight course: Building a RESTful API with ASP.NET Core. I'm a solution architect focused on APIs and security, and a Microsoft MVP.
Building an API is one thing. Building a RESTful API is something different. In this course, you'll learn how to do that with ASP.NET Core.
We'll look into how we can correctly interact with our API by using the correct http methods & status codes: getting, updating, creating and deleting resources. Learning about method safety and idempotency will help us choose the correct approach for these different use cases. We'll also look into some less-obvious cases and principles, like creating a list of resources in one go, and upserting.
We'll cover validation and logging as well, as when we're creating or updating something, we want to ensure the input is valid, and if it isn't, log that.
We'll also cover common functionality RESTful APIs expose these days, like paging, sorting, filtering, data shaping and so on.
But we won't stop there. We're going to ensure our API is HATEOAS-enabled, so hypermedia will drive application state. It's one of those constraints a RESTful architecture has that tends to separate truly RESTful APIs from run-of-the-mill web APIs.
We'll also learn how to correctly use media types, and we'll look into versioning, caching and handling concurrency.
We'll end with a module on protecting & documenting the API.
In the end, we'll have built an API with level 3 maturity, which is the highest possible level for APIs.