J
J
Jeff_Parker2022-04-06 12:37:50
Parsing
Jeff_Parker, 2022-04-06 12:37:50

The request does not return all the data. Why?

It is necessary to automate reporting from a web application.
It was decided to repeat requests and take data in JSON, it turned out to be much more convenient. The problem arose when I decided to speed up the parsing process - namely, not to enter the bot separately for each account, but to work only with the general "pool", that is, with the page where all accounts are listed. Going there, you can see such a request

624d59f65fdf0858065582.jpeg

. Everything seems to be in order, an array of 160 data lines. This is what you need. But...

624d5a7817a2c301052007.jpeg

It seems there is less data, only 50 rows out of 160 promised. Strange...
After breaking my head for fifty years for a couple of minutes, I realized that the number of elements on the page corresponds to what the request transmits. Here they are, these elements

624d5d57acd88629075879.jpeg

To be honest, I tried to show these elements in the console for almost half an hour ...
And this is how they look on the page, for those who are interested

624d5ef331c7b724016523.jpeg

And 47 more of them
Now let's move on to the question, how can I still get all these elements if the number of rows of data limited by page capacity?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
Alexey Ukolov, 2022-04-06
@Jeff_Parker

We do not know how to work with an API unknown to us. Obviously, there is some kind of pagination there, if the data from number 51 can still be obtained somehow. What this pagination looks like, we do not know.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question