Hi @gurkantuna,

For the trending data, this is by design. Trending is only useful to view in its original trending order. If you want more flexibility (although, there is no trending data) you should look at discover.

@travisbell said:

Hi @gurkantuna,

For the trending data, this is by design. Trending is only useful to view in its original trending order. If you want more flexibility (although, there is no trending data) you should look at discover.

Thanks @travisbell , actually I wasn't just talking about only trending, but I think that the case I mentioned is also required for trending data. It doesn't matter if it is a trend data or any other filter, the paginated data should return by any sorting parameter.

You can review it from
https://movies.gurkantuna.com/genre/28/pages/2 => order by vote_up from 8.2
https://movies.gurkantuna.com/genre/28/pages/3 => order by vote_up from 8.2 again!

The data that should be there is below
/pages/2 example 20 data 8.2, 8.2, 8.1.......8.0
/pages/2 example 20 data 8.0, 8.0, 7.9,7.8.......7.7

However, you should have noticed that the vote_up ranking only exists based on the page you are on and does not continue from the next page. Because there is no endpoint in the API from where I can pull data in this way. So, have I explained this clearly now?

You should take a look at the discover endpoints. They are the only endpoints that support more dynamic queries like this. The options for sort_by are listed there.