Navigation

    SmartAPI Forum
    • Register
    • Login
    • Search
    • Categories
    • Popular
    • Groups
    • FAQs
    • API Docs

    Historical Candle Data not working as expected

    General Discussion
    0
    2
    57
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      laskshmi last edited by

      GetCandleData API
      Hi,
      I developed a logic during march of this year that would periodically hit the https://apiconnect.angelbroking.com/rest/secure/angelbroking/historical/v1/getCandleData API and it was working fine. I didn't work the project after that. When I tried to run the same now after several months with the below request.

      {
          "exchange": "NFO",
          "symboltoken": "57919",
          "interval": "ONE_MINUTE",
          "fromdate": "2023-11-16 09:15",
          "todate": "2023-11-16 09:15"
      }
      

      I get error response like below.

      {
          "message": "Internal Error",
          "errorcode": "AB2001",
          "status": false,
          "data": null
      }
      

      But when I try

      {
          "exchange": "NFO",
          "symboltoken": "57919",
          "interval": "ONE_MINUTE",
          "fromdate": "2023-11-16 09:15",
          "todate": "2023-11-16 09:16"
      }
      

      I get proper response

      {
          "status": true,
          "message": "SUCCESS",
          "errorcode": "",
          "data": [
              [
                  "2023-11-16T09:15:00+05:30",
                  44390.85,
                  44390.85,
                  44276.6,
                  44300.0,
                  2626
              ],
              [
                  "2023-11-16T09:16:00+05:30",
                  44300.0,
                  44301.7,
                  44275.0,
                  44283.3,
                  1679
              ]
          ]
      }
      

      my question is why does 09:15 to 09:15 doesn't work, but 09:15 to 09:16 works and even 09:16 to 09:16 works, why does the first one doesn't work. This is breaking my logic.

      1 Reply Last reply Reply Quote 0
      • M
        Moderator_1 last edited by

        Hello @laskshmi

        Apologies for the delayed response.
        Thanks for raising this issue. I have raised this issue to tech team and will get back to you once I get a resolution from them. If you have any other issue, please share request and response on smartapi@angelbroking.com.

        Regards
        SmartAPI Team

        1 Reply Last reply Reply Quote 0
        • First post
          Last post