Best NSE/BSE Company Announcement APIs for Earnings Season
This comparison covers company-announcement feeds and filing records, including earnings-season notices and results. It is broader than a financial-results-only API and narrower than the full alert-delivery workflow. See the earnings API comparison for result records and the stock-alert API comparison for routing and delivery.
For an application that needs structured Indian company events, Drishti and TrueData both document developer-facing APIs for corporate announcements. NSE and BSE provide exchange-level records and contracted data products. The right choice depends on whether you need a source portal, a licensed feed, or an application-ready event stream.
Quick answer: best announcement APIs for Indian companies
| Option | Best for | Interface and data | Main check |
|---|---|---|---|
| Drishti announcements | Structured company announcements for APIs, alerts, and research workflows | REST, WebSocket, SDKs, category filters, and source references | Check product access, source link behavior, and symbol coverage |
| TrueData Corporate Announcements API | Vendor-delivered NSE/BSE filings with REST and WebSocket options | Corporate announcements, results, meetings, and other disclosures | Confirm latency, history, schema, product entitlements, and reuse rights |
| NSE Corporate Filings | Directly checking NSE-published notices and result records | Search filters, attachments, CSV options on relevant views, and filing details | Public browsing is not equivalent to an API licence |
| BSE Self Data Feed | Contracted BSE corporate-data APIs | Corporate data, financials, disclosures, announcements, and actions | KYC, product agreement, scope, and delivery format |
The exchanges publish company-submitted information. NSE explicitly notes that announcements are displayed on receipt and that the company is responsible for their accuracy. Your interface should preserve attribution rather than implying the exchange independently validated every claim. (NSE filings)
What counts as a company announcement API?
An announcement API gives software a way to retrieve or receive records about listed companies. It may return a filing headline and category, a detailed record, an attachment reference, or a WebSocket event. Those are different levels of access.
For earnings monitoring, check whether the provider distinguishes:
- board-meeting intimation from meeting outcome;
- financial results from a newspaper publication or investor presentation;
- original filing from a later revision;
- NSE-listed identifier from BSE scrip code;
- provider ingestion time from the company or exchange source time.
The NSE event calendar and filing pages can help validate the meaning of a record. They are also a reminder that an announcement is not automatically the underlying financial statement in a normalized table.
Drishti: best for structured events and application workflows
Drishti’s announcements API supports filtered discovery, category lookup, detailed records, and source-document resolution. Its WebSocket guide describes an announcement stream alongside a REST endpoint, so a service can recover a recent window through REST and listen for new records through a stream.
That split is useful for a company watchlist, filing queue, or research workflow. Store the provider ID and event category, link the event to a company and period, and retain a source link for review. If a downstream user opens a filing, resolve the source document at that point rather than making an unsupported PDF URL from a headline.
Drishti is the strongest fit here when the job is structured Indian filings rather than broad price ticks or order execution. Start with the API reference and WebSocket setup.
TrueData: best for vendor-delivered live corporate announcements
TrueData describes its Corporate Announcements API as a REST and WebSocket feed for NSE and BSE exchange announcements. Its published examples include categories such as financial results, board meetings, corporate actions, and business disclosures. The provider also documents a separate corporate-data API for company fundamentals.
This can fit a team that wants a vendor feed and its own event rules. Request test credentials and ask for representative payloads covering a result intimation, the actual result, and a revision. Confirm both the timestamp semantics and the rights for public display or redistribution. A vendor’s exchange authorisation does not tell you which uses your particular contract permits.
NSE: best for validating direct NSE submissions
NSE’s corporate filings surface lets visitors search company filings and inspect details and attachments. The exchange also has dedicated views for financial results, board meetings, and the event calendar.
These are useful reference sources and may fit a human review workflow. For a commercial application, ask about the licensed feed rather than treating the public interface, page data, or a CSV download as permission to automate and republish it.
BSE: best for contracted BSE corporate data
BSE’s Self Data Feed lists Corporate Data API products covering company financials, disclosures, announcements, and actions. BSE’s product tariff sheet separately lists corporate products such as announcements, financial results, and the financial-results calendar.
That is a direct exchange-data path to evaluate for BSE records. Before committing, request the feed manual, sample messages, historical availability, identifiers, timestamps, and current usage terms. Verify whether the selected product is a live event feed, a download, or a calendar dataset.
How to prevent duplicate and confusing alerts
Treat each filing as an event with a stable record ID, company identifier, category, source time, ingestion time, and source link. For a result cycle, connect related events rather than overwriting them:
Board-meeting notice → meeting outcome → financial result → revision (if any)
An update should create a new version or linked event. Keep the old one for audit, then route the latest record to a reviewer. If your connection was down, recover a bounded period with REST before relying on the live stream. The broader earnings-monitoring workflow explains recovery, deduplication, and review queues.
How we compared announcement APIs
We compared documented exchange coverage, record categories, REST or streaming access, source-document handling, and the need for a separate data agreement. We did not independently test feed latency, historical completeness, or correction delivery. The “best for” labels describe workflow fit; confirm the exact payload and rights with the provider.
FAQs about NSE/BSE announcement APIs
Does NSE provide a public announcements API?
NSE publishes corporate-filings pages with searchable records and downloads on some views. That does not by itself establish a general public API or permission to republish the data. Ask about the applicable exchange product and agreement.
Are financial results and corporate announcements the same feed?
Financial results are one kind of company filing. A broader announcement feed can include board meetings, corporate actions, disclosures, and other subjects. Check the category fields and source records.
Should I poll or use WebSockets?
Use REST or a supported download for backfill and recovery. Use a WebSocket where you need live delivery and your plan permits it. Even with a stream, persist IDs and recover missed records after a disconnect.
Can I publish an announcement in my own app?
That depends on your provider’s contract and the exchange’s applicable terms. Confirm storage, public display, redistribution, and derived-data rights in writing before launch.
Test a single result cycle
Choose one company, retrieve its board-meeting notice and resulting filing through your selected source, then verify both against the source record. If the fields, identifiers, and rights fit, scale the same flow to the rest of your coverage list.
