ASP.NET Web API is a framework for building HTTP services for clients like browsers and mobile devices. It is based on the Microsoft .NET Framework and an ideal choice for building RESTful services.

- Wiki
24 articles, 4 books. Go to books ↓

Versioning of API is very much required if you are providing services for the public. It's the only way we can make our API's supporting forward and backward compatibility. By versioning you don't effect the existing customers and break their applications which depends on your API.

Onee of my favorite features of ASP.NET WebAPI is the opportunity to run your code outside Internet Information Service (IIS). I don’t have anything against IIS, but System.Web is really a problem and, in some cases, IIS pipeline is too complicated for a simple REST call.

The Angular-file-upload directive by nervgh is an awesome lightweight AngularJS directive that handles file upload for you and lets you upload files asynchronously to the server. This article will provide you with a basic understanding of how to upload files using this directive together with the .NET WebAPI service on a SFTP server.

Darrel Miller felt perhaps a bit disillusioned by the sheer number of unnecessary content included in the standard ASP.​NET Web API Template provided by Visual Studio. So he set out to find out what the minimum required files and Nuget packages are to create an ASP.​NET Web API project.

This post will walk you through the step-by-step procedure on building a simple ASP.NET 5 application using AngularJS with Web API.

Routing can be a very tricky issue within ASP.NET MVC and Web API applications. This can be especially true if you have a variety of different routes with varying parameters defined in such a way that a single request could satisfy multiple routes.

Inevitably, if you’re building an API, you’re going to want to monitor requests made to that API. A big step in doing that is logging each API request so that you can capture and determine important information about your endpoints, such as data being sent in, data being returned, how many times endpoints were invoked, and how long it took endpoints to serve their requests.

Cookies can be removed, edited, and faked. Leveraging the HSTS database as a storage mechanism potentially reduces the possibility that your tracking ID will be deleted.

SwaggerUI is more that just documentation - it actually allows developers to make authenticated calls to the API.

Validation is one of the key components in any web app. After all, we should never trust any input to our applications, ever.

Dependency Injection's primary purpose is to separate the implementation from the interface, and allow the system to supply the implementation at a given time. StructureMap (and it's Web API implementation) provide most of the groundwork to do just that.

How to set up an ASP.NET Web API project that uses AutoMapper and StructureMap to provide us with mapping and injection-based repositories and controllers.

Once you have your Web API developed, before exposing it to your clients, based upon your needs you may need to secure some or all parts of your API Service so that only verified users can access your API service. This securing in ASP.NET can be achieved using the authentication and authorization mechanisms.

In order to demonstrate how to combine the power of React, ASP.NET Web API, and Pusher, we’ll be building a realtime chat application.

Learn how providing information in available HTTP header elements can help make interactions between unrelated systems straightforward and meaningful.

Can someone DOS attack your API and bring down your web service? Could I hit your API at 100 requests a second and bring down your server? Or can you throttle your users like this?