Introduction

Welcome to the SharePoint 2013 REST Series. In my previous article, Getting List Items From a List in SharePoint 2013 Using REST API we saw how to create a Custom List using the REST API.

In this article, we will discuss how to delete a SharePoint List using the 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 give you entry into granular access points.

List of REST End Points

The following is a list of End points that are very commonly used in a SharePoint list.

Note: 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

Step 2:

Navigate to the App.js file. Copy the following code and paste it in.

Code
  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/";
  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
  21. // Load the js files and continue to the successHandler
  22. $.getScript(scriptbase + "SP.RequestExecutor.js", execCrossDomainRequest);
  23. });
  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="CustomList”
  33. // Issue the call against the app web.
  34. // To get the title using REST we can hit the endpoint:
  36. // appweburl/_api/web/lists/getbytitle('listname')/items
  37. // The response formats the data in the JSON format.
  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/getbyTitle('Master')/Items?$select=Title&@target='" + hostweburl + "'",
  45. method: "GET",
  46. headers: { "Accept": "application/json; odata=verbose" },
  47. success: function (data) {
  48. alert("success: " + JSON.stringify(data));
  49. },
  50. error: function (err) {
  51. alert("error: " + JSON.stringify(err));
  52. }
  53. }
  54. );
  55. }
  56. // This function prepares, loads, and then executes a SharePoint query to get
  57. // the current users information
  58. //Utilities
  59. // Retrieve a query string value.
  60. // For production purposes you may want to use
  61. // a library to handle the query string.
  62. function getQueryStringParameter(paramToRetrieve) {
  63. var params =
  64. document.URL.split("?")[1].split("&");
  65. for (var i = 0; i < params.length; i = i + 1) {
  66. var singleParam = params[i].split("=");
  67. if (singleParam[0] == paramToRetrieve)
  68. return singleParam[1];
  69. }
  70. }

Screenshot





Step 3:

While deploying, you will be prompted with the following screen. Press Trust it and proceed to with the deployment.

Trust it

Code Walkthrough

A . GET Method in REST API

A SharePoint 2013 REST service supports sending POST commands that include object definitions to endpoints that represent collections. In this example, Master is a custom SharePoint list that will be deleted..
  1. executor.executeAsync(
  2. {
  3. url: appweburl + "/_api/SP.AppContextSite(@target)/web/Lists/getbytitle('" + listName + "')?@target='" + hostweburl + "'",
  4. method: "POST",
  5. headers: {
  6. "IF-MATCH": "*",
  7. "X-HTTP-Method": "DELETE"
  8. },
  9. success: function (data) {
  10. alert("success: " + JSON.stringify(data));
  11. },
  12. error: function (err) {
  13. alert("error: " + JSON.stringify(err));
  14. }
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":"*"

HTTP-Method:”Delete”

A HTTP DELETE command against the specific endpoint URL to delete the SharePoint object represented by that endpoint. For recyclable objects, such as lists, files, and list items, this results in a Recycle operation.

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 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="Master";
Summary

I hope this article helps you. Happy Share Pointing.