Best Indian Earnings APIs for NSE/BSE Results in 2026
This comparison focuses on APIs for filed NSE/BSE company results and structured earnings records. It does not rank price feeds, broker trading APIs, or services based on estimated report dates. For scheduled board-meeting dates, see the earnings calendar API comparison; for broader company filings, see the announcement API comparison.
For a developer building a results monitor, Drishti is the closest fit for structured earnings and upcoming-result records with source references. NSE and BSE provide direct exchange data products and filing portals. TrueData offers developer APIs for company announcements and financial data. Choose by checking the exact fields, exchange coverage, delivery contract, and permitted use before wiring it into your product.
Quick answer: which NSE/BSE earnings API should you try?
| Option | Best fit | What to verify |
|---|---|---|
| Drishti earnings API | Structured earnings filings, upcoming-result events, and event workflows | Check the symbol/quarter coverage you need and open the linked source document for important fields |
| NSE Financial Results | Direct NSE filings and exchange-published result data | The public page offers filters and downloads; confirm the separate licensed product and rights for automated or downstream use |
| BSE Self Data Feed | Contracted BSE corporate data and financial products | Register, complete KYC, choose the product, and confirm data-use terms and delivery format |
| TrueData corporate APIs | Vendor APIs for announcements and company financial data | Request the relevant sandbox and confirm NSE/BSE scope, history, latency, and use rights |
“Earnings API” can mean several things. One API may provide the date of a board meeting scheduled to consider results. Another may return a structured filing after the board approves it. A third may provide standardized quarterly line items. Compare the actual response against your job, not just the product label.
What should an Indian earnings API return?
Start by writing down the record your application needs. At a minimum, test these fields:
- company name and a stable identifier, such as symbol, scrip code, or ISIN;
- fiscal year and quarter, not just the date the record reached the provider;
- event type, such as upcoming board meeting or filed financial results;
- standalone or consolidated basis, and audited or unaudited status where available;
- source time, provider ingestion time, and any revision information;
- source document or a reliable way to open it;
- pagination, rate limits, historical range, and access terms.
The quarter-end date and filing date are different dates. The board-meeting intimation is a schedule; the results filing is the actual record to review. Keep them as separate objects and link them by company and quarter.
Drishti: best for structured earnings-event workflows
Drishti documents separate endpoints for upcoming earnings events, earnings filings, filing details, and source attachments. The upcoming endpoint returns board-meeting calendar rows whose purpose mentions financial results. The earnings endpoints are for filings after they appear. That separation makes it useful for a calendar that changes into a filing review queue.
You can retrieve by symbols or scrip codes, then connect records to an internal dashboard, alert, or research workflow. The API also has REST, SDK, OpenAPI, and WebSocket surfaces for teams that need more than a one-off fetch. Start with the earnings reference and the Python SDK.
Choose Drishti when your first requirement is an event record that can be filtered, routed, and connected to its source. Check another source as well if you need a complete standardized fundamentals database or a guaranteed field for every issuer and quarter. Validate several symbols before designing your schema around optional fields.
NSE: best for direct NSE filing records
The NSE Financial Results page lets users filter company results and period, download CSV data, and convert XBRL submissions into Excel. NSE also publishes an integrated financial filing page with quarter-based filtering.
That is useful when you need to inspect the exchange-published record or compare what a vendor returned with the original filing. Do not assume a public web page or a download button is a general-purpose developer API. If your application needs unattended access, storage, or redistribution, ask NSE Data & Analytics about the product and agreement that cover that use.
BSE: best for a contracted BSE corporate-data feed
BSE’s Self Data Feed lists API products for corporate data, including company financials, disclosures, announcements, and corporate actions. The portal describes registration, KYC, product selection, agreement, and payment as part of onboarding. BSE’s information-products tariff sheet also lists corporate products such as financial results and a financial-results calendar.
This is the direct path to evaluate when BSE coverage and an exchange agreement are central to the product. Before building, confirm whether the selected feed contains the exact result types, attachments, fields, history, and delivery mode you need. “BSE corporate data” is a family of products, not one universal endpoint.
TrueData: best for a developer-facing vendor API across company data
TrueData’s API catalogue describes REST and WebSocket corporate-announcement APIs and a separate corporate-data and fundamentals API. Its published material includes financial results, company financial statements, and corporate information.
That makes it a candidate when your application needs vendor-normalized data and more than filings alone. Ask for a sample payload for both NSE and BSE issuers, the historical period, correction behavior, and written rights for your intended display, storage, and redistribution. A successful API response is not itself a licence for every downstream use.
How to compare Indian earnings APIs before choosing
Use a small acceptance test instead of a large feature spreadsheet:
- Pick five companies you actually cover, including one dual-listed issuer.
- Fetch one upcoming-result event and one filed result per company where available.
- Compare identifier, quarter, result basis, dates, source links, and missing values.
- Re-fetch after a revision and check whether you can identify which version changed.
- Confirm rate limits, costs, storage rights, public display, and redistribution with the provider.
NSE’s financial-results surface supports CSV downloads and XBRL conversion, while BSE’s contracted product catalogue includes financial results and calendars. Treat those as distinct delivery options rather than proof that every vendor has identical schemas. (NSE results, BSE product catalogue)
For a monitor that needs to recover after downtime, use REST for bounded backfill and a stream for new events if your plan supports it. Store provider record IDs and source links so an analyst can check the filing. The earnings-monitoring guide covers that workflow in more detail.
How we compared these earnings APIs
We reviewed the providers’ public product pages and documentation for NSE/BSE coverage, scheduled-event versus filed-result records, source links, delivery options, and stated access terms. We did not independently benchmark completeness, latency, or uptime. The “best for” labels describe the documented fit for a job, not a performance ranking. Test your symbols and quarters before relying on any provider.
FAQs about Indian earnings APIs
Is there a free NSE or BSE earnings API?
The exchanges publish filing and calendar pages with downloads, and BSE lists contracted API products. A public download or website is not necessarily an unrestricted API. Confirm automated-access and reuse terms for your use case.
Does an upcoming earnings date mean the results are available?
No. It can be a board-meeting schedule. Wait for the actual result filing, then link it to the scheduled event using the company and quarter.
Can one API provide both upcoming dates and filed financial results?
Some products expose both event-calendar and results endpoints. Test them separately: the date may be revised, the filing may arrive later, and the fields may differ.
What is a sensible first test?
Fetch five symbols across one reporting period, compare the payloads with source filings, and document missing fields and permitted use before expanding coverage.
Try one earnings event first
If your build needs scheduled results events and structured filing records, start with the Drishti earnings API reference. Check one issuer and quarter against its source filing before you build the rest of the calendar.
