Skip to main content

How to define a REST service with pagination support - Part 2

Part 1:
Part 2:
In this post we will see how we can implement using ApiController, a REST service that expose a list of items using pagination.
In the previous post related to this subject we define the REST API for pagination. We saw how important is for clients to has all the information directly in the message itself. For example the next page URL should be send by the service, not constructs by the clients.
The below example contains the request and response of our REST service.
GET /api/cars?pageNumber=3&pageSize=20

Get items from database
Let’s assume that we are using Entity Framework to fetch data from database. To be able to get only the items that we need for the requested page we will need to use a LINQ expression that contains

  • Skip – to get only the items starting from a specific location
  • Take – take only the items that are needed for the current page

Unfortunately, Skip and Take commands can be used only in combination with OrderBy. Because of this we will need to call and apply an order by before each query. This is needed because this is the only way how EF can guarantee that the items that are returned are the expected one (items from database are not orders).
List<Car> entities = carSet
                                        .OrderBy(x => x.Id)
                                        .Skip((pageNumber - 1) * pageSize)
On top of this we will need to get the total number of items. For this we will to make another query that retrieves the total available items.
int totalItems = carSet.Count();
Generate response
The response from the repository can we wrapped  in a class that extends List<T> and has a property with all the information related to pagination (page number, size, items count).
public class Page<TItem> : List<TItem>
    public Page()

    public Page(IEnumerable<TItem> collection, Paging paging)
        : base(collection)
        Paging = paging;

    public Paging Paging { get; set; }
Class that contains all the information related to pagination:
public class Paging
    public int PageNumber { get; set; }

    public int PageSize { get; set; }

    public int TotalPages { get; set; }

    public int TotalItemsCount { get; set; }

    public bool HasNext
            return TotalPages > PageNumber;

    public bool HasPrev
            return PageNumber > 1 && PageNumber <= TotalPages;
Next we will need to use a dynamic object to generate the response message that contains all the necessary information.
public class PaginationUtility
    private const string PageNumberQueryName = "page";
    private const string PageSizeQueryName = "pageSize";
    private const string ErrorMessageForInvalidPage = "This page don't exist.";

    public HttpResponseMessage CreateResponseMessageForPaginaionRequests<TEntity>(Page<TEntity> requestedPage,
        HttpRequestMessage request)
        dynamic bodyMessage = CreateResponseBody(requestedPage, request);

        HttpResponseMessage responseMessage = requestedPage.Count == 0 ||
                                                requestedPage.Paging.PageNumber > requestedPage.Paging.TotalPages
            ? CreateResponseMessageForInvalidPagingRequest(request)
            : CreateResponseMessageForPagingRequest(request);

        responseMessage.Content = new StringContent(JsonConvert.SerializeObject(bodyMessage));

        return responseMessage;

    private static dynamic CreateResponseBody<TEntity>(Page<TEntity> requestedPage, HttpRequestMessage requestMessage)
        Paging currentPage = requestedPage.Paging;
        string uriPath = requestMessage.RequestUri.GetLeftPart(UriPartial.Path);

        string prevPageLink = currentPage.HasPrev
            ? GeneratePaginationNavigationUri(currentPage.PageNumber - 1, currentPage.PageSize, uriPath)
            : string.Empty;

        string nextPageLink = currentPage.HasNext
            ? GeneratePaginationNavigationUri(currentPage.PageNumber + 1, currentPage.PageSize, uriPath)
            : string.Empty;

        string firstPageLink = currentPage.TotalPages == 0
            ? string.Empty
            : GeneratePaginationNavigationUri(1, currentPage.PageSize, uriPath);
        string lastPageLink = currentPage.TotalPages == 0
            ? string.Empty
            : GeneratePaginationNavigationUri(requestedPage.Paging.TotalPages, currentPage.PageSize, uriPath);

        dynamic pagInformation = new
            pageNumber = currentPage.PageNumber,
            pageSize = currentPage.PageSize,
            totalPages = currentPage.TotalPages,
            totalItemsCount = currentPage.TotalItemsCount,
            items = requestedPage.ToList()

        return pagInformation;

    private static HttpResponseMessage CreateResponseMessageForInvalidPagingRequest(HttpRequestMessage request)
        HttpResponseMessage errorResponse = request.CreateErrorResponse(
        return errorResponse;

    private static HttpResponseMessage CreateResponseMessageForPagingRequest(HttpRequestMessage request)
        HttpResponseMessage response = request.CreateResponse(HttpStatusCode.OK);
        return response;

    private static string GeneratePaginationNavigationUri(int page, int pageSize, string uriPath)
        UriBuilder prevUriBuilder = new UriBuilder(uriPath);
        NameValueCollection prevQuery = HttpUtility.ParseQueryString(prevUriBuilder.Query);
        prevQuery.Add(PageNumberQueryName, page.ToString(CultureInfo.InvariantCulture));
        prevQuery.Add(PageSizeQueryName, pageSize.ToString(CultureInfo.InvariantCulture));
        prevUriBuilder.Query = prevQuery.ToString();
        return prevUriBuilder.ToString();
Our controller is very simple, it only has to call the repository method that gets the items and format the response using the above code.
 public HttpResponseMessage Get(int page, int pageSize)

We are done. In this post we saw how easy we can expose a REST API with pagination support using EF and ApiController.


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions. Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood. using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope. In the fol

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder. using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token. The following code show to you how you could write the encode and decode methods.