# National Stock Exchange of India

> National Stock Exchange of India Ltd (NSE) is India's largest stock exchange. It exposes its
> trading and post-trade systems to Exchange members and empanelled vendors through published
> protocol documents rather than a public developer portal. There is no OpenAPI, no AsyncAPI, no
> SDK, no Postman collection and no /llms.txt of NSE's own — every interface below is documented
> only as a PDF or ZIP. This file was generated by API Evangelist from NSE's public pages and
> protocol documents on 2026-08-04; it is a third-party profile, not an NSE publication.

## APIs

- [NSE RFQ Web API](https://bricsonline.nseindia.com/rfq): JSON/HTTPS Web API for the
  Request-for-Quote platform for corporate bonds and debt. 41 documented operations under
  `/rest/v1/` covering login/session, RFQ master, market watch, negotiation, deal, deal amendment,
  participant group/limit and portfolio limit. Session token in the `loginKey` header.
- [NSE CBRICS Web API](https://bricsonline.nseindia.com/bondsnew): JSON/HTTPS Web API for the
  Corporate Bond Reporting and Integrated Clearing System. An API-enabled CBRICS user is the
  prerequisite for enabling the RFQ Web API.
- [NSE Offer For Sale (OFS) Web API](https://eofs.nseindia.com/api/): JSON/HTTPS Web API for OFS
  order entry, modification, cancellation and query, plus `GET /messaging/message-stream`. Bearer
  `accessToken` via `POST /auth/token`, renewed with `POST /auth/refreshToken`.
- NSE RFQ FIX Interface: FIX 5.0 (SP2) over FIXT.1.1, TLS with client-certificate authentication.
- Non-NEAT Front-End (NNF), Multicast Tick-By-Tick (MTBT), Drop Copy and Extranet API: binary
  member protocols for order entry, market data broadcast and post-trade file exchange.

## Docs

- [Trading protocols — every protocol document](https://www.nseindia.com/static/trade/platform-services-neat-trading-system-protocols)
- [RFQ Protocol for Web API v1.1.10 (PDF)](https://nsearchives.nseindia.com/web/mediaattachment/2026-07/RFQ_-_Protocol_for_Web_API_-_Ver_1.1.10_20260703110148.pdf)
- [OFS Web API v1.3.4 (PDF)](https://nsearchives.nseindia.com/web/mediaattachment/2026-05/OFS-WEB_API_Ver1.3.4_20260519122437.pdf)
- [WEB CBRICS Protocol v1.16 (PDF)](https://nsearchives.nseindia.com/web/mediaattachment/2026-02/WEB_CBRICS_PROTOCOL_1.16_20260216103027.pdf)
- [NSE RFQ FIX Interface Protocol v1.0.2 (PDF)](https://nsearchives.nseindia.com/web/sites/default/files/inline-files/NSE%20RFQ%20-%20FIX%20Interface%20Protocol%20-%20Ver%201.0.2.pdf)
- [Exchange circulars (how API changes are announced)](https://www.nseindia.com/resources/exchange-communication-circulars)
- [NSE Data & Analytics — data and info vending](https://www.nseindia.com/static/nse-data-and-analytics/data-information-vending)

## Artifacts (API Evangelist, derived from the above — not published by NSE)

- authentication/national-stock-exchange-of-india-authentication.yml
- conventions/national-stock-exchange-of-india-conventions.yml
- errors/national-stock-exchange-of-india-problem-types.yml
- asyncapi/national-stock-exchange-of-india-webhooks.yml
- sandbox/national-stock-exchange-of-india-sandbox.yml
- lifecycle/national-stock-exchange-of-india-lifecycle.yml
- changelog/national-stock-exchange-of-india-changelog.yml
- conformance/national-stock-exchange-of-india-conformance.yml
- packages/national-stock-exchange-of-india-packages.yml
- security/national-stock-exchange-of-india-domain-security.yml
- well-known/national-stock-exchange-of-india-well-known.yml

## Notes for agents

- Access is member-only. Credentials are issued by the Exchange to an enabled member user; there is
  no self-service sign-up, no free tier and no public sandbox key.
- Market data is licensed commercially by NSE Data & Analytics Ltd under a data-vending agreement.
  Redistribution of NSE data without that agreement is not permitted.
- `https://www.nseindia.com/api/*` (e.g. `/api/marketStatus`) is the undocumented JSON surface the
  NSE website itself consumes. It is fronted by an Akamai bot manager that returns HTTP 403 to
  non-browser clients on the site root, and it carries no published contract or terms of use for
  programmatic consumption.
- No idempotency key, no pagination contract, no rate-limit headers and no RFC 9457 problem details
  are documented anywhere in the surface.