Jump to content

ArturCz

Community Member
  • Posts

    8
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by ArturCz

  1. 6 hours ago, andysinclair said:

    I just had the same experience, my API application stopped working overnight with the same error message.

    A pre-emptive warning would have been useful, even just an email to request me to update KYC data would have been sufficient.

    Good to hear that I'm not the only one. IG might listen better if more people have the same issue. Blocking all access to enforce manual action (late at night!) is unacceptable behavior for an API that should be stable and predictable, especially if money is on the line through automated trading.

    • Like 2
  2. Dear IG team,

    I just wanted to quickly mention that my whole software backend connected to IG's Production API failed this night. The reason was "error.public-api.failure.kyc.required". At least the error message was descriptive enough to let me know that KYC information had to be updated for my account. However, to fix this issue, manual action was required and automatic self-healing capabilities were of no use in this case.

    The bad part is: I received no prior warning that KYC information is due for an update. So, out of the blue, API access got fully blocked this night and manual action was required to fix this issue. This is unacceptable behavior. I know IG can do better than randomly blocking all access to the API without any preemptive notice.

    I hope this message reaches someone where the feedback is really taken into consideration so that such a thing doesn't happen again in the future.

    • Like 2
    • Great! 1
  3. After a week this issue seems to be resolved for now, session refreshes are not failing frequently anymore. Seems like the cause of this issue was in IG's backend but got resolved. From the outside I would guess that the backend was overloaded somehow or that there was some internal server logic error. I will revive this thread again if the issue comes back.

    This shows: if you are planning to use an API for automated trading, make sure to try to automatically resolve basic issues with ALL tools available to prevent the trading operation from failing. Fortunately, I had/have the mechanisms in place to handle most quirks of IG's API to literally force the API to function. Otherwise my trading operation would probably have been unusable during the last week.

  4. Hey,

    I'm working with IG's OAuth authentication process to keep an authenticated session in my REST API client. As IG's OAuth access token expires every 60 seconds, I refresh the access token with the provided refresh token every 55 seconds to keep a valid access token at all times (having a look at network traffic in IG's REST API companion, it looks like it's done exactly the same way there).

    However, recently the POST /session/refresh-token v1 interface became very unstable, often throwing error.security.invalid-details or error.security.authentication.timeout. As I use an exponential backoff retry mechanism behind the requests, the requests sometimes works after 3 or 4 retries (after 10ms to 100ms delay before I trigger the next retry). However, sometimes the requests don't succeed at all and I'm forced to create a new session with the POST /session v3 interface (which has worked as a last resort for now).

    Even if I have recovery mechanisms in place to ensure a valid access token, it's a bit odd that POST /session/refresh-token v1 fails this often recently. Session management is the most basic layer of an API and it shouldn't be this unstable.

    I should mention that I run two distinct processes which maintain their own authenticated sessions. But even with two sessions I'm doing 2 non-trading requests per 55 seconds which is well within IG's REST API quotas.

    It looks like the POST /session/refresh-token v1 interface might be overloaded on IG's side for some reason recently. If this is the case it might be helpful that I call attention to this issue here. If this isn't caused by an overload on IG's side I would appreciate some feedback what I should do different (which would ultimately imply that it is not done in the very correct way in IG's REST API companion as well).

    I would appreciate if there is some feedback regarding this issue!

    Best regards,

    ArturCz

  5. Fortunately, the issues seem to be resolved by now. Don't know what went wrong on IG's side but at least everything is working as expected again.

    Here is some constructive criticism from my side which might in the best case contribute to some improvements in the future:

    All in all, I don't like the fact that the contact link on the IG Labs page for API related information is already dead for more than a year and that forum support seems to be a bit sparse. It would not be such a problem if the demo API was down from time to time. But it is a whole other thing if the live API is completely unusable for more than 24 hours and that there seems to be no real way to contact IG with API related issues (which were for sure not caused from my side with buggy requests). There are better ways to handle such situations and maybe IG is willing to improve a bit on it in the future. 👍

  6. There seem to be issues on IG's side as I currently have three different API keys for the demo API. So it is indeed possible to have more than one key, however, the key generation seems to be broken for both the demo and live API right now.

    I also opened another thread because the live API gives me internal server error responses for most API requests at the time which makes the live API completely unusable. It looks like the incident is still not recognized by IG as their status page still shows that everything is operational.

    All in all, I don't like the fact that the contact link on their IG Labs page for API related information is already dead for more than a year and that forum support seems to be rather sparse. It would not be such a problem if the demo API was down time to time. But it is a whole other thing if the live API is completely unusable for more than 24 hours now and that there seems to be no real way to contact IG with API related issues (which for sure are not caused from my side with buggy requests).

  7. Hi,

    since yesterday I am having problems with IG's live API, at least these requests respond with 500 and "errorCode: null" for me:

    • GET /watchlists
    • GET /marketnavigation
    • GET /session

    IG's demo API seems to be fully functional, the issue exists only for IG's live API which is more severe of course.

    I am currently also not able to generate a new API key (live as well as demo) as I get a notification that the key can not be created due to technical problems. As the IG status page shows that everything is operational, are you still aware of some current problems with the live API or might it be a problem which is uniquely linked to my account?

    Looking forward to a statement as soon as possible as the live API is not really usable for me at the moment.

×
×
  • Create New...
us