The Best Indian Stock Market News APIs for Developers in 2026

If your app follows Indian stocks, the first question is not “Which news API is cheapest?” It is “What counts as news in this product?” A portfolio screen needs company-linked stories. A morning briefing needs India-wide headlines. A filing alert needs an exchange announcement, not a publisher's article about that announcement.
For an NSE/BSE watchlist, Drishti is the most direct fit in this list: its news records can be filtered by symbol or BSE scrip code, and the same platform exposes announcements, earnings, and a news WebSocket. Marketaux is useful when you want a wider publisher feed with entity filters. EODHD combines ticker news with broader market-data products, but test the Indian symbols you need before buying. NewsAPI and GNews are better starting points for general India business headlines than for a company-keyed equity feed.
This is a comparison of documented interfaces and use cases, checked on 22 September 2026. It is not a measured ranking of latency, completeness, price, or editorial quality. We build Drishti.
The five options at a glance
| API | Best fit | Useful filter | Check before you commit |
|---|---|---|---|
| Drishti | Indian-equity watchlists and company news | Symbol, BSE scrip code, sentiment, date | Plan and WebSocket entitlement; test your watchlist |
| Marketaux | Multi-source financial news with entity tagging | Country, exchange, symbol, source | Entity-match quality and article limits |
| EODHD | Ticker news beside historical market data | Ticker, topic, date | News availability for each NSE/BSE symbol |
| NewsAPI | India business headlines and publisher search | Country, category, keyword, domain | No exchange identifier; production licence |
| GNews | India-localised headlines, including regional languages | Country, language, category, query | Country means publisher location, not Indian-stock relevance |
The distinction matters: “India” in a headline filter does not mean “mapped to this NSE or BSE security.” Before choosing a feed, test ten companies from your real watchlist, including at least one dual-listed company and one smaller issuer. Count relevant stories, duplicates, missing symbols, and time from publication to availability. That sample tells you more than a generic provider feature grid.
1. Drishti: best for a company-keyed Indian market news feed
Drishti's news endpoint returns paginated records with title, summary, company, symbol, sentiment, source, link, scrip code, and date when those fields are available. It accepts symbol, scrip-code, sentiment, and time-window filters. This makes it useful for a portfolio panel that asks, “What happened to these companies?” rather than “What is the top business story today?”
Use a server-side request like this to fetch recent news for two companies:
curl -G "https://developers.manasija.in/v1/news" \
-H "X-API-Key: $DRISHTI_API_KEY" \
--data-urlencode "symbols=RELIANCE,TCS" \
--data-urlencode "limit=10"
The Python and TypeScript SDKs expose the same news query. For an alerting app, subscribe to the news product through Drishti WebSockets and use REST to recover a period missed during downtime. REST news pages cost one credit when they return data; live WebSocket access requires a paid plan. Check current pricing and symbol limits against your expected watchlist size.
Drishti also has separate announcements, earnings, and conference-call products. Keep those event types distinct. A news article about a result and the company's exchange filing are related records, not interchangeable sources.
Choose it when: company identity, NSE/BSE context, source links, and a path from recent-news lookup to live alerts matter more than a general-news firehose. It does not place trades or replace an exchange tick-data feed.
2. Marketaux: best for a broad financial-news feed with entity filters
Marketaux's API is built around news articles and detected financial entities. Its /v1/news/all endpoint can filter by symbol, exchange, country, source, language, and publication time. Marketaux also has an India market page, so the India filter is a documented product path rather than a guessed query parameter.
This is a sensible fit if you need to blend Indian company mentions with global market coverage or want to explore which publishers are contributing articles. Ask for entity-filtered results and inspect the entity array, not only the headline: a company name can appear in a story without being the subject of the story.
Check: the number of returned articles per request varies by plan. Measure the entity matching and source mix on your watchlist before designing alert thresholds around it. A tagged publisher article is still not an exchange filing.
3. EODHD: best when news sits beside market-data workflows
EODHD's Financial News API accepts a ticker (s), topic (t), date range, limit, and offset. Its market-data documentation uses exchange-suffixed symbols such as RELIANCE.NSE for Indian historical prices. That shared ticker convention may simplify a dashboard that already uses EODHD prices and fundamentals.
Do not infer from Indian price coverage that every Indian symbol has a useful news history. The public news examples use US tickers. Try the exact NSE and BSE symbols, dates, and companies in your product before treating EODHD as a complete Indian-company news feed. Also account for its documented per-request API-call cost.
Choose it when: one vendor for prices, fundamentals, and news is more valuable than a specialised Indian-news schema, and your sample proves that the news coverage fits.
4. NewsAPI: best for India business headlines, not security mapping
NewsAPI's India business endpoint uses country=in&category=business. Its Everything endpoint searches by keyword, date, domain, and language. This is useful for a market-news page, publisher monitor, or broad “what is being discussed?” search.
The returned article model includes publisher, title, URL, image URL, and publication time. It does not give you an NSE symbol or BSE scrip code as a first-class security identifier. A query for a company name can also catch unrelated namesakes. If you want company alerts, add your own entity-resolution and review step.
The free Developer plan terms limit it to development and testing environments, not staging or production. Check the commercial plan and article-display rights before making it a customer-facing feature.
5. GNews: best for localised headline discovery
GNews offers search and top-headline endpoints with country, category, and language parameters. India (in) is supported, as are English and several Indian languages, including Hindi, Tamil, Telugu, Marathi, and Malayalam. This can help a product that needs a wider view of business coverage across languages.
GNews is a general news API. Its documentation explicitly says the country parameter identifies where articles were published; their contents are not necessarily about that country. It does not promise exchange-symbol tagging. Treat it as discovery, then map and verify any company match yourself.
Choose it when: regional-language and broad headline discovery are the goal. Test source mix and duplication if you intend to merge it with a market-specific feed.
News, filings, and market data are three different inputs
A common integration mistake is to build a “stock news” product from one feed and expect it to cover every market-moving event. Use the source that matches the record:
| Reader question | Input to look for | Why |
|---|---|---|
| “What are publishers saying about TCS?” | Company-linked news | Editorial coverage and context |
| “What did TCS disclose to the exchange?” | NSE/BSE announcement | The issuer's source filing |
| “How did TCS trade after it?” | Licensed price or broker market data | Price and volume observations |
NSE publishes an RSS directory that includes corporate-announcement feeds; BSE offers corporate-data products. Those are useful reference points when evaluating filing coverage, but neither should be confused with an editorial financial-news API. If your app needs both, show the news article and the source filing separately, each with its own timestamp and link.
A practical buying checklist
Run the same short trial against every candidate. Pick a watchlist of ten NSE/BSE companies and a recent trading week. Then record:
- Identity: Can each story be matched to the right company, exchange symbol, or BSE scrip code?
- Coverage: How many relevant stories arrive, and from which publishers? Are smaller companies represented?
- Freshness: Record the original publication time and when your app first sees the story. Do not label a feed “real-time” from the vendor name alone.
- Duplicates and corrections: Do updates arrive as new records? Can you keep a stable article ID or source URL?
- Rights and cost: Check commercial display, storage, redistribution, request quotas, and streaming entitlement in writing.
Start with the narrowest query your product needs. If you're building a company watchlist, try Drishti's news endpoint with real symbols, then add announcements if users also need the underlying filings. If you're building a general India business-news page, test NewsAPI or GNews first. The right API is the one whose records match the question your users will ask—not the one with the longest feature list.

