FAQs on Notis-Access
The NSEIL Online Trade Inquiry System (NOTIS) is a client application/service provided by the Exchange for its Members to receive data for their trade, trade modifications and give-up confirmation on a real time basis.
The Exchange trading system transfers online data to the NOTIS server on real time basis. The NOTIS client application deployed at member end (i.e. using Application Program Interface APIs or EXE based, depending on the segment) sends periodical request to pull the data from the NOTIS server into their application for further processing.
Members can connect to NOTIS API/EXE via Internet or Leased Line.
Capital Market, Futures & Options and Currency derivatives segments can be accessed via APIs whereas Exchange provides a NOTIS EXE application for accessing Commodity Derivatives segment and Securities Lending and Borrowing Market (SLBM).
For accessing NOTIS in CM, F&O and CD segments members need to provide their static IP to the Exchange for whitelisting. The IP shall be whitelisted upon request and member shall be able to access the necessary data from said static IP’s after connecting to the URL’s provided in the API specifications.
NOTIS API can hold ONLY 200 characters for whitelisting of IP's. Accordingly, considering an average number of characters in an IP may range from 11 to 15 digits (eg. the IP: 192.168.1.1 has 11 characters including decimals) 12 to 16 static IPs can be whitelisted respectively.
If the member has a specified list of IP’s from same segment, these can be combined using the asterix symbol ie *.
For example: 192.168.1.1, 192.168.1.2, 192.168.1.3 can be used as 192.168.1.*
By doing this more IP’s can be whitelisted, however limit of 200 characters shall continue to remain applicable.
Yes, the same static IP can be used for all the segments for accessing NOTIS.
No. The static IP is mapped at Member level and hence the same static IP cannot be used for two different Trading members.
Members may access NOTIS for SLBM and Commodity Derivatives segments via Internet, through the Exchange C2N Application Utilities. The member can login with Corporate manager id, add the static IP details which shall be whitelisted and thereafter access the necessary data after logging in the NOTIS EXE.
For members using leased-line connectivity, the WAN IP details at member end need to be provided to the Exchange. The leased line IP shall be whitelisted, and relevant firewall accesses shall be granted post which member shall be able to access the NOTIS API / EXE. Member shall have to change connection parameter in the connection set-up to IP - 172.19.125.70 and port 443 instead of www.connect2nse.com for connecting to NOTIS API Live via Lease Line.
Note: UAT access is not available via Lease Line connectivity
The Exchange protocol document serves as a development guide for trading members to communicate with the NOTIS server thereby enabling download of trade and action inquiries.
Member may refer to the ‘member trouble shooting guide’ for trouble shooting of common errors faced while placing Token/Trade Inquiry API requests.
The latest protocol documents for NOTIS API and trouble-shooting guide are made available on the Exchange website. The same can be accessed by visiting the below link:
NOTIS API for CM, F&O and CDS segment can be accessed by following the below mentioned steps:
- Download the NOTIS API protocol documents and troubleshooting guide from the website as a ready reference for basic queries
- Develop customized front ends or interface with own (members’) internal systems.
- Complete the registration of API and creation of user credentials with the MSD team of the exchange
- Access the UAT Trade Inquiry API Service and complete the testing
- Access the LIVE/Production Trade Inquiry API Service.
The steps to complete the API registration and create user account are as follows:
- Send the registration request to the MSD team on the email ID: email@example.com mentioning the below details
- Member Code
- Member Name
- Contact Person Name, Email Address, and Mobile Number
- Segment for which NOTIS access is required
- Static IP which will be used to access the API
- UAT or LIVE access
Upon receipt of the said details, the admin at NSEIL will verify and generate the user credentials i.e. the Consumer Key and Consumer Secret.
- Once registered, the member/user will be emailed on the registered email id the username & password (Consumer Key and Consumer Secret) to access the token API in order to get token.
- Using this token user can access and start using the Trade Inquiry API.
All timestamps provided via the NOTIS API’s are in Jiffy format. The Jiffy Time conversion utility is a utility tool provided by the Exchange as a ready reference to members for conversation from jiffy format to regular time format.
Members may access the sample jiffy time conversion utility in the ‘member trouble shooting guide’ available on the Exchange website. Members will need to run the java-based file and use it for the necessary time conversion.
The Exchange protocol document provides the detailed manual and technical specifications to be met prior to designing the customized front ends/ interface.
Members are advised to refer the API protocol documents which provide step by step instructions to access Trade Inquiry and Actions Inquiry URL’s. Members are also requested to refer the trouble shooting guide for basic troubleshooting. Alternately members may mail their specific queries to the trade helpdesk at firstname.lastname@example.org or use the helpdesk portal to raise a ticket for their query.
However, members may note the Exchange will not be in a position to comment / guide / assist members on the nature and choice of implementation of the functionalities mentioned in the API specification documents in the applications developed /deployed by the participants. While the Exchange endeavors to provide API specification related assistance on best effort basis for market participants benefit, it is advised that the service should not be used as a surrogate service for development of applications to be deployed at member end.
No. Exchange does not have any approved/empaneled vendor for providing NOTIS API solution to members.
The Exchange does not impose any restrictions on members for use of NOTIS API service to download trade. Members can run multiple instances simultaneously after conducting necessary hygiene checks and following the usage guidelines as mentioned in the API specifications.
As mentioned in the API specifications, please note that when connecting for multiple segments or running multiple instances for NOTIS, the token is to be requested only once and shared for the number of instances being run, since the token generated is common for the member code/credentials. In case multiple tokens are generated on account of duplicate request being received from member end, member may encounter error 500 while accessing the API.
No. The user credentials i.e. consumer key and consumer secret for UAT and LIVE are different. Hence the same consumer key and consumer secret for test scenario cannot be used for live scenario. Members are requested to ensure that they input the consumer key as Username and consumer secret as Password while accessing the API. In case incorrect credentials are used or configured at member end, members will get 401 error in response.
The NOTIS API protocol document provides the detailed instructions to generate token. The steps for generating token to access NOTIS API are as below: -
- Access the below URLs for UAT/Live respectively
- Set the username (consumer key) and password (consumer secret) in Authorization tab
- REST service/API testing can be completed using Postman Tool or Talend API Tester (App from Google Chrome)
Members are requested to note that the token once generated is valid for 9 hours or 32400 seconds. The member should regenerate the token only after current token has expired to continue to request the trade/actions data via NOTIS API. Multiple token generation request even when token is valid may lead to removal of member’s IP from whitelisting.
Member may e-mail the details of the specific query or error to the MSM email helpdesk for necessary troubleshooting. The request should contain the below mentioned details which shall enable the helpdesk team to undertake the necessary analysis:
- Member Code
- Member Name
- Environment: UAT or LIVE
- Static IP from which you logged in on NOTIS API.
- Issue / query in detail with relevant screenshots:
- Observation from Postman tool and exports of requests and response from Postman tool for analysis.
- Name of authorized person:
- Email id of authorized person:
- Contact details:
The issue shall be analyzed by the specialist team and resolution shall be provided to member in due course.
Please be advised that the Exchange shall not be able to provide assistance / troubleshoot issues encountered in internal applications of members. As mentioned in the API specifications, members are required to check in tools like postman / Talend API Tester for analysis from Exchange.
Please refer the API specs for detailed steps and URL for UAT environment in respective segment. Please note that UAT access is not available via Lease Line connectivity.
Please refer the API specs for detailed steps and URL for LIVE/Production environment in respective segment.
Certain scenarios result in removal of IP from whitelist which means that member will not be able to access the API until IP is re-added to the whitelist. The said scenarios are mentioned below:
- Members should limit requests to 15 seconds between each request to the Trade Inquiry API/token service.
- Members should send requests to the API between 6:30 AM to 5:00 AM next day.
Note :- NOTIS services shall not be available between 5:00 AM to 6:30 AM due to maintenance activity.
Certain scenarios result in removal of IP from whitelist which means that member will not be able to access the API until IP is re-added to the whitelist. In such a scenario, the member should request the Exchange to whitelist the IP for resuming the service. In case the above scenarios are not applicable, the member is advised to reach out to the Trade helpdesk toll free number for further assistance or use the helpdesk portal to raise a ticket for their query.
To analyze the same members are advised to capture the observation reported/exported from postman tool and share the same with the trade helpdesk team on email at email@example.com . The issue shall be analyzed by the specialist team and resolution shall be provided to member in due course.
Please note that the original trade messages are downloaded via transcode 6001. Client code modification messages are sent in transcode 5445 in same structure. Please check your implementation for handling of the aforesaid transcodes.
Further for trade modification, in case the buyer / seller broker modifies the trade i.e. client code modification, the trade modification message with transcode 5445 is also being sent to the counterparty broker i.e. seller / buyer without any change of original client code in the modification message. Members need to handle this at their application end.
Please note the current behaviour of NOTIS API in this regard.
- If a trade has been executed in "X" CP code and later modified by the executing member to CP code "Y" and you are a clearing member for "Y" CP code.
- The trading Member shall receive all information of original trade in trades url as well as CP code modification in the Actions URL.
- The Clearing member for CP Code "Y" will receive only the modification information in the Action URL.
- The Clearing Member for CP code "Y" will not receive the original trade information as the trade was executed in CP code "X"
Accordingly, clearing member may check with the executing broker member in case they have done any CP code modification with the Clearing corporation for the trades in question.
This error is generally observed when two tokens are generated for the same consumer key/secret. As the token generated is common for the member code/credentials, members while connecting via NOTIS API, need to ensure that when connecting for multiple segments for NOTIS, the token is to be requested only once and shared for the number of instances or segments being run at member end. The token once generated is valid for 9 hours or 32400 seconds, and members need to regenerate the token only after current token has expired to continue to request the trade/actions data.
This issue could arise in case multiple requests are sent by member for token creation. Please note that the Exchange has rolled out an enhancement for convenience of members w.e.f EOD of May 31, 2021 which allows member to retry after 2 seconds for creation of fresh token after facing such an error. Members need not send any separate communication to the Exchange for reset of the existing duplicate token created.
Error 401 is reported when, either credentials used are incorrect or the request is being sent from IP which is not whitelisted at the Exchange end. Accordingly, members are requested to check these two parameters at their end. Further, the detailed steps with screenshots are provided in the ‘member trouble shooting guide’ made available in the latest protocol documents for NOTIS API. In case the query persists, member may reach out to the Trade helpdesk toll free number and provide relevant details for analysis and further assistance. Members may also use helpdesk portal to raise a ticket for their query.
To resolve the same members are advised to capture the observation reported/exported from postman tool and share the same with the trade helpdesk team on email at firstname.lastname@example.org . The issue shall be analyzed by the specialist team and resolution shall be provided to member in due course.
“This document/FAQ has been drafted in order to ease Member’s/reader’s understanding of the subject matter. The information and/ or content (collectively ‘Information’) provided herein is general information only and NSE has issued detailed circulars to that effect from time to time. While reasonable care has been exercised to ensure that the information is adequate and reliable, no representation is made by NSE as to its accuracy or completeness and NSE, its affiliates and subsidiaries accept no liability of whatsoever nature for any direct or consequential loss, including without limitation any loss of profits, arising from reliance on this Information. The readers are expected to undertake their own diligence and are advised not to solely rely on this document. Any such reliance shall be at the reader’s own risk. Nothing stated herein shall bind NSE, in any manner whatsoever.”