Inoreader integration hits API rate limit too quickly (Premium account) — need OAuth2 / more efficient sync #10

New issue

Closed

opened 2026-03-17 21:23:30 -07:00 by serrebi · 0 comments

serrebi commented

2026-03-17 21:23:30 -07:00

Owner

Hello,

Thanks for BlindRSS — it’s a very interesting tool.

However, I’m encountering a blocking issue with the Inoreader integration.

Problem

Even with an Inoreader Premium account, BlindRSS quickly triggers the error:

Error fetching feeds: Inoreader rate limit active. Retry in 30s.

On the Inoreader developer dashboard for the App ID that BlindRSS forces me to use, the limits are:

API Zone 1: 100 requests / day

API Zone 2: 100 requests / day

My usage shows ~94 requests one day, then 104 the next day, which makes synchronization unusable for normal daily use.

Why this is not viable

BlindRSS appears to require each user to provide their own App ID / App Key, which places everyone under the developer quotas (100 requests/day). With this ceiling, a normal RSS workflow is practically impossible.

Additionally, attempting to “log in with credentials” does not work (invalid_client), which is consistent with the fact that Inoreader’s recommended method is OAuth2.

Expected behavior

Ideally:

Implement OAuth2 (authorization code flow) for Inoreader so BlindRSS can authenticate as the user (not as a developer application), without requiring every user to create an app key.

Implement a more API-efficient synchronization strategy (delta sync / fetch item IDs first, caching, avoid repeated heavy requests).

Respect Retry-After on 429 responses and avoid retry loops.

Steps to reproduce

Configure BlindRSS with Inoreader using an App ID / App Key.

Perform a few normal synchronizations (or simply use the app).

Within the same day, or at latest the next day, BlindRSS hits the rate limit and sync becomes unusable.

Environment

BlindRSS: latest available version

Windows: Windows 11

Inoreader: Premium

Thank you — I can provide logs or test a build if needed.

Hello, Thanks for BlindRSS — it’s a very interesting tool. However, I’m encountering a blocking issue with the Inoreader integration. Problem Even with an Inoreader Premium account, BlindRSS quickly triggers the error: Error fetching feeds: Inoreader rate limit active. Retry in 30s. On the Inoreader developer dashboard for the App ID that BlindRSS forces me to use, the limits are: API Zone 1: 100 requests / day API Zone 2: 100 requests / day My usage shows ~94 requests one day, then 104 the next day, which makes synchronization unusable for normal daily use. Why this is not viable BlindRSS appears to require each user to provide their own App ID / App Key, which places everyone under the developer quotas (100 requests/day). With this ceiling, a normal RSS workflow is practically impossible. Additionally, attempting to “log in with credentials” does not work (invalid_client), which is consistent with the fact that Inoreader’s recommended method is OAuth2. Expected behavior Ideally: Implement OAuth2 (authorization code flow) for Inoreader so BlindRSS can authenticate as the user (not as a developer application), without requiring every user to create an app key. Implement a more API-efficient synchronization strategy (delta sync / fetch item IDs first, caching, avoid repeated heavy requests). Respect Retry-After on 429 responses and avoid retry loops. Steps to reproduce Configure BlindRSS with Inoreader using an App ID / App Key. Perform a few normal synchronizations (or simply use the app). Within the same day, or at latest the next day, BlindRSS hits the rate limit and sync becomes unusable. Environment BlindRSS: latest available version Windows: Windows 11 Inoreader: Premium Thank you — I can provide logs or test a build if needed.