Our application is calling the Search for content endpoint to retrieve thousands of files matching specific criteria.
Because we have to retrieve so many files, we "paginate" that endpoint using the limit and offset parameters.
The first call we make looks like the URL below
The next call is the exact same URL, but offset is 200. Then the following call offset is 400.
This should continue until we retrieve all the possible files. However, in our application, the call below consistently fails with a 400 Bad Request error.
Note all the previous "pagination" calls (offset = 0 upto offset = 9800) are successful. Also, the total_count field has a value of 14151, so offset = 10000 should return files.
Are there some undocumented changes with the Search for content endpoint that caps the number of results that can be returned or does the offset now have a maximum value that it can't exceed?