Idea

Thanks for the reply!

It sounds like I will need to use the nextPage element, as all calls do not contain the totalPages/totalElements elements, and this wont be added to those that don't contain them from Anton's reply below. This is unfortunate, but a reality. Your second solution may work for some, but assuming that you'll never have more than 1000 records returned does not sound like a good idea.

Anyway, thanks again!

Thanks for the reply!

I see what you're saying. However, while I do not understand how your data is stored on the back end, in any traditional RDBMS (SQL Server, MySQL, etc.) getting a count of all elements requires substantially less processing then retrieving all of the records. If your data is stored in this way, it should be really easy, and fast to get a count of all of the records. Also, there should always be a date range for the logs that are being requested, and even if there was no date, I believe that you do not keep call logs indefinitely, so there will always be a cutoff for the amount of call logs available to pull. So saying that there is a potential to fetch an unlimited number of records is not right.

As far as I can tell, the max number of elements allowed on one page is 1000. This seems like a lot, but we have more than 1000 messages for any given location/day on a very regular basis. 

The reason that I chose to use the totalPages element to iterate through all pages was because I assumed (falsely) that all requests/results would be consistent, thus returning the totalPages for any and all calls. Secondly, using a specific number for iterations is a more concrete, predictable way to get all record. Checking for the nextPage element each and every time just requires a bit more processing.

Actually, checking for nextPage element shouldn't be any more expensive.

Here is a recursive example using the JS SDK to fetch all call logs. It expects some environment variables to be set (which are prefixed with process.env.[ENV_VAR_NAME].

    function getCallLogsPage() {
                   
        return platform
            .get('/account/~/call-log', {
                   
                page: page,
                perPage: process.env.LOGS_PER_PAGE, // MAX is 1000
                dateFrom: process.env.DATE_FROM,
                dateTo: process.env.DATE_TO,
                view: process.env.VIEW
            })  
            .then(function (response) {
                   
                console.log(response.json());
                // Sanity check
                if( response ) { 
                    console.log("************** SHOULD BE A SUCCESSFUL 200 REQUEST - NOTHING TO SEE HERE...MOVE ALONG PLEASE ***************");
                    if(timeoutObject) {
                   
                        clearTimeout(timeoutObject);
                    }   
                    retryAfter = 0;
                    var data = response.json();
                    //console.log("************** THE NUMBER OF CALL LOGS THIS REQUEST CYCLE ARE : ***************", data.records.length);
                    callLogs = callLogs.concat(data.records);
                    if (data.navigation.nextPage) {
                   
                        page++;
                        return getCallLogsPage(); // this will be chained
                    } else {
                   
                        return callLogs; // this is the finally resolved thing
                    }
                }
            });
    } // end of getCallLogsPage()
    /*
     Loop until you capture all extensions, and then continue processing data
     */
    return getCallLogsPage()
    .then(<NEXT_FUNCTION_IN_PROGRAM>)
    .catch(function (e) {
                   
            console.error(e);
            throw e;
        }
    });

Thanks for your reply. I have my app updated to use the nextPage element. Thanks!