I am currently using SOAP Calls for getLeadChanges .My request are:
1) First Request :
{"start_position":{"oldest_created_at":"2013-04-04 00:00:00 UTC","latest_created_at":"2013-04-05 00:00:00 UTC"},"activity_name_filter":{"stringItem":["Send Email"]},"batch_size":"1000"}
Results : Remaining Records 35669 , offset = "ID:108510324,minID:108507849,maxID:108641860,rc:35669"
2) I make use of this offset for 2nd API call
{"start_position":{"oldest_created_at":"2013-04-04 00:00:00 UTC","latest_created_at":"2013-04-05 00:00:00 UTC","offset":"ID:108510324,minID:108507849,maxID:108641860,rc:35669"},"activity_name_filter":{"stringItem":["Send Email"]},"batch_size":"1000"}
Results : Remaining Records 34669, offset = "ID:108512252,minID:108507849,maxID:108641860,rc:34669"
3) I just keep on consuming this offset until Reamining Count =0 . But on my 24th API call
Request :
{"start_position":{"oldest_created_at":"2013-04-04 00:00:00 UTC","latest_created_at":"2013-04-05 00:00:00 UTC","offset":"ID:108639515,minID:108507849,maxID:108641860,rc:13669"},"activity_name_filter":{"stringItem":["Send Email"]},"batch_size":"1000"}
Results : Remaining Records 0
So the discrepancy is if 13669 records were remaining before the API call, then the result should give "Remaining Records = 12669" and I should be able to paginate until Remaining Records =0. But it looks like it is giving this 0 way earlier?
Is there behavior normal or I am missing something in my API calls?
.png)