Jump to content
  • 0

Client suspended with the APi


sybessonne

Question

Hello, 

I'm a developer. I would like to launch trades automatically with the IG API.

But I'm currently suspended. I can't create a session with the API. I think this is because I use it too much maybe.

I have the message : 

"errorCode": "error.security.client-suspended"

 

Could you explain me how to remove the restriction to be allowed to reuse the API ?

 

Cordially

  • Like 1
Link to comment

5 answers to this question

Recommended Posts

  • 0
On 03/03/2021 at 01:20, sybessonne said:

Hello, 

I'm a developer. I would like to launch trades automatically with the IG API.

But I'm currently suspended. I can't create a session with the API. I think this is because I use it too much maybe.

I have the message : 

"errorCode": "error.security.client-suspended"

 

Could you explain me how to remove the restriction to be allowed to reuse the API ?

 

Cordially

Hi @sybessonne,

It seems that your Demo account is locked (possibly password) once locked it will be suspended. Please reach out to helpdesk.uk@ig.com or use our live chat feature to contact our helpdesk with your account details to unlock your account.

All the best - Arvin

Link to comment
  • 0

Hi all,

I have the same issue where I'm getting a 401 response with a '{"errorCode":"error.security.client-suspended"}'

This WAS on my DEMO credentials (must have been during my integration build, whoops. I did get everything working with my LIVE credentials though)

I since contacted the helpdesk.au@ig.com to share the error code and request they reset my DEMO credentials/account so I can access it ..

Helpdesk.au@ then asked if I was using the right credentials (of course I am) .. 

So I ran a couple of tests using my LIVE credentials to share with helpdesk.au@.ig.com to demonstrate that if you use the right credentials, you actually get a different error.. i.e. you get a 403 error:

- of '{"errorCode":"error.security.invalid-details"}' if you use the wrong password

- of '{"errorCode":"validation.pattern.invalid.authenticationRequest.identifier"}'  if you use the wrong username and password

- of  '{"errorCode":"error.security.api-key-invalid"}'' if you use the wrong API key but the right username and password

In doing so and helping helpdesk.au@ by demonstrating these different codes vs. scenarios I've now locked myself out of my DEMO account - per my original request (which was probably a whoops on my part), and now my LIVE account through using these credentials to demonstrate to them what the error codes are and what they mean.

For noting, I've been using my LIVE API credentials for 2 months now with no issue (so I know my integration is robust) but wanted to get access to the DEMO account to test my automated strategies before deploying into the LIVE environment.

Can someone please help ... I'm not sure that helpdesk.au@ understands the issue (and I mean no offense, just doesn't seem they have documentation to support the difference(s) in error codes etc. and what this code means they need to do at their end?)..

Thanks

Cam

 

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
  • image.png

  • Posts

    • Currently, Bitget wallet stands as one of the most suitable decentralised wallets. It is built with everything incorporated into it, it is the hub of a handy suite of tools that cater to every crypto enthusiast.  It is interesting to note that it has been over 6 years since the platform commenced rendering crypto services. In commemoration of its 6th anniversary, an event has been set up to let its users earn some good amount and merch along with.  The criteria for participation is relatively easy. You just need to join to win exclusive merch, firstly by following @BitgetWallet while adding a RT + Comment #BitgetWallet6Years’’ Similarly, you can give insightful feedback about Bitget Wallet and stand a chance to win Bitget exclusive merch like T-shirt, Cap, Hoodie and Wristband. I will be jumping on this event too. Such an easy peasy way to earn.
    • Basically, they're letting creators mint NFTs and other digital stuff across multiple blockchains at once. Holograph isn't the only one trying to build bridges between blockchains. Projects like Omnibridge and Wormhole are also in the game, each with their own way of moving your digital assets around.  While Holograph focuses on this "native minting" thing across chains, other projects might be a better fit depending on what you need. Doing your research is key! Definitely something to consider. While Holograph recently scored a cool $11 million in funding, omnichain functionality is still pretty new. They've also got some interesting features, just landed on Bitget, and seems to be building an empire state. There could be bumps in the road, so be sure to do your own research and understand the potential risks. So, what do you think? Is Holograph the future of NFTs, or is it just a bunch of hype? Have you tried any other cross-chain solutions? Let's hear your thoughts in the comments!
    • May 22nd marks Bitcoin Pizza Day, a celebration of the first real-world transaction using Bitcoin. In 2010, Laszlo Hanyecz made history by offering 10,000 Bitcoins for two Papa John's pizzas, showcasing Bitcoin's practical potential. The cryptocurrency community commemorates this milestone with various events, including meetups, webinars, and giveaways. Bitget's Pizza Day Raffle is one such event, offering prizes in cryptocurrencies and tokens. Whether you're interested in Bitcoin's history, community, or uses, this event is worth exploring.
×
×
  • Create New...
us