Hey. I don’t know this is a bug or the developers themselves have done so. I use VK API on android. Here the request is ready, sent with a working token, and the answer does not match the answer if I do it on the API website. This discrepancy on the number and list of songs. An example is this: the simplest query, Q="twenty one pilots ride" and count 5 (this is a bunch of songs to send to the maximum in response). In the application, the answer is: count (the number of songs satisfying this keyword) is exactly 4187 , about the amount that I sent 3 pieces, but I had to 5 . The same on the site: count 4191 , returns 5 songs that the first 2 not in response to the request in my application, and of course, these first 2 songs are the most suitable. Who faced this problem?

    1 answer 1

    Problems can be in two places:

    1. You forgot to pass the parameter v (API version), which is why everything works awry.
    2. Songs that are lacking in response are protected by copyright. As far as I know, only copyright-protected songs are returned to official applications, and the API console is also considered an official application. Alternatively, you can try making requests to audio.search , pretending to be an official application .
    • since this approach is not working. It is necessary to dig into the apk can find something. 100% developer adds some parameter - Javidan