2 Replies Latest reply on Apr 24, 2018 4:38 PM by Ian Springer

    Pagination issues with some endpoints

    Nicolas Brisoux

      We are having issues with the pagination using some endpoints, regarding the documentation the API should return the property “moreResult” which indicates if there are more results in subsequent pages.

       

      In these endpoints the “moreResult” property is not coming:

       

      • /rest/v1/lists.json
      • /rest/v1/lists/{LIST_ID}/leads.json
      • /rest/v1/leads/programs/{PROGRAM_ID}.json
      • /rest/v1/campaigns.json

       

      Request:

      /rest/v1/lists.json?batchSize=5&access_token=xxxxxxxxxxxxxx

      Response:

      {

          "requestId": "f9fc#1605b4c5a14",

          "result": [

              {

                  "id": 1001,

                  "name": "Tradeshow1",

                  "workspaceName": "Default",

                  "createdAt": "2015-11-15T20:03:16Z",

                  "updatedAt": "2016-12-28T20:17:17Z"

              },

              ........

              ........

              ........

           ],

          "success": true,

          "nextPageToken": "TMXXXAWSCCSRDRWQZ33VCJOFXI======"

      }

       

      I think the "nextPAgeToken" property is not reliable to determine if are more results.

       

      Any idea? What can we do?

       

      Thanks in advance,