Creating a Document Library using SharePoint 2013 REST API

Introduction

The SharePoint 2013 environment adds the ability 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 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 end points that are the most commonly used on 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’)

In this article, let's see how to create a SharePoint Document Library using the REST API. The following code is tested in my SP 2013 online environment.

Step 1: Before writing your code, please ensure that 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

permission 

In SharePoint 2013, use POST to create entities such as lists and sites. The

Step 2: Navigate to App.js file Copy the following code and Paste it.
Code
  1. 'use strict';  
  2. var hostweburl;   
  3. var appweburl;   
  4.    
  5.     // This code runs when the DOM is ready and creates a context object which is   
  6.     // needed to use the SharePoint object model  
  7.     $(document).ready(function () {           
  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.              // Function to prepare and issue the request to get  
  26.           //  SharePoint data  
  27.           function execCrossDomainRequest() {  
  28.             // executor: The RequestExecutor object  
  29.             // Initialize the RequestExecutor with the app web URL.  
  30.             var executor = new SP.RequestExecutor(appweburl);             
  31.             var listName="CustomLibrary";  
  32.   
  33.             // Issue the call against the app web.  
  34.             // To get the title using REST we can hit the endpoint:  
  35.   
  36.             //      appweburl/_api/web/lists/getbytitle('listname')/items  
  37.             // The response formats the data in the JSON format.  
  38.   
  39.             // The functions successHandler and errorHandler attend the  
  40.             //      sucess and error events respectively.  
  41.             executor.executeAsync(  
  42.                 {  
  43.             url: appweburl + "/_api/SP.AppContextSite(@target)/web/Lists?@target='" + hostweburl + "'",  
  44.             method: "POST",  
  45.             body: "{ '__metadata': { 'type': 'SP.List' }, 'BaseTemplate': 101,'Description': '" + listName + "', 'Title':'" + listName + "'}",  
  46.             headers: {"content-type""application/json; odata=verbose"},  
  47.             success: contextSuccessHandler,  
  48.             error: contextErrorHandler  
  49.                 }  
  50.             );  
  51.               
  52.           }                       
  53.     // This function prepares, loads, and then executes a SharePoint query to get   
  54.     // the current users information       
  55. //Utilities     
  56. // Retrieve a query string value.   
  57. // For production purposes you may want to use   
  58. // a library to handle the query string.   
  59. function getQueryStringParameter(paramToRetrieve) {   
  60.     var params =   
  61.         document.URL.split("?")[1].split("&");     
  62.     for (var i = 0; i < params.length; i = i + 1) {   
  63.         var singleParam = params[i].split("=");   
  64.         if (singleParam[0] == paramToRetrieve)   
  65.             return singleParam[1];   
  66.     }   
  67. }     
  68. //Retrieve the form digest value.      
  69. //Store the value of the form digest.   
  70. function contextSuccessHandler(data) {   
  71.     alert("List Created Successfully"); 
Screenshot
 
Screenshot
Code
Coding
Code Walkthrough

A. Post Method in REST API

A SharePoint 2013 REST service supports sending POST commands that include object definitions to endpoints that represent collections. For example, you could send a POST command that included a new list object definition in ATOM to the following URL, to create a SharePoint list:

  1. executor.executeAsync(  
  2. {  
  3.     url: appweburl + "/_api/SP.AppContextSite(@target)/web/Lists?@target='" + hostweburl + "'",  
  4.     method: "POST",    body: "{ '__metadata': { 'type': 'SP.List' }, 'BaseTemplate': 101,'Description': '" + listName + "', 'Title':'" + listName + "'}",  
  5. headers: {"content-type""application/json; odata=verbose"},  
  6. success: contextSuccessHandler,  
  7. error: contextErrorHandler 

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 = new SP.RequestExecutor(appweburl);  
  5.     var listName="CustomLibrary";
  6. }

Summary

I hope this article helps you.

Up Next
    Ebook Download
    View all
    Learn
    View all