Jump to content
  • 1

Eror with IG API?


blitzjoker

Question

Hi I am getting the following error from the IG API when trying to log in via their Excel interface file:

{“errorCode”:”error.client.accounts.list.generic-error”}

I log in every day this way and have never had this problem before.  Does anyone have any idea how to get round it?

 

Link to comment

29 answers to this question

Recommended Posts

  • 0

One way that I am bypassing this error at the moment is by using the json object that is coming from the AuthenticationResponse. 

Within the response there is one node that contains the Account Info as well as another node that contains all the accounts that you might have. There you can find almost the same information that you would get from the Accounts endpoint.

{
  "accountType": "SPREADBET",
  "accountInfo": {
    "balance": 0,
    "deposit": 0,
    "profitLoss": 0,
    "available": 0
  },
  "currencyIsoCode": "GBP",
  "currencySymbol": "£",
  "currentAccountId": "",
  "lightstreamerEndpoint": "https://apd.marketdatasystems.com",
  "accounts": [
    {
      "accountId": "",
      "accountName": "Spread bet",
      "preferred": true,
      "accountType": "SPREADBET"
    }
  ],
  "clientId": "",
  "timezoneOffset": 1,
  "hasActiveDemoAccounts": true,
  "hasActiveLiveAccounts": true,
  "trailingStopsEnabled": false,
  "reroutingEnvironment": null,
  "dealingEnabled": true
}

  • Sad 1
Link to comment
  • 0

I don't use the Excel add-in. I develop in c# using plain html Rest calls, so I was more talking about the json response from the service itself. I replied to your initial message just to say that I was having the same problem, so you don't get mad :D
But looking at the sample code for Excel provided from IG I can see that there is a Subscription group that handles this call:

 private SubscriptionGroup accountBalanceSubscription;

This object is within the IGApiExcelClient class.

That subscription connects ultimately to the rest endpoint that throws the error, you will need to change it to use the information coming from the authentication response instead of the accounts response. I can image anyway that this error should be fixed very soon. I am expecting it to go away tomorrow during the day.

Can we log this error anywhere that would reach the API team? I saw that you posted the same message on the API forum as well but no one seemed to reply. 

Edited by jlz
  • Sad 1
Link to comment
  • 0

Thanks jlz; I program in vba and could probably use what you have said to maybe delve into a solution, but none of us should have too really.  Still, you are probably right that this will be fixed soon, unless IG have just given up on their API which is always possible.  It's certainly not well supported.  No, I don't know how to report this directly to IG sadly.  I'll have a look tomorrow maybe and report back if I find out more.

 

Link to comment
  • 0

I'm having this problem too.

I'm looking for a work around. I call the API from a .net application. I will advise if I find a solution.

I hope IG supports their API more actively going forward. It's the one feature that provides value add over other brokers

Cheers

 

 

 

Link to comment
  • 0

Thank you to jlz for a work around using the authentication response. Having implemented the jlz approach (under .net) I find now also that the /accounts end point is working again, at least for the Live account.  

 

 

  • Like 1
Link to comment
  • 0
On 19/06/2020 at 14:59, blitzjoker said:

Hi I am getting the following error from the IG API when trying to log in via their Excel interface file:

{“errorCode”:”error.client.accounts.list.generic-error”}

I log in every day this way and have never had this problem before.  Does anyone have any idea how to get round it?

 

 

On 19/06/2020 at 15:09, jlz said:

I am getting the same error.
I tried the API companion at https://labs.ig.com/sample-apps/api-companion/index.html
and it returns the same error you posted as well . I guess we have to wait for it to be fixed, it is a 500 internal server error. We can't do anything. 

 

On 19/06/2020 at 15:58, Mellstock said:

I am having the same problem

 

On 19/06/2020 at 16:21, another_user said:

I'm also having this issue, it was working this morning. 

When trying to GET https://demo-api.ig.com/gateway/deal/accounts I receive this response:

status_code: 500
content: {"errorCode":"error.client.accounts.list.generic-error"}

