You are using SmartConnect directly from library. Instead create a login function that logs in with the API key like below

ANGEL_API_KEY = your_API_key
smart_api = SmartConnect(api_key=ANGEL_API_KEY)

and you can use smart_api.ltpData(...)

it'll work. You're welcome.

@aabraham19
"Your Client ID","Your PIN","Your totp here")
use pin inplace of password you are ok. write if you cant solve this issue

@gaurang

instrument_url = 'https://margincalculator.angelbroking.com/OpenAPI_File/files/OpenAPIScripMaster.json'

response = urllib.request.urlopen(instrument_url)
instrument_list = json.loads(response.read())

def token_lookup(ticker, exchange='NSE'):
for i in instrument_list:
if i['symbol'] == ticker and i['exch_seg'] == exchange:# and i['symbol'].split('-')[-1] == 'EQ':
return i['token']

token_lookup('NIFTY50')
def symbol_lookup(token, exchange='NSE'):
for i in instrument_list:
if i['token'] == token and i['exch_seg'] == exchange and i['symbol'].split('-')[-1] == 'EQ':
return i['name']

@mahidaparth7 please use 'producttype': 'INTRADAY' instead of 'MIS'

@ananthapad all the orders placed after market go as AMO orders. You can read it here in the place orders section - https://smartapi.angelone.in/docs/Orders

@dave you can use historical API for the same.

historical API - https://smartapi.angelone.in/docs/Historical

To get the token for a scrip of your choice, you can use instruments API.

Instruments API - https://smartapi.angelone.in/docs/Instruments

@tanay1907 There is no such API provided by Angel One.

@tkrshpatel You need to have a Angel One client ID to use the APIs.

If you are already registered with Angel One, you can use your client ID, or else you can sign up for Angel One here - https://www.angelone.in/open-demat-account

@smohit94 You can get only those instruments, whose token is present in the instrument master.

@gaurang You won't be able to trade in such scrips via SmartAPI. You can trade in such scrips via app or web.

@mdzainj you can check the API details on the SmartAPI documentation, an alternate workaround that you asked for would be using websocket 2.0 for your use case.