updates.friends filters not working

[Viswanath]

Hi,
I'm sending the following request from my windows phone app:

GET https://www.goodreads.com/updates/fri...

But the server still returns everything and does not filter anything .Is this some known problem or am I missing something in the URL?

Thanks

[Viswanath]

Ping? Any idea why this is happening? It's a simple request but doesn't seem to work.

[Nichole]

Hey Viswanath,

Can you explain what you mean "it returns everything"? Are you seeing updates from people you aren't friends with?

Or do you mean you're passing in an "update_filter" and it's not honoring that parameter?

[Viswanath]

Thanks for your response.

It's not honoring the following filters:

1) max_updates
2) update_filter
3) update

The result is same whether I use these filters or not.

[Viswanath]

And since max_updates is not working, I'm able to get more than 12 items or so in the news feed. It's typically filled with just friend requests and hence making the feed pretty much useless.. Do you have better API's to get more items just like your native apps? I feel this is a very critical UX for any app and I need to have the data to actually display it properly in the app.

[Viswanath]

Hi Nichole,

Any progress on this? This is really degrading the quality of my app. Any idea what is going on here? Appreciate you taking the time.

Thanks
Viswa

[Viswanath]

I have verified that update_filter works in this. But 'update' does not work. According to the documentation, this can takes the following values:

1. books
2. reviews
3. statuses
4. all (default)

This is the setting that is not being honored.

[Gunther]

i'm hitting the same problem, is there any progress on this?

[David]

Hey guys, I figured out how it ...sort of... works.

Turns out there's an undocumented parameter called "max_updated_at" that takes some id. If you include this, it tells the api where to start getting the next set of data from.

Problem is that this id isn't given anywhere in the public API. In the private API, there's a "maxUpdatedAt" attribute that's returned with each result so the app can tell the api where to start the next time, but in the public api, that attribute isn't there and we're SOL.

tldr; they (intentionally?) left the ability to get multiple update pages out of the public API.

[Oleg]

David wrote: "Hey guys, I figured out how it ...sort of... works.

Turns out there's an undocumented parameter called "max_updated_at" that takes some id. If you include this, it tells the api where to start get..."

set max_updated_at to unixtime of last item updatad_at field from friends.update list.

If you have any more information of undocumented parameters - please write it. I am creating sailfish goodreads application now