Supercharging ASP.NET Core API with OData

Hassan Habib


In this article, I’m going to show you how you can supercharge your existing ASP.NET Core APIs with OData to provide better experience for your API consumers with only 4 lines of code.

For the purpose of this tutorial please clone our demo project WashingtonSchools so you can follow up and try the different features we are going to talk about in this article.

You can clone the demo project from here:


What is OData?

Let’s talk about OData …

OData is an open source, open protocol technology that provides the ability to API developers to develop Queryable APIs, one of the most common things API developers need is pagination for instance.

With OData you can enable pagination, ordering of data, reshaping and restructuring of the data and much more with only 4 lines of code.

One of the most common scenarios today is when developers call an endpoint and pull out data that they are going to filter, reshape and order later on the client side. This seems a bit wasteful. especially if the data is large enough that could cause latency and require further optimizations for a better user experience.


Getting Started

To get this started, this tutorial assumes you already have an API that provides some list of objects to your end users, for the purpose of this tutorial, we are going to use a sample WashingtonSchools API project that we built to demonstrate this feature.

Our API endpoint api/students returns all the students available in our database.

To enable OData on that endpoint, we are going to need to install a nuget package for all OData binaries that’ll enable us to turn our endpoint into a Queryable endpoint.

The nuget package we are targeting here is:


Once that’s installed, let’s go ahead and add OData services to our API.

To do that, go to: Startup.cs file and add in this line of code in your ConfigureServices Function:


Now we need to enable the dependency injection support for ALL HTTP routes.

To do that, in the same file Startup.cs let’s go to the Configure function and add these two lines of code:

app.UseMvc(routeBuilder => {





The first line of code enables the dependency injection to inject OData services into your existing API controller.

The second line of code determines which OData functionality you would like to enable your API consumers to use, we will talk about Expand, Select and OrderBy in details shortly after we complete the setup of OData on your project.

The last line of code we would want to add is an annotation on top of your API controller method, in our example here, we have a StudentsController class that has a GetStudents method to server all the available students in our database.

Now all we need to do is to add this annotation on top of your GetStudents endpoint as follows:



So your controller method code should look like this:



public IEnumerable<Student> GetStudents(){

       return this.context.Students;


Now that the setup is done, let’s test OData select, OrderBy and expand functionality.



On your favorite API testing software or simply in the browser since this is a GET endpoint, let’s try to select only the properties that we care about from the students objects.

If the students object consists of an ID, Name and we care only about the Name, we could call our endpoint like this:


The results will be a json list of students that only has the Name property displayed. try different combinations such as:


The select functionality enables you to control and reshape the data to fit just your need, it makes a big difference when your objects hold large amounts of data, like image data for instance that you don’t really need for a specific API call, or rich text that is contained within the same object, using select could be a great optimization technique to expedite API calls and response time.



The next functionality here is the OrderBy, which allows you to order your students based on their names alphabetically or their scores, try to hit your endpoint as follows:


You can also do:

api/students?$orderby=Score desc



One other functionality we want to test here is the expand. The expand functionality comes with a great advantage since it allows navigation across multiple entities.

In our example here, Students and Schools are in a many-to-one relationship, we can pull the school every student belongs to by making an expand call like this:


Now we get to see both students and their schools nested within the same list of objects.



The last functionality here is the Filter. Filtering enables you to query for a specific data with a specific value, for instance, If I’m looking for a student with the name Todd, all I have to do is to make an API call as follows:

api/students?$filter=Name eq ‘Todd’

The call will return all students that have the name Todd, you can be more specific with certain properties such as scores. For instance: if I want all students with scores greater than 100, I could make the following API call:

api/students?filter=Score gt 100

There are more features in OData that enables even more powerful API functionality that I urge you to explore such as MaxTop for pagination.


Final Notes

Here are few things to understand about OData:

  1. OData has no dependency whatsoever on the entity framework, it can come in handy with EF but it doesn’t depend on it, here’s a project that runs an OData API without EF:
  2. OData can give you more optimization with EF if you use IQueryable as a data return type that IEnumerable since IQueryable only evaluates after the query is built and ready to be executed.
  3. OData is much older than any other similar technology out there, it was released officially in 2007 and it has been around since then being used in large scale applications such as Microsoft Graph which feeds most of Microsoft Office products and XBOX in addition to Microsoft Windows.


The Future of OData

OData team continues to improve the feature and make it even easier and simpler to use and consume on existing and new APIs with both ASP.NET Web API (classic) or ASP.NET Core and we are working on adding even more powerful features in the near future.


Discussion is closed. Login to edit/delete existing comments.

  • Hector Mota 0

    Hey I didnt know that this actually exists O.o so this is similiar to graphQL. ? Hey thanks for info man

  • Jordan King 0

    Thanks, Hassan, great article(loved the video too on the MS developer channel).  I am going to use .net core and Angular for my next major project.  I would love to see how you would implement api endpoint security. For example, if an admin can select and filter a list of clients vs the same client endpoint secured for a single client so they can only filter/get their own client data.  Do you recommend exposing different endpoints based on security access or can you handle this with the same endpoint?  For context, I am planning on using OpenApi with Swagger/nSwag studio to auto-generate endpoints and typescript classes and possibly fluent Validation as well.

  • Peter St Angelo 0

    I like this technology.  Can I use Odata with CQRS (with MediatR) -if so, are there any examples of it?

    • Hassan HabibMicrosoft employee 0

      Haven’t tried that before, will take a look and let you know.

    • Praneet Nadkar 0

      This seems like a great idea. MediatR with OData! Nice. 

  • Naveed Zafar 0

    Thank you Hassan 

    • Hassan HabibMicrosoft employee 0

      Thank you 🙂

  • zephania Eliah 0

    how can to make odata work with swagger as after implementing Odata over my api swagger specification breaked up

      • Wil Wilder Apaza Bustamante 0

        This comment has been deleted.

    • Saurabh MadanMicrosoft employee 0

      You can also try to use the OData to OpenApi convertor library that the team developed a few months ago. OData is a very rich protocol so representing all aspects of its convention in OpenAPI is not possible. However, we’ve tried to map as many aspects that will allow you to produce a very rich OpenApi description.

      If you already have a swagger spec then you might need to configure some routes so the odata routing does not take over existing routes. You will need to register the routes that you do not wish to process via OData Route handler. 

  • Karthik Giddu 0

    How to use Odata with aspnet core 3.0 Endpoint routing?

    • Daniel Smith 0

      I’d like to know this too.  I get the following in .NET Core 3.0 Preview 4:
      “Using ‘UseMvc’ to configure MVC is not supported while using Endpoint Routing.”

      • Saurabh MadanMicrosoft employee 0

        This is a known issue with OData libraries and we are currently investigating the work that needs to be done. We hope to provide more updates on this work in the coming months. 

  • 华 范 0

    Great Article~!  I was writing hundreds of endpoint methods in my ASP.NET Core project until I saw this article.

    I tried, but it doesn’t work. No matter what I have tried e.g. in PostMan
    the endpoint always returns back the full data rather than a list of titles.

    Btw, I have Swagger in my project. Is it the cause of my problem??

    Please help. Thanks~!

    • Guillermo Acosta 0

      Missing $ after ?{{server}}/api/posts/odata?$select=Title

  • Rajib Mishra 0

    Great atricle. How to generate the Service Metadata document in Atom format?

Feedback usabilla icon