Click here to Skip to main content
15,113,086 members
Articles / Web Development / ASP.NET
Posted 1 May 2013


80 bookmarked

Using ASP.Net WebAPI with Web Forms

Rate me:
Please Sign up or sign in to vote.
4.78/5 (35 votes)
22 Jun 2013CPOL8 min read
Asp.Net WebAPI is a framework for building RESTful HTTP services which can be used across a wide range of clients including web, phone and desktop applications. With WebAPI we can use XML and JSON to send and retrieve data from the service. The use of Json or XML makes it quite flexible to be used [

Asp.Net WebAPI is a framework for building RESTful HTTP services which can be used across a wide range of clients including web, phone and desktop applications. With WebAPI we can use XML and JSON to send and retrieve data from the service. The use of Json or XML makes it quite flexible to be used across a variety of devices. 

Although WebAPI ships and installs with ASP.Net MVC 4, it can be used in normal Web Forms application as well.

In this example, we will use WebAPI with a traditional Web Forms application for adding and displaying a list of User Information. We will be using Visual Studio 2012 and .Net 4.5. 

Creating the Project

Open Visual Studio 2012, Go To New -> Project. Select Visual C# -> Web from the left hand navigation and select project type as ASP.Net Web Forms Application. Enter the project name as WebAPIDemo

A new project will be created with a default template and our solution will show the following structure

Adding Model Class

We will then add a Model Class to our project. The Model class will represent the data in our application. We will add a model class called Users in our project

Right Click the Project in the Solution Explorer, Select Add -> Class from the Context Menu. The name of the class will be “Users” and it will have the following properties

namespace WebAPIDemo
    public class Users
        public int Id { get; set; }
        public string FirstName { get; set; }
        public string LastName { get; set; }
        public string Company { get; set; }
        public string Email { get; set; }
        public string PhoneNo { get; set; }

The WebAPI can automatically serialize the model as JSON or XML object and will write the data in the body of the HTTP response. If the clients can read the serialize data, they will be able to deserialize it. Most of the clients are able to read the XML or JSON data. The clients can also specify the format it wants by setting the “Accept Header” property in the request message.

Creating The Repository

Ideally in a production scenario, we should be storing our data in some sort of persistent storage like database but to keep this demo simple, we will storing it in local memory.

To keep our storage implementation separate from the application code, we will be using Repository pattern. This way we can change our storage implementation at any future data without many changes to the application code.

We will start by creating a generic repository interface. Add a new class to the project and call it “IUserRepository”. It will have the following code

namespace WebAPIDemo
    public interface IUserRepository
        IEnumerable<Users> GetAllUsers();
        string AddUser(Users user);
        Users GetUserById(int id);
        void DeleteUser(int id);

The “GetAllUsers” function return a list of the all the users. The “AddUser” function will add a new user and “GetUserById” will return a particular user based on the id that has been passed.

Add a Class to the solution called “UserRepository”. The class will implement the “IUserRepository” and will have the following implementation.

namespace WebAPIDemo
    public class UserRepository : IUserRepository
        private List<Users> userList = new List<Users>();
        private int _id = 3;
        public UserRepository()
 userList.Add(new Users { Id = 1, FirstName = "Madhur", LastName = "Kapoor", Company = "ABC", Email = "", PhoneNo = "65431546" });
userList.Add(new Users { Id = 2, FirstName = "Alan", LastName = "Wake", Company = "XYZ Corp", Email = "", PhoneNo = "64649879" });
        public IEnumerable<Users> GetAllUsers()
            return userList;
        public string AddUser(Users user)
            user.Id = _id++;
            return "User added";
        public Users GetUserById(int id)
            var user = userList.FirstOrDefault<Users>((p) => p.Id == id);
            if (user == null)
                throw new HttpResponseException(HttpStatusCode.NotFound);
            return user;
        public void DeleteUser(int id)
            var user = userList.FirstOrDefault<users>((p) => p.Id == id);

            if (user == null)
                throw new HttpResponseException(HttpStatusCode.NotFound);


In the class, we are using a local variable “userList” to store all the users. In the constructor, we are adding a few records to the list.

The “AddUser” function adds a new user to the list with a new Id.

The “GetUserByID” function uses a LINQ query to return the user with the specified id. If the user is not found, an HTTPResponseException is thrown which is interpreted by browser as “404” error.

You will need to add a reference to the “System.Web.Http” for the HttpResponseException class to work.

Creating The WebAPI Controller

We will now add a WebAPI controller to the solution. A WebAPI controller is a class that handles the HTTP request by the clients. WebAPI Controllers are similar to MVC Controllers except they derive from “ApiController” class instead of “Controller” class.

Right Click the solution, select Add -> Web API Controller Class. Name the Controller class as “UserController”.

The controller class will have some default function for Get, Put, Delete etc. Delete those functions and add the following functions so the code will look like below.

namespace WebAPIDemo
    public class UserController : ApiController
        static IUserRepository repository = new UserRepository();

        public IEnumerable&lt;Users&gt; GetAllUsers()
            var users = repository.GetAllUsers();
            return users;

        public Users GetUserById(int id)
            var user = repository.GetUserById(id);
            return user;
        public string AddUser(Users user)
        {  var response = repository.AddUser(user);
            return response;
        public void DeleteUser(int id)

Adding Route in Global.asax

For the controller to handle requests of a particular type, we will have to define a route in the Global.asax file.

Open global.asax file and add the following code in the “Application_Start” method

            name: "DefaultApi",
            routeTemplate: "api/{controller}/{id}",
            defaults: new { id = System.Web.Http.RouteParameter.Optional }

The controller will now be able to handle request of type “api/User/”

Testing The WebAPI

We will now Test our WebAPI by running it in the browser. Run the Web Application by pressing “Ctrl + F5” or going to “Debug -> Start Debugging” from the Visual Studio menu.

On running the application, the “Default.aspx” page will open. The URL will be something like http://localhost:56851/Default.aspx where 56851 will be port number.

To Test the WebAPI,  we will have to use the URL as defined in the Route. Enter the following URL in the browser http://localhost:56851/api/User/ (Replace 56851 with your port number)

The result will depend upon the type of browser you are using. In Internet Explorer, you will be prompted to save a file named “User”.

The file contains the Http response. Select “Open” and in the “Open with” dialog, select “Notepad” to open the file.

The Notepad will show the data in the JSON format which has been returned by the WebAPI.

[{"Id":1,"FirstName":"Madhur","LastName":"Kapoor","Company":"ABC","Email":"","PhoneNo":"65431546"},{"Id":1,"FirstName":"Alan","LastName":"Wake","Company":"XYZ Corp","Email":"","PhoneNo":"64649879"}]

If you are using Chrome or Firefox, you are likely to get a XML representation of the data. This is because Internet Explorer and Firefox send different “Accept Header” with the request and so the WebAPI returns different content type.

If you are using Internet Explorer with Developer tools, you can check the Request header that is being sent by the browser.

Just Open the Developer tools by pressing F12, go to network option and Enable “Start Capturing” and then with developer tools open, enter the WebAPI URL in the browser and press enter

If you use the following URL “ http://localhost:56851/api/User/1 (Replace 56851 with your port number)”

It will return the user whose ID is ‘1’. Typing an ID that does not exist will result in a “Page Not Found” error.

Calling WebAPI with JQuery

Now we will call the WebAPI using JQuery and will display the result in a web page.

In the “Default.aspx” file, we will use the following code for the body section to display the data

<asp:Content runat="server" ID="BodyContent" ContentPlaceHolderID="MainContent">
<h2>My Address Book</h2>
    <br />
                <td>Full Name</td>
        <tbody id="usersection">
    <br />
    <br />
        <h2> Add A Contact</h2>
            <td>First Name</td>
                <asp:TextBox runat="server" ID="txtFirstName" /></td>
            <td>Last Name</td>
                <asp:TextBox runat="server" ID="txtLastName" /></td>
                <asp:TextBox runat="server" ID="txtCompany" /></td>
                <asp:TextBox runat="server" ID="txtPhone" /></td>
                <asp:TextBox runat="server" ID="txtEmail" /></td>
                <asp:Button Text="Save" runat="server" ID="btnSave"  />
    <br />
    <br />
    <asp:TextBox ID="txtSearch" runat="server"  />
    <asp:Button ID="btnSearch" runat="server" Text="Search" OnClientClick="search();return false;" />
    <br />
    <br />
    <p id="searchResult" >
<br />
    <br />
    <asp:TextBox ID="txtDelete" runat="server"  />
    <asp:Button ID="btnDelete" runat="server" Text="Delete" OnClientClick="deleteuser();return false;" />

Include a reference to JQuery in your project in the head section

<script src="Scripts/jquery-1.7.1.js" type="text/javascript"></script> 

Getting list Of Users

To get a list of users, we will send a Get Request to the “api/User”

$(document).ready(function () {
            $.getJSON("api/User", function (data) {
                $.each(data, function (key, val) {
                    var row = "<tr><td>" + val.Id + "</td><td>" + val.LastName + ", " + val.FirstName + "</td><td>" + val.Company +
                        "</td><td>" + val.PhoneNo + "</td><td>" + val.Email + "</td></tr>";

We use the “getJSON” JQuery function to send the GET Request specifying the URL. The second parameter is the callback function which will be called once the request is completed successfully. The “data” object will contains a list of JSON or XML objects which will be returned by the service.

Once we get the “data” from the API, we are iterating through the data and appending it to the body section of the table.

The “getJSON” function is called in the “document.ready” function so that it executed immediately when the page executes. On running the application now, you will get the following page

The default records which we added are displayed

Adding a User

We will now add a user using a Post Request using JQuery Ajax. As you can see, we have already created a form for entering the data. Once the save button is clicked, the following function is called

function insertData() {
            var Emp = {};
            Emp.FirstName = $("#<%=txtFirstName.ClientID %>").val();
            Emp.LastName = $("#<%=txtLastName.ClientID %>").val();
            Emp.PhoneNo = $("#<%=txtPhone.ClientID %>").val();
            Emp.Company = $("#<%=txtCompany.ClientID %>").val();
            Emp.Email = $("#<%=txtEmail.ClientID %>").val();
                url: "<%=Page.ResolveUrl("/api/User/AddUser")%>",
                type: "POST",
                contentType: "application/json;charset=utf-8",
                data: JSON.stringify(Emp),
                dataType: "json",
                success: function (response) {
                error: function (x, e) {

We are using the “ajax” method of JQuery to send a POST request to the the “api/User/AddUser” URL. As the “AddUser” function expects an object of type “User”, we create a JSON object and pass it with the request. The “success” function will be called if the request is successful and the response will be shown. In case of any error, the “error” function will be called.

Try adding a User. If everything is successful, you will get the following response. (Note: Ideally there should be validation on user input, for keeping the tutorial simple, I have not added any validation)

On Clicking Ok, the list will be updated and the new added user will be visible

Adding Search Function

To get a User by ID, we will call the “api/User/Id” passing the id of the user we want to display.

The code which is going to get called on Search button click will be

function search() {
    var id = $('#<%=txtSearch.ClientID %>').val();
    $.getJSON("api/User/" + id,
        function (data) {
            var str = data.Id + ' - ' + data.LastName + ", " + data.FirstName + " - " + data.Company;
        function (jqXHR, textStatus, err) {
            $('#searchResult').text('Error: ' + err);

We call the Jquery “getJSON” function but this time we are passing the ID with the URL and the API will return a single JSON object if the User is found.

If no user exists with the ID, we will get an error as shown below

Adding Delete Functionality  

To Delete the User, we will call the "api/User/id" and we will pass the id of the user which we want to delete. This time we will call the function using the Delete Http verb.

Here is the function which is getting called on Delete button click 

 function deleteuser() {
            var id = $('#<%=txtDelete.ClientID %>').val();
                url: "<%=Page.ResolveUrl("/api/User/")%>" + id,
                  type: "DELETE",
                  contentType: "application/json;charset=utf-8",
                  success: function (response) {

                      alert("User Deleted");

                  error: function (x, e) {
                      alert("Id Not Found");


If the id is not found, a 404 exception will be raised else the user will be deleted.

The Complete Code for the Default.aspx file can be found in the attached solution

We can also add the Update functionality to the application in similar manner. WebAPI can be used with Asp.Net MVC in a similar fashion.

Do leave your feedback and issues in the comments.

Download Solution


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Madhur Kapoor
Technical Lead Infosys
India India
Madhur is Technology Lead by profession having around 9+ yrs of experience in IT industry working on Microsoft Technologies. Apart from Microsoft Technologies, he also likes to work on Mobile Development in Android.

His Technical expertise include .Net technologies including MVC, WebAPI, Azure.

Apart from coding, he like to play Xbox Games, strum guitar or read books.

My Blog :

Comments and Discussions

Question404 on IIS Pin
alinciurea29-Nov-16 4:17
Memberalinciurea29-Nov-16 4:17 
AnswerRe: 404 on IIS Pin
Madhur Kapoor30-Nov-16 19:45
MemberMadhur Kapoor30-Nov-16 19:45 
GeneralRe: 404 on IIS Pin
alinciurea22-Dec-16 1:40
Memberalinciurea22-Dec-16 1:40 
QuestionUpdate Your profile Pin
barodaexpress18-Oct-15 9:30
Memberbarodaexpress18-Oct-15 9:30 
Questionmy address book didn't show the already stored data Pin
mojojojojopow14-Oct-15 22:12
Membermojojojojopow14-Oct-15 22:12 
GeneralVery nicely explained Pin
Vamsi Pulavarthi29-Aug-15 8:32
professionalVamsi Pulavarthi29-Aug-15 8:32 
Questionweb api Pin
GopalSamy J8-May-15 0:52
MemberGopalSamy J8-May-15 0:52 
QuestionHow to generate the Web API help for this? Pin
Tweetyshwet9-Mar-15 3:51
MemberTweetyshwet9-Mar-15 3:51 
QuestionHow does it work? Pin
Dennis Sivtsov6-Dec-14 7:54
MemberDennis Sivtsov6-Dec-14 7:54 
AnswerRe: How does it work? Pin
Bistra Hristova28-May-15 4:22
MemberBistra Hristova28-May-15 4:22 
Question[My vote of 1] The mapping of functions to controllers are not explained. Pin
Janilane21-Oct-14 18:31
MemberJanilane21-Oct-14 18:31 
AnswerRe: [My vote of 1] The mapping of functions to controllers are not explained. Pin
Leo Fajardo20-Aug-15 6:00
MemberLeo Fajardo20-Aug-15 6:00 
QuestionError missing System.Web.Http reference Pin
bruceshining21-Aug-14 11:50
Memberbruceshining21-Aug-14 11:50 
AnswerRe: Error missing System.Web.Http reference Pin
Bistra Hristova27-May-15 6:10
MemberBistra Hristova27-May-15 6:10 
QuestionHow to bind dropdown list Pin
demouser7431-Jul-14 23:23
Memberdemouser7431-Jul-14 23:23 
QuestionEdit Data Pin
demouser7431-Jul-14 4:04
Memberdemouser7431-Jul-14 4:04 
QuestionValidation Pin
demouser7431-Jul-14 1:29
Memberdemouser7431-Jul-14 1:29 
AnswerRe: Validation Pin
Madhur Kapoor1-Jul-14 7:05
MemberMadhur Kapoor1-Jul-14 7:05 
QuestionSecurity Pin
Neetflash17-Dec-13 2:52
MemberNeetflash17-Dec-13 2:52 
AnswerRe: Security Pin
Madhur Kapoor18-Dec-13 20:41
MemberMadhur Kapoor18-Dec-13 20:41 
GeneralMy vote of 3 Pin
afeera azeez23-Aug-13 3:57
Memberafeera azeez23-Aug-13 3:57 
QuestionGlad I found this post Pin
Thomas Kopp23-Jul-13 10:32
MemberThomas Kopp23-Jul-13 10:32 
GeneralMy vote of 4 Pin
Ashutosh Phoujdar25-Jun-13 4:11
MemberAshutosh Phoujdar25-Jun-13 4:11 
Thanks for sharing!!!
It is very crisp and concise. Congratulations to you.
GeneralVote of 5 Pin
Gonzalo F.25-Jun-13 0:42
MemberGonzalo F.25-Jun-13 0:42 
QuestionThanks Pin
HariPrasad katakam23-Jun-13 22:55
MemberHariPrasad katakam23-Jun-13 22:55 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.