8.2 KiB
| title | author | description | manager | ms.author | ms.custom | ms.date | ms.prod | ms.technology | ms.topic | uid |
|---|---|---|---|---|---|---|---|---|---|---|
| Build web APIs with ASP.NET Core | scottaddie | Learn about the features available for building a web API in ASP.NET Core and when it's appropriate to use each feature. | wpickett | scaddie | mvc | 04/24/2018 | aspnet-core | aspnet | article | web-api/index |
Build web APIs with ASP.NET Core
By Scott Addie
View or download sample code (how to download)
This document explains how to build a web API in ASP.NET Core and when it's most appropriate to use each feature.
Derive class from ControllerBase
Inherit from the ControllerBase class in a controller that's intended to serve as a web API. For example:
::: moniker range=">= aspnetcore-2.1" [!code-csharp] ::: moniker-end ::: moniker range="<= aspnetcore-2.0" [!code-csharp] ::: moniker-end
The ControllerBase class provides access to numerous properties and methods. In the preceding example, some such methods include BadRequest and CreatedAtAction. These methods are invoked within action methods to return HTTP 400 and 201 status codes, respectively. The ModelState property, also provided by ControllerBase, is accessed to perform request model validation.
::: moniker range=">= aspnetcore-2.1"
Annotate class with ApiControllerAttribute
ASP.NET Core 2.1 introduces the [ApiController] attribute to denote a web API controller class. For example:
This attribute is commonly coupled with ControllerBase to gain access to useful methods and properties. ControllerBase provides access to methods such as NotFound and File.
Another approach is to create a custom base controller class annotated with the [ApiController] attribute:
The following sections describe convenience features added by the attribute.
Automatic HTTP 400 responses
Validation errors automatically trigger an HTTP 400 response. The following code becomes unnecessary in your actions:
This default behavior is disabled with the following code in Startup.ConfigureServices:
Binding source parameter inference
A binding source attribute defines the location at which an action parameter's value is found. The following binding source attributes exist:
| Attribute | Binding source |
|---|---|
| [FromBody] | Request body |
| [FromForm] | Form data in the request body |
| [FromHeader] | Request header |
| [FromQuery] | Request query string parameter |
| [FromRoute] | Route data from the current request |
| [FromServices] | The request service injected as an action parameter |
[!NOTE] Do not use
[FromRoute]when values might contain%2f(that is/) because%2fwon't be unescaped to/. Use[FromQuery]if the value might contain%2f.
Without the [ApiController] attribute, binding source attributes are explicitly defined. In the following example, the [FromQuery] attribute indicates that the discontinuedOnly parameter value is provided in the request URL's query string:
Inference rules are applied for the default data sources of action parameters. These rules configure the binding sources you're otherwise likely to manually apply to the action parameters. The binding source attributes behave as follows:
- [FromBody] is inferred for complex type parameters. An exception to this rule is any complex, built-in type with a special meaning, such as IFormCollection and CancellationToken. The binding source inference code ignores those special types. When an action has more than one parameter explicitly specified (via
[FromBody]) or inferred as bound from the request body, an exception is thrown. For example, the following action signatures cause an exception:
- [FromForm] is inferred for action parameters of type IFormFile and IFormFileCollection. It's not inferred for any simple or user-defined types.
- [FromRoute] is inferred for any action parameter name matching a parameter in the route template. When multiple routes match an action parameter, any route value is considered
[FromRoute]. - [FromQuery] is inferred for any other action parameters.
The default inference rules are disabled with the following code in Startup.ConfigureServices:
Multipart/form-data request inference
When an action parameter is annotated with the [FromForm] attribute, the multipart/form-data request content type is inferred.
The default behavior is disabled with the following code in Startup.ConfigureServices:
Attribute routing requirement
Attribute routing becomes a requirement. For example:
Actions are inaccessible via conventional routes defined in UseMvc or by UseMvcWithDefaultRoute in Startup.Configure. ::: moniker-end