How to Implement GET Method in Web API?. The Complete ASP.NET Web API Developer Course 2023 [Videos].

In this Video, I am going to discuss how to Implement GET Method in Web API Application with an example. Please read our previous Video where we discussed Media Type Formatter in Web API with examples. As part of this Video, we are going to discuss the following pointers.

1. Understanding CRUD Operations.
2. Understanding Request Verbs, Request Header, Request Body, Response Body, and Response Status Codes in Web API.
3. Create the database schema in SQL Server with testing data.
4. Using Entity Framework to interact with the database.
5. How to Implement the GET method in ASP.NET Web API?
6. Testing the Web API Get Method using Fiddler.

Understanding CRUD Operations.

In general, when we talk about a database table, there are four operations (known as CRUD Operations) that we perform on it. They are as follows

1. C- Create a Row,
2. R- Read a Row,
3. U- Update a Row, and
4. D- Delete a Row

From the context of an ASP.NET Web API resource, the above four actions (Read, Create, Update and Delete) are corresponded to GET, POST, PUT and DELETE methods respectively. Let us understand some concepts which are required to understand the HTTP verbs.

Request Verbs (GET, POST, AND DELETE)

These describe what should be done with the resource.

Request Header

When a client sends a request to the server, the request contains a header and a body. The request method contains additional information, such as – what type of response is required. For example, The response should be in XML, JSON, or some other format.

Request Body

The request body contains the data that we want to send to the server. For example, a post request contains the data for a new item that we want to create. The data format may be in XML or in JSON

Response Body

The response body contains the data of the response from the server. For example, if the request is for a specific employee, the response body includes employee details in XML, JSON, and so on.

Response Status Codes

The Response Status codes are nothing but the HTTP status codes which specifically gives the status of the response to the client. Some of the common status codes are 404 not found, 200 OK, 204 No content, 500 Internal Server Error and so on.

Use the below SQL Script to create and populate the necessary database table with some test data. The below script

1. Create a database called WEBAPI_DB
2. Creates the Employees table and populate it with some test data

Fetch the records: SELECT * FROM Employees Will give the following result

Creating a new ASP.NET Web API Project

Open Visual Studio and select File – New – Project as shown below

From the “New Project” window, from the left pane select the “Visual C#” which is under the “Installed – Templates” section. Similarly, from the middle pane select ASP.NET Web Application and then provide the name of the project as “EmployeeService“. Finally, click on the “OK” button as shown in the image below.

Once we click on the OK button a new dialog will pop up with Name “New ASP.NET Project” for selecting project Templates.

In this dialog, we are going to choose the Web API project template and click on the OK button. At this point, you should have the Web API project created.

Adding ADO.NET Entity Data Model to retrieve data from the database

Right-click on the Models folder and then select Add – New Item option which will open the Add New Item window and from the “Add New Item” window select the “Data” option from the left pane and from the middle pane select ADO.NET Entity Data Model. In the Name text box, type EmployeeDataModel and finally click the Add button as shown in the below image.

Once you click on the Add button, it will open the Entity Data Model Wizard and from that wizard select “EF Designer from database” option and click on the “Next” button as shown below.

On the next screen, click on the “New Connection” button as shown in the image below

Once you click on the New Connection Button it will open the Connection Properties window. On “Connection Properties” window, set

1. Server Name = provide the server name
2. Authentication = Select the authentication type
3. Select or enter a database name = WEBAPI_DB
4. Click the OK button as shown below.

Once you click on the OK button it will navigate back to the Choose Your Data Connection wizard. Here Modify the Connection String as EmployeeDBContext and click on the Next Button as shown in the below image.

On the next screen, select Entity Framework 6.x as shown in the below image. This step may be optional if you are using a higher version of visual studio.

On Choose Your Database Objects and Settings screen, select the “Employees” table, provide the model namespace name and click on Finish button as shown below. 

Once you click on the Finish Button the following edmx file will be generated within the Models folder as shown below.

Adding Web API Controller

Right-click on the Controllers folder and select Add – Controller option and then select “Web API 2 Controller – Empty” and click on the “Add” button as shown below.

On the next screen set, the Controller Name as EmployeesController and click on the Add button as shown in the below image.

Implementing the GET method in ASP.NET Web API:

Copy and paste the following code in EmployeesController.cs

At this point when we navigate to /api/employees we should see all employees and when we navigate to /api/employees/1 we should see all the details of the employee whose Id=1

We have two get methods one without parameter and one with a parameter. Whenever we pass the id parameter then it will return the employee whose id we passed and if we do not pass the id parameter value then it will return all the employees.

Lets see what will happen when we issue a request for an employee whose id that does not exist with one example.

Here we are trying to get the details of an employee whose id does not exist in the database. So when we click on the execute button it will give us the below response.

The above image clearly shows that we get null as the response and the status code is 200 OK. According to the standards of REST when an item is not found, then it should return 404 Not Found.

To achieve this, we need to modify the Employees Controller as shown below. 

At this point, when we issue a request for an employee with ID = 15 which does not exist we get a 404 along with the message “Employee with Id 15 not found” as shown below.