Netflix API Forums

API Forum

RSS Feed

Possible bug? - Requesting higher start index than max results

  1. OK - yes, I know I shouldn't be asking for more than i got - and I added code to check max results as soon as i noticed this behavior. Regardless I wonder if the API should at least return a different subcode.

    In the scenario my user has 75 results.;
    http://api.netflix.com/users/me-/recommendations?expand=synopsis,formats&start_index=0&max_results=25
    http://api.netflix.com/users/me/recommendations?expand=synopsis,formats&start_index=25&max_results=25
    http://api.netflix.com/users/me/recommendations?expand=synopsis,formats&start_index=50&max_results=25
    http://api.netflix.com/users/me/recommendations?expand=synopsis,formats&start_index=75&max_results=25 <! -- (o based index means this is more than we have)
    http://api.netflix.com/users/me/recommendations?expand=synopsis,formats&start_index=100&max_results=25
    http://api.netflix.com/users/me/recommendations?expand=synopsis,formats&start_index=125&max_results=25


    The result when I ask for the 76 -100 titles i get a dump of the entire recommendations set, all 75 results. That repeats when i ask for 101-125, etc

    Message edited by eddiewebb 2 years ago

  2. JR Conlin2 years ago

    Yep, looks like a bug. Thanks!

  3. eddiewebb2 years ago

    np.

    BTW - You guys have done an fantastic job with the API, one of the more compliant and standardized restful services I have used.

[ Page 1 of 1 ]