How to Get the List of Features Activated in SharePoint Web Application 2013 Using REST API

Introduction

Welcome to the SharePoint 2013 REST Series. In my previous articles, we saw how to get web info for a SharePoint web application using the REST API.

This article explains how to get the list of Features enabled for a web application.

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
            http://server/site/_api/site
  • Web
            http://server/site/_api/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 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 Full Permission
Site Collection Full Permission
Web Full Permission Full Permission
List Full Permission Full Permission

    /List of REST End Points.jpg

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

Code

  1.   var hostweburl;     
  2.   var appweburl;     
  3.        
  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.               
  8.              //Get the URI decoded URLs.     
  9.      hostweburl =     
  10.          decodeURIComponent(     
  11.             getQueryStringParameter("SPHostUrl"));     
  12.      appweburl =     
  13.          decodeURIComponent(     
  14.              getQueryStringParameter("SPAppWebUrl"));     
  15.                 // Resources are in URLs in the form:    
  16.          // web_url/_layouts/15/resource    
  17.          var scriptbase = hostweburl + "/_layouts/15/";      
  18.       
  19.          // Load the js file and continue to load the page with information about the list top level folders.    
  20.          // SP.RequestExecutor.js to make cross-domain requests    
  21.              
  22.           // Load the js files and continue to the successHandler    
  23.              $.getScript(scriptbase + "SP.RequestExecutor.js", execCrossDomainRequest);    
  24.               });    
  25.                  
  26.               // Function to prepare and issue the request to get    
  27.            //  SharePoint data    
  28.            function execCrossDomainRequest() {    
  29.              // executor: The RequestExecutor object    
  30.              // Initialize the RequestExecutor with the app web URL.    
  31.              var executor = new SP.RequestExecutor(appweburl);                            
  32.   
  33.              // Issue the call against the app web.    
  34.              // To get the title using REST we can hit the endpoint:    
  35.                  
  36.              // The response formats the data in the JSON format.    
  37.              // The functions successHandler and errorHandler attend the    
  38.              //      sucess and error events respectively.    
  39.    executor.executeAsync(  
  40.      {  
  41.          url:  
  42.   
  43.              appweburl +   
  44.                
  45.              "/_api/SP.AppContextSite(@target)/web/Features?@target='" +      
  46.              hostweburl + "'",    
  47.          method: "POST",  
  48.        
  49.   
  50.              headers: { "Accept""application/json; odata=verbose" },                   
  51.              success: function (data) {    
  52.                  alert("success: " + JSON.stringify(data));    
  53.              error: function (err) {    
  54.                  alert("error: " + JSON.stringify(err));    
  55.              }      
  56.   
  57.                  }              
  58.   
  59.              );                                
  60.   
  61.            }                      
  62.   
  63.      // This function prepares, loads, and then executes a SharePoint query to get     
  64.      // the current users information    
  65.          
  66.  //Utilities     
  67.       
  68.  // Retrieve a query string value.     
  69.  // For production purposes you may want to use     
  70.  // a library to handle the query string.     
  71.  function getQueryStringParameter(paramToRetrieve) {     
  72.      var params =     
  73.          document.URL.split("?")[1].split("&");       
  74.      for (var i = 0; i < params.length; i = i + 1) {     
  75.          var singleParam = params[i].split("=");     
  76.          if (singleParam[0] == paramToRetrieve)     
  77.              return singleParam[1];     
  78.      }     
  79.  }     
Step 3: When deploying, you will be prompted with the following screen. Press Trust it and proceed with the deployment.
List of REST End Points 3.jpg
Output
 
WebInfo property Description
Created Gets a value that specifies when the site was created.
Description Gets or sets the description for the site.
Id Gets a value that specifies the site identifier.
Language
Gets a value that specifies the locale ID (LCID) for the language that is used
LastItemModifiedDate
Gets a value that specifies when an item was last modified in the site.
Title Gets or sets the title for the site.
WebTemplateId Gets the identifier of the site template.

Code Walkthrough

  • 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":"*".
  • 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. 1.  function execCrossDomainRequest() {    
  2. 2.  // executor: The RequestExecutor object    
  3. 3.  // Initialize the RequestExecutor with the app web URL.    
  4. 4.  var executor = new SP.RequestExecutor(appweburl); var metatdata = "{ '__metadata': { 'type': 'SP.Data.TestListListItem' }, 'Title': 'changelistitemtitle'}";    
Summary

I hope this article helps you.

Recommended Ebook

SharePoint Framework (SPFx) A Developers Guide

Download Now!
Similar Articles