Feedly API
Agent-ready OpenAPI document · curated by JenticData EnrichmentData Transformationbearer8 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Pull article streams, fetch entries, run searches, and manage boards in a Feedly account through a bearer-authenticated REST API.
Use for: I need to pull the latest articles from a Feedly feed, Search Feedly for articles mentioning a specific competitor, Get a specific Feedly entry by its ID, Save an article to a Feedly board
Not supported: Does not handle feed publishing, podcast hosting, or social posting - use for Feedly stream reads, entry fetches, search, and board curation only.
Jentic publishes the only available OpenAPI specification for Feedly API, keeping it validated and agent-ready. Feedly is a content intelligence and RSS aggregation platform whose API exposes streams, individual entries, search, boards, and enterprise team membership. The eight endpoints in this spec let analysts pull article streams, fetch single entries, run full-text search, and curate boards programmatically - the building blocks for market intelligence, competitive monitoring, and AI-driven research workflows.
Install Jentic One Beta
Connect the Feedly API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Feedly API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffeedly.com%2Ffeedly" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffeedly.com%2Ffeedly" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Feedly API.
Pull stream contents for any feed or category via /v3/streams/contents
Fetch a single entry by ID with /v3/entries/{entryId}
Batch-fetch multiple entries in one call with /v3/entries/.mget
Run full-text search across the user's content with /v3/search/contents
List Feedly tags and boards available to the account
Add articles to a board with PUT /v3/tags/{streamId}
List Feedly Enterprise users and team folders for shared research
Use Cases
Patterns agents use Feedly API for, with concrete tasks.
★ Competitive Market Monitoring
Strategy teams use Feedly as a market-intelligence layer. GET /v3/streams/contents pulls the latest articles from a curated industry feed and POST /v3/search/contents runs targeted searches for competitor names, then PUT /v3/tags/{streamId} saves the most relevant articles onto a shared board for analyst review.
Run POST /v3/search/contents for the competitor name, then PUT /v3/tags/{streamId} for each highly ranked article into the Strategy board.
AI-Powered News Briefings
Newsroom and analyst tools use Feedly content as the source layer for AI summarisation. GET /v3/streams/contents and POST /v3/entries/.mget retrieve the article bodies for downstream LLM summarisation, producing a daily briefing without scraping public sites.
Pull GET /v3/streams/contents for the morning category and pass each entry into the summarisation model, writing the digest into Slack.
Enterprise Research Library
Feedly Enterprise lets a research team share boards across users. GET /v3/enterprise/users and GET /v3/enterprise/folders expose the team and folder structure so an internal portal can render the organisation's curated research without giving every employee direct Feedly access.
List GET /v3/enterprise/users and render their assigned folders from GET /v3/enterprise/folders into the internal research portal.
Agent-Driven Article Curation
An AI agent supporting an analyst can use Jentic to discover Feedly's stream, search, and tags endpoints, run a search for emerging topics, fetch the full entries, and add the most relevant ones to a board for human review - all without holding the raw Feedly bearer token.
Use Jentic to search 'search feedly content' and execute POST /v3/search/contents with the analyst's topic query.
Key Endpoints
8 endpoints — jentic publishes the only available openapi specification for feedly api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/v3/streams/contents
Get stream contents
POST
/v3/search/contents
Search across user content
POST
/v3/entries/.mget
Batch-fetch multiple entries
GET
/v3/entries/{entryId}
Get a single entry
PUT
/v3/tags/{streamId}
Add articles to a board
GET
/v3/tags
List tags and boards
GET
/v3/streams/contents
Get stream contents
POST
/v3/search/contents
Search across user content
POST
/v3/entries/.mget
Batch-fetch multiple entries
GET
/v3/entries/{entryId}
Get a single entry
PUT
/v3/tags/{streamId}
Add articles to a board
GET
/v3/tags
List tags and boards
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Feedly API by hand means handling its OAuth bearer auth and passing the right stream and entry ids into content, search, and tagging calls yourself. Through Jentic you install once, import Feedly from the API Directory, store the token once, and your agent calls it.
Permission scoping
Feedly puts the stream and entry id in the URL path (/tags/{streamId} and /entries/{entryId}), so a rule can pin your agent to one board or entry. You choose the operations it may call, so a write like tagging an entry to a board is included only when you add it, while stream, search, and entry reads can stay read-only.
Credential isolation
Your Feedly bearer token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search Feedly content', and Jentic returns the matching Feedly endpoint with its input schema, including the required stream and query parameters, so the agent calls the right endpoint without browsing the docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Feedly API through Jentic.
Why is there no official OpenAPI spec for Feedly API?
Feedly publishes API documentation on developers.feedly.com but does not provide a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Feedly API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Feedly API use?
Feedly uses OAuth 2.0 bearer tokens issued via the developer console. Through Jentic the bearer is stored in the vault and injected into the Authorization header at call time so the agent never sees the raw token.
Can I search across my Feedly content?
Yes. POST /v3/search/contents runs a full-text search across the user's subscriptions and saved articles, returning ranked entries with their stream context.
What are the rate limits for the Feedly API?
Feedly applies per-token rate limits and returns X-RateLimit headers on responses; numeric limits are not declared in this spec. Apply exponential backoff on 429 responses and check the developer console for the active quota.
How do I save an article to a Feedly board through Jentic?
Run pip install jentic, search 'add article to feedly board', load PUT /v3/tags/{streamId}, and execute it with the entry ID and target board (tag) to file the article.
Can I batch-fetch multiple entries in one request?
Yes. POST /v3/entries/.mget accepts a list of entry IDs and returns the full entries in a single response, reducing round-trips for summarisation pipelines.
Can I limit what my agent is allowed to do with the Feedly API?
Yes. Because you run Jentic One yourself, your own rules decide which Feedly operations and credentials the agent can use. You can keep it to read-only calls like GET /v3/streams/contents, GET /v3/entries/{entryId}, and POST /v3/search/contents, and only add the write PUT /v3/tags/{streamId} when you want the agent to save articles to a board. Since the stream and entry IDs sit in the URL path, a rule can also pin the agent to a single board or entry.
GET STARTED