Deezer album chart API returns different results with access token -

i noticed different response deezer api album chart request when valid access token included in request. without access token full results, it, first 14 results. also, 14 results don't match first results of full results.

request without access token (using httpie):

http 'https://api.deezer.com/chart/462/albums' 

response:

{   ...   "next": "https://api.deezer.com/chart/462/albums?index=10",    "total": 300 } 

request access token (using httpie):

http 'https://api.deezer.com/chart/462/albums?access_token=frk...' 

response:

{   ...   "next": "https://api.deezer.com/chart/462/albums?access_token=frk...&index=10",    "total": 14 } 

so album chart results filtered according requesting user? if so, how , why? there way unfiltered results using deezer javascript sdk dz.api call (that automatically adds access token)?

actually, token, should know, allows identify user. rights (from country, label, account...) according track read in order filter availability of tracks, that's why can have different results or without token, 2 different tokens.

you can use dz.api without login, have results according current country. adds automatically token if you're logged.