Let’s Capture Missing or Insufficient SharePoint REST Endpoints

2 minute read

Today I got an alert that the SharePoint UserVoice suggestion from Corey Roth (@coreyroth) entitled Add managed metadata term store operations to REST API got the coveted “Thinking About It” tag from the Product Group. I like to tweet out changes like this to let people know the Product Group is listening and acting on our feedback – beyond saying “That’s good feedback!” It’s not all wine and roses, though:

Thank you for your feedback! Just letting you know that we absolutely have this in our backlog, but unfortunately this currently is not included in our short term engineering tasks. We absolutely understand the request and seeing vote counts around this, will help to further prioritize this work for next sprints.

I got a couple of tweets back right away pointing out some other current holes in the REST APIs.

If you think there are other endpoints the REST APIs need or endpoints that don’t work well, please add them to the comments here. I’ll work them up into a list for the Product Group and let’s see what we can get moving! We’ll play by the rules and add the list to UserVoice, but I think all the individual suggestions get lost and it’s harder to see the bigger picture. For each item on the list, I’ve tried to capture related UserVoice suggestions.

The list so far:

Advertisements

25 Comments

  1. I think Rest is great enhancements but it needs more improvements such as search is limited to specific properties, like if I need to search users of a specific department or I need to search a user by email, rest is not going to help me.
    I have a list containing 1000s of records for last a few years and I need to extract data for any date range, from date and to date, despite the claims date ranges don’t work through rest api to filter custom lists.
    In document sets, through rest api, I cant filter with custom properties.
    In a common scenario, suppose I have a number of subsites and I have to display those sub sites as per user permissions. There is no function to bring sub site lists as per user permission. Therefore, 1st load all sub sites then check permissions and display to the user, is actually extra overhead.

    I believe a rich set of api or functions is needed to meet user expectations.
    Mostly errors that rest api returns are of no use, it could be more intelligent.
    In my intranet dashboard, I want to pull data from multiple other SharePoint bases applications but cross site is not supported in this case.

    Reply
    • @Mumtaz:

      I think some of your issues may not actually be issues.

      I agree that the REST endpoint for user profiles is not great, but unfortunately, that’s as much a function of the User Profile Service as it is the REST endpoint. Have you tried using search instead?

      I just did the following date/time filter on a Custom List, which worked fine:
      ?$filter=MyDate%20ge%20datetime%272017-05-15T00:00:00.000Z%27%20and%20EventDate%20le%20datetime%272017-05-15T23:59:59.000Z%27

      I also filter on custom properties in Document Sets all the time, so that should work.

      Making a call to /_api/web/webs should provide permission trimmed results.

      What version of SharePoint are you using? Can you provide specific errors which you think could use some improvement?

      M.

      Reply
  2. itemCount in RestApi needs improvement as well, currently its not supporting in combination with filter. itemCount returns counter of whole list and simply ignoress filters

    Reply

Have a thought or opinion?