API: read your feeds, folders, tags and articles from your own code
Your own code can reach everything Inoreader collects for an account, including subscriptions, folders and tags, the articles of any stream, unread counts and monitoring feeds. It all comes through a documented REST API with OAuth 2.0.
Read the API documentation- ProAPI access is included in Pro.
- TeamTeam plans include it too, with one shared application for the whole team.
What it does
With the Inoreader API, your own code can work with an Inoreader account. Your program can list the subscriptions, folders and tags, read the articles of any stream with paging and filters, read and change the unread state, tag and save articles, add feeds and create monitoring feeds. The responses are JSON in a format that generations of feed reader clients already know, so existing libraries and code often fit with little change.
Applications that other people use sign in with OAuth 2.0, through a consent page on Inoreader and refresh tokens. Scripts that act on your own account can use a client login instead. You register each application in the developer panel in Preferences, which also shows its daily limits and usage. Higher limits come with Custom plans.
The Zapier, IFTTT and n8n integrations are built with it. If an integration platform runs out of options for what you need, the API is the next step.
How it works
- On a Pro or Team account, open Preferences, Developer, and create an application. Note its app ID and key.
- Read the authentication guide and implement OAuth 2.0, or use the client login for a script that works on your own account.
- Call the methods you need, such as the subscription list, stream contents, unread counts and edit tag. Each one is documented with a request and a response.
- Watch the usage in the developer panel. The rate limit headers on every response tell your code when the daily quota resets.
What people use it for
Building a newsroom dashboard
Read your media team's monitoring feeds every minute and show them on a wall screen.
Running a content pipeline
Your editors tag articles in Inoreader, and a script pulls them and publishes them to a website or a newsletter tool.
Building a client for a platform we do not cover
Write a reader for a desktop or a device we do not cover, with the same subscriptions, folders, tags and read state as your account.
Frequently Asked Questions
What can the API do?
It can list and edit subscriptions, folders and tags, and read the articles of any stream, such as a feed, a folder, a tag, your saved articles or your unread ones. It can also get unread counts, mark articles as read, tag them, add feeds and create monitoring feeds. The developer portal lists every method with examples.
How do I get access?
Register an application under Preferences, Developer, on a Pro or Team account. You get an app ID and key, along with usage statistics for the last 30 days and the daily limits of your app.
How do users sign in to my app?
Through OAuth 2.0. Your app sends the user to a consent page on Inoreader and receives an access token and a refresh token, so the user never types their password outside Inoreader. For scripts that only act on your own account, there is also a simpler client login.
What are the limits?
Each app can make 100 calls a day in each of the two method zones. Every response reports the usage and the reset time in its headers. Higher limits are available on Custom plans.
Is there a Team application?
Yes. Every Team plan includes one shared application that all members can use. More applications and higher limits are available as add-ons.
Where is the documentation?
At inoreader.com/developers. There you will find every method with its parameters and responses, the authentication flows, the ID formats and the rate limits. You can send questions to [email protected].
From the help center
From the blog
Build your own newsfeed
Ready to give it a go?
Start a 14-day trial, no credit card required.