Feedly API

Name: Feedly API API
Brand: Feedly API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData Transformationbearer8 EndpointsREST

For Agents

Pull article streams, fetch entries, run searches, and manage boards in a Feedly account through a bearer-authenticated REST API.

Quickstart

Get started with Feedly API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search feedly content"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Feedly API 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

GET STARTED

Start building with Feedly API API

Explore with Jentic

View OpenAPI Document

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 document for Feedly API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Feedly API 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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Feedly OAuth bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped reference and Jentic injects the Authorization header at execution time, so raw tokens never enter agent or LLM context.

Intent-based discovery

Agents search by intent (e.g. 'search feedly content') and Jentic returns the matching Feedly endpoint with its input schema, including required stream and query parameters.

Time to first call

Direct Feedly integration: 2-3 days for OAuth setup, stream pagination, and search wiring. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

NewsAPI

Lightweight news search API without the curation and boards layer

Choose NewsAPI when you need broad news search but not user-curated feeds and boards.

Complementary

Pocket

Personal save-for-later service that pairs with Feedly for read-it-later workflows

Use Pocket to capture articles for individual reading while Feedly powers shared research streams.

Complementary

Slack

Team chat platform that pairs with Feedly to broadcast curated articles

Use Slack to push the daily Feedly briefing into the relevant team channels.

FAQs

Specific to using Feedly API 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 at https://app.jentic.com/sign-up.

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.