Python SDK

• 

  List of all Smartapi functions in Python
  • Mnagesh  

  12
  1
  Votes
  12
  Posts
  1297
  Views

  M

  @mnagesh Thnx buddy. May I have any example of gttCancelRule ?
• S

  Difference between status and orderstatus
  • Surya 1  

  6
  0
  Votes
  6
  Posts
  513
  Views

  H

  @admin i'm not getting this difference why both status has same value
• S

  SmartAPI connectivity issue from VPS
  • Shekkil  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• A

  TrailingStoploss in ROBO Order
  • akshita0508  

  3
  0
  Votes
  3
  Posts
  24
  Views

  D

  Check this: def PlaceRoboOrder(self, TradingSymbol, Token, BuySell, Exchange, Quantity, Price, stoploss,squareoff): try: orderparams = { "variety": "ROBO", "tradingsymbol": TradingSymbol, #"SBIN-EQ", "symboltoken": Token, #"3045", "transactiontype": BuySell, #"BUY", "exchange": Exchange, #"NSE", "ordertype": "LIMIT", #"LIMIT",Limit_Market "producttype": "BO", "duration": "DAY", "price": Price, #"19500", "squareoff": squareoff, "stoploss": stoploss-1, #"0", "quantity": Quantity, #"1" "triggerprice" : stoploss, #Price-stoploss "trailingstoploss": 5 } smartApi.placeOrder(orderparams)
• P

  getCandleData rate-limit false positives at ~0.003 req/sec — six independent reports, zero acknowledgment
  • pari  

  2
  0
  Votes
  2
  Posts
  8
  Views

  P

  @admin Tagging you directly for visibility — six independent reports of this exact symptom, across two different endpoints, all well under documented limits, deserves more than the one dismissive reply on topic 5595. Could someone actually look at the server-side rate-limit telemetry for the accounts involved (linked above) and confirm whether this is a known issue?
• D

  SmartApi.smartExceptions.DataException: Couldn't parse the JSON response received from the server: b'Access denied because of exceeding access rate'
  • Deeeepak  

  5
  0
  Votes
  5
  Posts
  18
  Views

  P

  Same issue here — running a Nifty-options intraday bot polling getCandleData (FIVE_MINUTE) once every 5 minutes, ~0.003 req/s against the documented 3 req/s/client cap. Comparing the identical 09:15-10:35 window across three consecutive sessions: 12, then 17, then 27 rate-limit rejections, and the last two days both fully exhausted a 6-attempt retry budget on the very first request of the day, before any other call had been made. That makes six independent reports of this exact symptom now, across two different endpoints — candle data and order book — all well under documented limits: 5636/5637, 5611, 5625, 5595, 5560. I've put together a fuller writeup with the full data here: https://smartapi.angelbroking.com/smartapi/forum/topic/5639/getcandledata-rate-limit-false-positives-at-0-003-req-sec-six-independent-reports-zero-acknowledgment Would genuinely appreciate an actual look at the server-side telemetry rather than another "can't help with your code" response.
• J

  Persistent AB1021 rate-limit error on getCandleData despite low request rate
  • Jay Patel  

  2
  0
  Votes
  2
  Posts
  5
  Views

  P

  Same issue here — running a Nifty-options intraday bot polling getCandleData (FIVE_MINUTE) once every 5 minutes, ~0.003 req/s against the documented 3 req/s/client cap. Comparing the identical 09:15-10:35 window across three consecutive sessions: 12, then 17, then 27 rate-limit rejections, and the last two days both fully exhausted a 6-attempt retry budget on the very first request of the day, before any other call had been made. That makes six independent reports of this exact symptom now, across two different endpoints — candle data and order book — all well under documented limits: 5636/5637, 5611, 5625, 5595, 5560. I've put together a fuller writeup with the full data here: https://smartapi.angelbroking.com/smartapi/forum/topic/5639/getcandledata-rate-limit-false-positives-at-0-003-req-sec-six-independent-reports-zero-acknowledgment Would genuinely appreciate an actual look at the server-side telemetry rather than another "can't help with your code" response.
• J

  Persistent AB1021 rate-limit error on getCandleData despite low request rate
  • Jay Patel  

  3
  0
  Votes
  3
  Posts
  9
  Views

  P

  Same issue here — running a Nifty-options intraday bot polling getCandleData (FIVE_MINUTE) once every 5 minutes, ~0.003 req/s against the documented 3 req/s/client cap. Comparing the identical 09:15-10:35 window across three consecutive sessions: 12, then 17, then 27 rate-limit rejections, and the last two days both fully exhausted a 6-attempt retry budget on the very first request of the day, before any other call had been made. That makes six independent reports of this exact symptom now, across two different endpoints — candle data and order book — all well under documented limits: 5636/5637, 5611, 5625, 5595, 5560. I've put together a fuller writeup with the full data here: https://smartapi.angelbroking.com/smartapi/forum/topic/5639/getcandledata-rate-limit-false-positives-at-0-003-req-sec-six-independent-reports-zero-acknowledgment Would genuinely appreciate an actual look at the server-side telemetry rather than another "can't help with your code" response.
• M

  SmartAPI Token and WebSocket Session Lifecycle
  • manojk3535  

  1
  0
  Votes
  1
  Posts
  3
  Views

  No one has replied

• S

  Invalid symboltoken for commodities
  • Saravanan1209  

  3
  0
  Votes
  3
  Posts
  10
  Views

  X

  CARLOS GOMES ALEXANDRE NETO TOTAL ASSETS AVAILABLE US$ 1.8 BILLION
• S

  Invalid API - AG8004 Even when using a valid API KEY
  • S57010238  

  2
  0
  Votes
  2
  Posts
  10
  Views

  S

  @S57010238 Since login AND placeOrder work but you still get AG8004, the key itself is fine — the failure is scoped to specific endpoints. Which call throws it (getCandleData / market data)? Two verified findings from debugging the same error family after the April migration: generateSession doesn't validate the API key at all, and endpoint groups validate scopes separately — so "logs in fine" (or even "orders work") proves nothing about the data endpoints. The migration replaced the old KEY TYPEs (Trading / Market Feed / Historical) with unified apps, but apps or keys that straddle the migration can still be rejected on some routes. Recreating the app fresh on the new portal fixed it in my case — note you may then hit "Primary static IP is already associated with another app", because deleted legacy apps don't release their registered IPs. Full write-up with the complete fix path + two extra gotchas (the Python SDK prints your API key into error logs; NSE Saturday DR-drill sessions serve mock candles as real data): https://smartapi.angelone.in/smartapi/forum/topic/5635/complete-fix-ag8004-invalid-api-key-after-successful-login-primary-static-ip-is-already-associated-with-another-app If you share which endpoint fails and when the app was created, happy to help narrow it down.
• S

  Complete fix: AG8004 "Invalid API Key" after successful login + "Primary static IP is already associated with another app"
  • saif859  

  1
  0
  Votes
  1
  Posts
  3
  Views

  No one has replied

• H

  Unable to place NFO orders
  • hrishikeshmurali  

  1
  0
  Votes
  1
  Posts
  3
  Views

  No one has replied

• V

  Inconsisten historic data
  • virendramatic  

  4
  0
  Votes
  4
  Posts
  18
  Views

  V

  @admin There is some issue at your end, using for more than 2 years, from may like he said no historical data update. Earlier 15sec/30sec/1min updata used to come, daily historic data used to update but now no.
• R

  GTT orders are failing
  • rakeshkr114  

  2
  0
  Votes
  2
  Posts
  12
  Views

  R

  @admin looks like the gtt api path got prefixed /gtt-service for /createRule, /modifyRule, /cancelRule which is not being allowed by the server and giving 404 with "no Route matched" error. Please look into it if possible. Thanks!
• A

  placeOrder() API returning empty response
  • A50937311  

  1
  0
  Votes
  1
  Posts
  13
  Views

  No one has replied

• S

  Market order placement post new circular from SEBI
  • sudeeshAlgo  

  1
  0
  Votes
  1
  Posts
  9
  Views

  No one has replied

• L

  RuntimeError: Order API error for SENSEX26MAY76400CE: Couldn't parse the JSON response received from the server: b''
  • Loki  

  2
  0
  Votes
  2
  Posts
  9
  Views

  A

  @loki your API request snippet must be sending some incorrect data.
• R

  LTP ISSUE
  • Raman12  

  2
  0
  Votes
  2
  Posts
  6
  Views

  A

  @raman12 You can use market data API to get LTP. Feed token is used in websocket and not in standard APIs.
• C

  Websocket Reconnection
  • Cyriac  

  2
  0
  Votes
  2
  Posts
  11
  Views

  C

  @cyriac @admin please reply....