1 Reply Latest reply on Jun 28, 2017 5:40 PM by blake.scott

    API contents/ not respecting count or startIndex

    bfloyd@compunet.biz

      The following endpoint should start at 100 and give the next 100 records.

       

      curl -u <username>:<password> -o index1.json https://<URL>/api/core/v3/contents?fields=%40all&abridged=false&includeBlogs=false&count=100&startIndex=100

       

      But what I actually get is:

       

      {

        "itemsPerPage" : 25,

        "links" : {

          "next" : "https://<URL>/api/core/v3/contents?sort=dateCreatedDesc&fields=%40all&abridged=false&includeBlogs=false&count=25&startIndex=25"

        },

      .. 25 records

      }

       

      ANY Query I come up with seems to ignore COUNT and START Index and just give the first 25 records.

       

      {

        "jiveVersion" : "2016.3.7.0",

        "jiveCoreVersions" : [ {

          "version" : 2,

          "revision" : 3,

          "uri" : "/api/core/v2",

          "documentation" : "https://developers.jivesoftware.com/api/v2/rest"

        }, {

          "version" : 3,

          "revision" : 15,

          "uri" : "/api/core/v3",

          "documentation" : "https://developers.jivesoftware.com/api/v3/rest"

        } ],

        "instanceURL" : "https://<URL>",

        "jiveEdition" : {

          "product" : "jiven",

          "tier" : 300

        }

      }

       

       

      Thank you for any insight you can provide!

       

      Ben

        • Re: API contents/ not respecting count or startIndex

          Hi bfloyd@compunet.biz,

           

          It looks like you are hitting the default limit that is outlined in the API Documentation, Jive REST API v3.14 :

           

          The max number of items returned per page. Usually set with the count   query parameter. Most paginated results default to 25 itemsPerPage and can be set as high as 100 with the count parameter.

           

          If you want to adjust the default, the system property for this setting is jive.api.result.count.override.  It is not recommended to set this setting beyond 100.  If you are a cloud customer, you will need to open a support case within your secret support group.

           

          Best,

          Blake