Posts made by jaideep siddula

@Moderator_1 @admin @Moderator_2 @Moderator_3
Hello SmartAPI team,
Hope you're doing great. I have read the complete documentation of the API and have few questions. First, how many sessions can I generate with one API key. Example, with the first session I generate I get a JWT, a refresh token and feed token. Now if I generate a second session, what happens to the all the tokens? Will they be valid? If they're valid, how can I manage these sessions? Second, I am able to establish a websocket connection even after destroying the JWT by calling terminationSession method provided in the documentation. How is this possible?
Thanks in advance.
Yours sincerely,
Jaideep.

@admin @Moderator_1 @Moderator_2
How do I successfully terminate a session. I am using the terminateSession() method to logout. But even after a successful logout message in the response. Session is still in use. I am getting a status code of 200. Please help. How do I check if my session is destroyed or not? It would of great help to all the people using the API and the can be more aware of the sessions generated and managing them. I want to terminate them every day as it is a good practise.
Thanks in advance.
Regards,
Jaideep Siddula

@dhaval0208 Hi, you can use the 'exchange_timestamp' key from the websocket message and call sws.close_connection() accordingly. Hope this helps.
Thank you.
Regards,
Jaideep Siddula

@Mnagesh
Well said!
Thank you,
Jaideep Siddula

@chetansuri Well said!

@subh
https://docs.python.org/3/library/threading.html#module-threading
Check this documentation to write the code yourself. Cheers!

@subh
There would be delay and some data would obviously be missing because there are ingenuities in the API infrastructure. It's about data retrieval.
Regards,
Jaideep Siddula

@Mnagesh
I completely agree with you. There has to be additional support regarding the timeout form the Smart API team.
@Moderator_1 @Moderator_2 @admin

@subh
For sure, bother. I've shared my phone number and email address. Feel free to contact.
Regards,
Jaideep Siddula

@subh
Interesting! Might I ask you for what use case you're planning to use the asyncio module. Would be really helpful if you could share your ideas. Thanks in advance!
Regards
Jaideep Siddula

@Moderator_1
Hello,
Hope you are doing well.
If margin requirements was exceeded, then why would the message 'exchange user id for the user is invalid' is shown in order details instead of 'insufficient funds'. Yes, I have gotten order rejected before due to 'insufficient funds' or margin, and the message in the order details was clear stating the same, i.e. "order rejected due to
insufficient funds. I sincerely request you to please look into it again.
Thank you.
Jaideep Siddula

@Moderator_1
My client code is J50936557. It was just after market open. No, the order wasn't in MCX. It was in NFO. Additionally, I placed multiple orders to buy options, and all of them got rejected with the same message. I also contacted support but, couldn't get any help. Please help.
Thank you.
Jaidee Siddula

@Moderator_1 @Moderator_2 @admin
Today, I have encountered a unexpected message and my order got rejected saying that 'exchange user id for the user is invalid'. In what cases, this happens. I have never experienced this before. Any information is appreciated.
Thank you.
Jaideep Siddula

@Mnagesh @techbytecache @Moderator_2

What I think is yes, there is scope for improvement in the API. I totally agree with you. I am just wondering, have you tried APIs from any other brokers? Would be happy if you shared your experience.

Regards,
Jaideep Siddula

@Mnagesh
Hope you're doing well. You could simply use try, except, finally(If you're using python) statement in your code. So, when a error is raised, the code tries again instead of raising it and ending the program. Hope this helps.

@techbytecache
Time Out Error is raised when the code is executed. The error can be tackled if you're good at handling exceptions and make the code work according to your use case. This comes handy building any application. We can not really depend on the infrastructure of the communication systems. They are bound to fail at times. In this example, you can change in the time out to 15 seconds, instead of 7 seconds which is the default. Cheers!

@techbytecache
It seems there was an error with making a POST request to the specified URL (https://apiconnect.angelbroking.com/rest/secure/angelbroking/historical/v1/getCandleData). The error message indicates a connection timeout issue, suggesting that the connection to apiconnect.angelbroking.com took longer than the specified timeout period (30 seconds in this case).

Error Type: ConnectTimeoutError
Host: apiconnect.angelbroking.com
Port: 443 (standard HTTPS port)
URL Path: /rest/secure/angelbroking/historical/v1/getCandleData
Request Type: POST
Headers: {'Content-type': 'application/json', 'X-ClientLocalIP': 'xxxxxxxxxxxxxxxxxxxxxx'}
Possible reasons could be

Retry: Sometimes, the error could be transient. Simply retrying the request after a short delay might succeed.

Check Network Connection: Ensure that the network connection from your end is stable and there are no issues with connectivity.

Server Status: Check if the server (apiconnect.angelbroking.com) is operational and not experiencing any downtime or maintenance.

Increase Timeout: If this issue persists, you might consider increasing the timeout value in your request to allow more time for the connection to establish.

Contact Support: If none of the above steps work, you may need to contact the support team of angelbroking.com for further assistance, as the issue might be specific to their infrastructure.

Hope this helps.

Regards,
Jaideep Siddula

@coolankurmahe
Brother, it's fixed. Could you please check it once again.
Thank you.

@Moderator_1 @Moderator_2 @admin

I wanted to express my sincerest gratitude for the swift action you took in response to my recent request.

Thanks to your efforts, we were able to recover the necessary data in a timely manner, which has undoubtedly prevented any potential disruptions. Once again, thank you for your quick response and your professionalism are truly valued.

Best regards,
Jaideep Siddula