Streams api paging

[Artihunas]

Hi, the  /v3/streams/contents endpoint does not return  continuation field in response.

[David Chatenay]

  Hi,

  Are you passing an access token in the `Authorization` header?

-- 

David Chatenay

Platform Engineer

Feedly

On Wed, Aug 18, 2021 at 5:26 PM Artihunas <arti...@gmail.com> wrote:

Hi, the  /v3/streams/contents endpoint does not return  continuation field in response.

--
You received this message because you are subscribed to the Google Groups "Feedly Cloud" group.
To unsubscribe from this group and stop receiving emails from it, send an email to feedly-cloud...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/feedly-cloud/f1981bd9-22a2-45d7-8a71-9124cf7b283dn%40googlegroups.com.

[Artihunas]

Hi, why  access token? this is a public API endpoint and worked before.

[David Chatenay]

  Indeed! But the APIs that don't require an access token are abused. Heavily. Some people are sending hundreds of thousands of requests per day, sometimes requesting the same feed once a second; ignoring the HTTP/429 responses we send back; jumping IP when they get blacklisted etc...

  We thought about making authentication mandatory for all APIs, but that would have been a bit severe.

  So we now limit the data you can fetch without an access token to the last 50 entries at most, with no continuation. This is consistent with what an RSS feed offers in the first place (you don't get access to the full article history). The rate limits are also stricter than before, and enforced more aggressively.

  I hope this clarifies the changes you are seeing.

-- 

David Chatenay

Platform Engineer

Feedly

To view this discussion on the web visit https://groups.google.com/d/msgid/feedly-cloud/140adbac-f1eb-46ae-9865-739cd981c09bn%40googlegroups.com.