background preloader

SharePoint REST API

Facebook Twitter

Use OData query operations in SharePoint REST requests. This documentation is archived and is not being maintained.

Use OData query operations in SharePoint REST requests

Learn how to use a wide range of OData query string operators to select, filter, and order the data you request from the SharePoint REST service. Use the $select query option to specify which fields to return for a given list, list item, or other SharePoint object represented by an entity set. You can use $select=* to return all available fields. Get to know the SharePoint 2013 REST service. SharePoint 2013 adds the ability for you to remotely interact with SharePoint sites by using REST.

Get to know the SharePoint 2013 REST service

Now, you can interact directly with SharePoint objects by using any technology that supports standard REST capabilities. To access SharePoint resources using REST, construct a RESTful HTTP request, using the Open Data Protocol (OData) standard, which corresponds to the desired client object model API. For example: Client object model method: Fields REST API reference. This documentation is archived and is not being maintained.

Fields REST API reference

Learn about field-related resources and endpoints in the SharePoint REST API. The examples in this article use jQuery AJAX requests. Before you try to use the examples, do the following: SharePoint and Web Services. In my last article, I showed you how to work with Windows SharePoint Services from within Microsoft Office 2003.

SharePoint and Web Services

But what if you're using something other than Office 2003 as as development environment, and want to tap into SharePoint data? No problem! Development With A Dot - Looping Through List Items in SharePoint 2013 Designer Workflows. SharePoint 2013 Designer workflows now has two new interesting options: the ability to call HTTP web services and the option to loop over some code a number of times.

Development With A Dot - Looping Through List Items in SharePoint 2013 Designer Workflows

This, together with the new REST API, which supports querying lists and returning data in JSON, allows iterating through list items in a workflow, something that was not possible before. In order to demonstrate this, let’s create a new Site Workflow in SharePoint Designer, that will iterate through the Tasks list: Call it Process Tasks, for example, and make sure you select SharePoint 2013 as the platform type. In the workflow designer, let’s start by creating a new stage, call it Retrieve Tasks: Consuming the SharePoint 2013 REST Service from SharePoint Designer. In SharePoint 2013 workflows was introduced a new action named Call HTTP Web Service.

Consuming the SharePoint 2013 REST Service from SharePoint Designer

This action is flexible enough to make requests to a variety web services including SharePoint REST service. Figure 1 shows you the Call HTTP Web Service action on the SharePoint Designer 2013 surface. Figure 1. SPD Workflow that demonstrates how to leverage Call HTTP Web Service action for Read operation The specified example demonstrates how to perform Read operation for retrieving webs information:

Calling user profile service from SharePoint Designer 2013 workflow yields "unauthorized" Current community your communities Sign up or log in to customize your list. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges.

Calling user profile service from SharePoint Designer 2013 workflow yields "unauthorized"

Workflow Loop Through Multiple SharePoint Items. Finally!

Workflow Loop Through Multiple SharePoint Items

It can be done with a SharePoint Designer 2013 workflow! This is something that I’ve been wanting to be able to do for YEARS, and now it’s possible… and I’m just now blogging about it. No, this can’t be done in any previous versions unless you go buy a 3rd party tool or get a dev to write something custom. Think about any time you’ve wanted to be able to edit multiple items in a list according to some condition. Think about lookups. 2013 - REST POST: How to add a list item with 'people and group', 'choice,' and 'URL' fields? I am trying to create a form for a SharePoint Hosted app that will allow users to request a teamsite.

2013 - REST POST: How to add a list item with 'people and group', 'choice,' and 'URL' fields?

The form writes to a list that is contained in the SharePoint site collection, from which a timer job will read and complete the teamsite provisioning process. The list I am updating contains vital 'User and Group', 'Choice', and 'URL' fields and I am having difficulty getting my REST post to work. When I run this code, I get a 400 error with this JSON reponse: Dinusha's Blog: Cross site collection data access via HTTP web service for a SharePoint 2013 designer workflow. Resolving Unauthorized exception. Recently I created a SharePoint 2013 approval workflow where I had to take approvers from a list located at a different SharePoint site collection.

Dinusha's Blog: Cross site collection data access via HTTP web service for a SharePoint 2013 designer workflow. Resolving Unauthorized exception

In this example I have two site collections named Config and Project where I have created the workflow in the Project site collection using SharePoint Designer. In the Config site collection I have a list called Approvers where I store relevant information regarding approvers. Following diagram shows the scenario I described. Create a SharePoint Site (SPWeb) using REST in SPD 2013 Workflow – SharePointRyan. I have been struggling with an issue for several days, and it’s one I’ve been trying to solve for an upcoming SharePoint Saturday presentation. That issue is creating SharePoint sub sites/SPWebs automatically via the “Call HTTP Web Service” action in SharePoint Designer 2013 workflow. There were several sources of information that ultimately provided the solution, so I will be sure to credit those folks in this article. There are several steps which are required to make this happen, and the coolest part is; this will work both on-premise and in Office 365/SharePoint Online!

The solution I was trying to provide was: