Retrieving Query Results by Date Range in SharePoint Site 2013 Using REST SEARCH API


Welcome to SharePoint 2013 REST Series. In my previous article, we saw how to retrieve query suggestions in a SharePoint site using SEARCH REST API.

This article explains the way how to filter SharePoint query string results by date range in REST API
The SharePoint 2013 environment adds the ability for you to remotely interact with SharePoint sites using REST. So you can talk to SharePoint objects using any technology that supports standard REST capabilities. In this way, SharePoint data can be accessed anywhere and everywhere.

List of REST Access Points

The following is a list of access points that provide you entry into granular access points.

  • Site

  • Web

  • User Profile

    http:// server/site/_api/SP.UserProfiles.PeopleManager
  • Search

    http:// server/site/_api/search
  • Publishing

    http:// server/site/_api/publishing

List of REST Popular End Points 

The following is a list of endpoints that are the most commonly used in a SharePoint list.

  • http://server/site/_api/web/lists
  • http://server/site/_api/lists/getbytitle(‘listname’)
  • http://server/site/_api/web/lists(‘guid’)
  • http://server/site/_api/web/lists/getbytitle(‘Title’)

Note: The following code is tested in my SP 2013 online environment.

Step 1: Before writing your code, please ensure you have sufficient permission to access cross-domain requests. So I have given full permission to all the contents listed below.

Tenant Full Permission
Site Collection Full Permission
Web Full Permission
List Full Permission


Step 2 : Navigate to the App.js file and copy the following code and paste it in.


  1. ‘use strict’;
  2. var hostweburl;
  3. var appweburl;
  4. // This code runs when the DOM is ready and creates a context object which is
  5. // needed to use the SharePoint object model
  6. $(document).ready(function () {
  7. //Get the URI decoded URLs.
  8. hostweburl =
  9. decodeURIComponent(
  10. getQueryStringParameter(“SPHostUrl”));
  11. appweburl =
  12. decodeURIComponent(
  13. getQueryStringParameter(“SPAppWebUrl”));
  14. // Resources are in URLs in the form:
  15. // web_url/_layouts/15/resource
  16. var scriptbase = hostweburl + “/_layouts/15/”;
  17. var accountName = ‘Domain\\Login’;
  18. // Load the js file and continue to load the page with information about the list top level folders.
  19. // SP.RequestExecutor.js to make cross-domain requests
  20. // Load the js files and continue to the successHandler
  21. $.getScript(scriptbase + “SP.RequestExecutor.js”, execCrossDomainRequest);
  22. });
  23. // Function to prepare and issue the request to get
  24. //  SharePoint data
  25. function execCrossDomainRequest() {
  26. // executor: The RequestExecutor object
  27. // Initialize the RequestExecutor with the app web URL.
  28. var executor = newRequestExecutor(appweburl);
  29. // Issue the call against the app web.
  30. // To get the title using REST we can hit the endpoint:
  31. // The response formats the data in the JSON format.
  32. // The functions successHandler and errorHandler attend the
  33. //      sucess and error events respectively.
  34. executeAsync(
  35. {
  36. hostweburl + “‘”, url: appweburl + “/_api/ search/suggest?querytext= ‘ContentType:Employee LeavingDate>2014-10-03’&rowlimit=500&SelectProperties=’ LeavingDate,fileExtension,filename,ContentType'”@target='” + hostweburl + “‘”,
  37. method: “GET” “,
  38. headers: { “Accept”: “application/json; odata=verbose”},
  39. success: function (data) {
  40. alert(“success: “+ JSON.stringify(data));
  41. error: function (err) {
  42. alert(“error: “+ JSON.stringify(err));
  43. }
  44. }
  45. );
  46. }
  47. // This function prepares, loads, and then executes a SharePoint query to get
  48. // the current users information
  49. //Utilities
  50. // Retrieve a query string value.
  51. // For production purposes you may want to use
  52. // a library to handle the query string.
  53. function getQueryStringParameter(paramToRetrieve) {
  54. var params=
  55. URL.split(“?”)[1].split(“&”);
  56. for(var i = 0; i < params.length; i = i + 1) {
  57. var singleParam = params[i].split(“=”);
  58. if(singleParam[0] == paramToRetrieve)
  59. returnsingleParam[1];
  60. }
  61. }


Step 3: When deploying, you will be prompted with the following screen. Press Trust it and proceed with the deployment.


Code Walkthrough

A. Post Method in REST API

The SharePoint 2013 REST service supports sending POST commands that include object definitions to endpoints that represent collections. In this example, Test List is a custom SharePoint list where list items are updated.

IF-MATCH header

Provides a way to verify that the object being changed has not been changed since it was last retrieved. Or, lets you specify to overwrite any changes, as shown in the following example: “IF-MATCH”:”*”.

B. Request Executor.JS

The cross-domain library lets you interact with more than one domain in your remote app page through a proxy. SP.RequestExecutor.js acts as a cross-domain library to fetch or create a SharePoint list from your APP domain.

  1. function execCrossDomainRequest() {
  2. // executor: The RequestExecutor object
  3. // Initialize the RequestExecutor with the app web URL.
  4. var executor = newRequestExecutor(appweburl); var metatdata = “{ ‘__metadata’: { ‘type’: ‘SP.Data.TestListListItem’ }, ‘Title’: ‘changelistitemtitle’}”;


Please check my other interesting topics below

SharePoint 2016 Features

Document Library Open Behavior in SharePoint 2013

Item Level Permission in SharePoint 2013

Leave a Reply

Your email address will not be published. Required fields are marked *