Not tried in live

 

On 19/06/2020 at 21:05, John_M said:

Yes me too - all my files aren't working

Same 500 error

Not a good time just before a market turn !!

 

On 20/06/2020 at 11:31, Guest rka said:

Same problem here. This seems to be an internal issue.

 

On 20/06/2020 at 08:26, rmwesley said:

Same for me via python ig-markets-api-python-library 

 

On 22/06/2020 at 02:58, BDod said:

I'm having this problem too.

I'm looking for a work around. I call the API from a .net application. I will advise if I find a solution.

I hope IG supports their API more actively going forward. It's the one feature that provides value add over other brokers

Cheers

 

 

 

 

On 22/06/2020 at 08:41, Guest elongden said:

same problem here and neither the demo or the live account works. When can this be fixed?

 

On 22/06/2020 at 08:54, JulianG said:

Same problem with me. It also occurs if you use the API companion. I also cannot switch accounts.

 

Hey everyone,

After speaking with out technical team they confirmed: 

 
I got your case with API on the forums. We have an incident on it INC0455486. So far we have fixed for the live and waiting on demo
 
If you're still experiencing issues with your live account please email us, explain the issues and reference the incident number above. Demo account issues should be resolved within the week. 
 
Apologies for the inconvenience. 
  • Like 1
  • Great! 1
Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • General Statistics

    • Total Topics
      23,033
    • Total Posts
      95,415
    • Total Members
      43,644
    • Most Online
      7,522
      10/06/21 10:53

    Newest Member
    Emperortraders
    Joined 28/09/23 17:49
  • Posts

    • Recently, Bybit shockingly announced the suspension of its services to the UK region due to strict regulatory measures by the region. This action by Bybit could further discourage crypto adoption, which is necessary for developing this industry. Strict regulations have continued to deprive crypto access/adoption to many users for a while. The regulatory bodies normally claim their action is in the interest of their citizens (to protect them from unsuspecting activities that could harm them) while some exchange feel this action is a sinister attack on them so the decision to suspend their service to such region. One question boggled my mind; i) Why can't exchange blend to those regulations? iii) Why are other exchanges surviving in such a region? The crypto industry is still young as such we expect some challenges and differences in opinions but finding a common ground that will ensure its development and growth should be paramount. That is why I feel exchanges and regulatory bodies need to work together for the betterment of this industry. While waiting for that scenario to play out which other exchange will you suggest for the users affected by this decision to use and what are your opinions on this strict regulations
    • hello, just tried IG sinals Intraday and short term and lost £200 ish.. anyone used them ? any help or feedback ?
    • Dow, Nasdaq 100 and CAC40 struggle in early trading Indices are under pressure again as oil prices and bond yields continue to rise. Source: Bloomberg  Chris Beauchamp | Chief Market Analyst, London | Publication date: Thursday 28 September 2023 11:38 Dow eats into Wednesday’s recovery The index briefly slumped to its lowest level since early June yesterday, heading towards the 33,230 level. A rebound from the lows helped to avoid another weak close but the general bearish move remains firmly in place. More losses target the May lows around 32,700. Buyers will be looking for a move back above 33,827 and the 200-day simple moving average (SMA) to suggest that a low has formed. Intraday movement has been capped by the 50-hour SMA over the past week. Source: ProRealTime Nasdaq 100 bounce fizzles The index managed to eke out a small rally yesterday off the lows, but has struggled to push higher in early trading this morning. This has put the price back above the August low of 14,553, so if this holds buyers may attempt to wrest control and drive the index back towards 15,000. A close back below 14,550 would mark a bearish development, potentially open the way towards the June lows at 14,230. Source: ProRealTime CAC40 stuck below previous support After falling just below the 7100 support zone earlier in the week, the index has managed to avoid any further steep losses for the time being. The March lows at 6900 beckon in the event of a fresh drop, while on the upside 7100 could act as resistance in the short-term now it has been broken as support. A longer-term bullish view would require a close back above 7200. Source: ProRealTime
×
×
  • Create New...
us