Category Archives: REST

HTTP 406 Error When Using Angular $http.get Against SharePoint REST End Points

Update: Marc AD ndersson pointed out this great piece of info:  That explains a lot :).

That may be the worst title of a blog post ever!  Anyhoo.

I typically do all of my prototyping against an O365 instance.  I have my personal instance so that I don’t have to be worried about affecting anyone else.  As an aside – remember when we call carried around virtual machines on our laptops with MOSS – SQL Server, IIS, deciding Hyper-V vs. VMWare?  Anyhoo…

I had developed an app using Angular in this environment that does, among other things, this:

.success(function(data, status, headers, config) {

    var getLinksResponse = data;

    getLinksResponse.value.forEach(function(theResult) {

    // and so on and so froth

This was working just fine in two different SharePoint online environments.  However, when my colleague ported it to a Cloudshare instance, he was getting an HTTP 406 error (which was the first time I ever got that one, so … yay, I guess).  We did a bit of research and noticed that the “Accept” header was off.  SharePoint online was perfectly happy with:

Accept: application/json

But the cloudshare instance (which is SP on prem, hosted in a virtual server) wanted the classic “odata=verbose” added in as well:

Accept: application/json;odata=verbose

To fix that, we added the header as such:

var config = {headers: {
‘Accept’: ‘application/json;odata=verbose’

.success(function(data, status, headers, config) {

  var getLinksResponse = data;

  getLinksResponse.value.forEach(function(theResult) {

  // and so on and so froth

That got rid of the 406, but it also changed the format of the response.  It was more … verbose.  (haha!)  More changes were required and here’s the final result:

var config = {headers: {
‘Accept’: ‘application/json;odata=verbose’

.success(function(data, status, headers, config) {

  var getLinksResponse = data;

  getLinksResponse.d.results.forEach(function(theResult) {

  // and so on and so froth

This only turned into a 30 minute problem for us, so we lucked out.  Hopefully someone finds this useful.


How To Specify People as a Search Scope / Content Source Using SharePoint 2013 REST API

I had reason to work with the SharePoint 2013 Search API via REST for the first time.  I wanted to search for people, not documents.  The key learning here is that you specify content sources via its GUID (or at least in this case). The following jQuery snippet shows how:

    loadExpertsAsync: function() { = true;

            url: this.CreateFullApiUrl() +
                "?querytext='portals'&sourceid='b09a7990-05ea-4af9-81ef-edfab16c4e31'" +
                "&selectproperties='LinkedInProfileUrl,GoogleCirclesProfileUrl,BALargeProfilePictureUrls,BAGridPictures,WorkEmail,Skills,AboutMe,Interests,JobTitle,PastProjects,PictureURL,PreferredName,TwitterHandle,LinkedInProfileUrl,PreferredName,GoogleCirclesProfileUrl'" +
            method: "GET",
            headers: { "Accept": "application/json; odata=verbose" },
            cache: false,
            success: function (result) {

In my case, I’m running the API against SharePoint online. To get the GUID, I followed these steps:

  1. Access the SharePoint admin center
  2. Select “search” from the left hand navigation
  3. Select “Manage Result Sources”
  4. Select “Local People Results”
  5. Look at the URL.

My URL looked something like:

The sourceid parameter is what worked for me.

(I understand that the sourceid may actually be a sort of permanent thing with SP, but I’ll always check anyway 🙂 ).


undefinedSubscribe to my blog.

Follow me on Twitter at

Example SharePoint REST Calls

Here’s a set of sample REST calls that work for me and may help you out as well.  As of 02/2014, there are two examples 🙂

  1. Reference a Column With Spaces In Its Name
  2. Reference a Multi-Select Column
  3. Perform a People Search via REST


I’ll add to this as time passes.

Here are some useful inks I’ve found as well:

Reference a Column With Spaces In Its Name

I create a custom list with a column named “Blog Author” (space between Blog and Author).

The $select to reference that column is:


Simply replace the space with “_x0020_”.  We see the _x0020_ in many examples across the internets and REST is no different.

If you don’t do that, you’re liable to get an error message like this:

The expression “Blog Author” is not valid.

Easy enough.

Reference a Multi-Select Lookup Column

Set up:

  1. Create a custom list named Categories.
  2. Add some categories.  I added categories thusly:image
  3. Create another custom list called MockBlog and add Categories as a multi-select list column (or site column if that’s how you roll).

Add some items to your Mockblog list and you’re ready.

An Ajax style call using jQuery will look something like this:

serverUrl += "/_api/web/lists/GetByTitle('MockBlog')/items" +
             "?$select=Title,Categories/Title,Blog_x0020_Author/Title" + 

We’re telling SharePoint “Give me the title for all the Categories (Categories/Title). Get the actual values for Title by $expanding the Categories list.”  (My RESTful paraphrasing is probably pretty loose, but this how I’m interpreting it).

If you’re doing this via JavaScript and using Fiddler to look at the output, you get something like this in return:



(The above is a JSON object)

Perform a People Search via REST

I blogged about this separately. The key is to specify a sourceid parameter whose value is the GUID of the Local People content source. (Content sources used to be called scopes and it’s my-oh-my so hard not to call everything a scope for me!).

Read more about it here:



undefinedSubscribe to my blog.

Follow me on Twitter at

Quick and Easy: Create a SharePoint Site Using REST

There are a lot of resources around that show how to do this, but I couldn’t find a comprehensive go-to link, so here we are.

You can create a SharePoint site using the REST API.  Here’s a fully baked example:

    SiteRequestForm.html: Collect information and create a site for the user.

        <td>Site Name:</td>
        <td><input type="text" name="SiteName" id="SiteName" /></td>
        <td colspan="2">
            <input type="submit" id="CreateSiteButton" value="Create the Site" />

<script src="../Plugins/jquery-1.11.0.min.js"></script>

var CreateSiteLogicContainer = {

    createSiteData: {
            "parameters": {
                __metadata: { "type": "SP.WebInfoCreationInformation" },
                Url: "Paultest1",
                Title: "Paultest1",
                Description: "rest-created web by Paul!",
                Language: 1033,
                WebTemplate: "sts",
                UseUniquePermissions: false

    createSite: function () { = true;

        CreateSiteLogicContainer.createSiteData.parameters.Url = $("#SiteName").val();
            url: "",
            method: "POST",

            headers: {
                "Accept": "application/json; odata=verbose",
                "content-type": "application/json;odata=verbose",
                "X-RequestDigest": $("#__REQUESTDIGEST").val()

            data: JSON.stringify(CreateSiteLogicContainer.createSiteData),

            success: function () { alert("success"); },
            error: function () { alert("error"); }


    wireUpForm: function () {
        $("#CreateSiteButton").click(function () {
            alert("About to try and create the site.");




When successful, you get a JSON packet in response like this:


My key thoughts and learnings from this include:

  • This approach uses jQuery.  In my case, my jQuery library is located in “../plugins.”  You’ll want to change that to point to your favorite JQ location.
  • You can copy and paste that whole snippet into a Content Editor Web Part on a page and it should work just fine.  You’ll want to change the end point of the API call and make sure you reference JQ correctly.
  • The URL is relative to your API’s endpoint.  In my case, it’s creating sub-sites underneath
  • You don’t need to provide a content-length. Some blog posts and MSDN document implies that you do, but happened for me automatically, which I assume is being handled by the $.ajax call itself.
  • This line is required in order to avoid a “forbidden” response: "X-RequestDigest": $("#__REQUESTDIGEST").val().  There are other ways to do it, but this is pretty nice.  I have lost the link to blog that provided this shortcut.  H/T to you, mysterious blogger!

Good luck and hope this helps someone out.


undefinedSubscribe to my blog.

Follow me on Twitter at

Quick and Simple: SharePoint REST Call Only Returns 100 Records

I’ve been working on a public facing web site for my SharePoint practice here in New York and it uses a lot of JavaScript and REST calls to show content.

During mainline development, I create a small dataset with just 10 or so rows in a custom list and my REST calls all pulled from there.  Once I bumped up the list to have a few hundred rows of data to test for anticipated growth, I found that I was getting exactly 100 rows returned back on my REST calls.

This is a very simple thing to address.  In my case (and I believe in most cases), the default REST calls to SharePoint (and possibly as an industry standard?) return 100 rows.  To return more than the default, use the $top parameter on your call, as in:

GET /Insights%20Dev/_api/web/lists/GetByTitle(‘MockBlog’)/items?$select=ID,Title,Categories/Title,Blog_x0020_Author/Title,DatePublished,BlogSummary&$expand=Blog_x0020_Author,Categories&$filter=&$top=9999

I picked 9999 in this case since I know that growth-wise, there won’t be more than 200 or so rows added to this list in a year.  If it becomes ungainly, we can implement some paging down the road.


undefinedSubscribe to my blog.

Follow me on Twitter at