Jump to content
  • 0

Difference between app and account on non trading API limits


CNDK

Question

Hi IG-team,

I have been experimenting with your api, and dont understand the difference between Per-app and Per-account no trading limits.

image.thumb.png.e009059e0afaf4c13db908fe4d873419.png

The way I read it is that i can make 60 calls per minute per application, and since i have 2 trading accounts those 60 calls are divider over those 2 accounts, so 30 for each. Basically I should be able to make 29 calls from account_1, switch account_2 to my preferred account, and make another 30 calls from account_2, all within 1 minute. 

This doesn't seem to work, so how should I understand the differences between Per-app and Per-account?

Link to comment

9 answers to this question

Recommended Posts

  • 0
17 hours ago, CNDK said:

Hi IG-team,

I have been experimenting with your api, and dont understand the difference between Per-app and Per-account no trading limits.

image.thumb.png.e009059e0afaf4c13db908fe4d873419.png

The way I read it is that i can make 60 calls per minute per application, and since i have 2 trading accounts those 60 calls are divider over those 2 accounts, so 30 for each. Basically I should be able to make 29 calls from account_1, switch account_2 to my preferred account, and make another 30 calls from account_2, all within 1 minute. 

This doesn't seem to work, so how should I understand the differences between Per-app and Per-account?

Dear @CNDK,

Thank you for your post.

Please note that the 60 per app applies to the overall application, and 30 per account refers to individual accounts. You are correct in assuming that you should be able to send a max of 60 (combined - from different accounts) non-trading requests within a minute.

Can you kindly provide the specific error you were receiving so that our technical team can look into it?

Thanks,

Koketso

- KoketsoIG

Link to comment
  • 0

Hi KoketsoIG,

I get the following message: 

"errorCode": "error.public-api.exceeded-api-key-allowance"

I'm trying in the api companion but i get the same error in both prod and demo.

Link to comment
  • 0
2 hours ago, KoketsoIG said:

Dear @CNDK,

Thank you for your post.

Please note that the 60 per app applies to the overall application, and 30 per account refers to individual accounts. You are correct in assuming that you should be able to send a max of 60 (combined - from different accounts) non-trading requests within a minute.

Can you kindly provide the specific error you were receiving so that our technical team can look into it?

Thanks,

Koketso

Hi KoketsoIG,

I get the following message: 

"errorCode": "error.public-api.exceeded-api-key-allowance"

I'm trying in the api companion but i get the same error in both prod and demo.

  • Like 1
Link to comment
  • 0
3 hours ago, CNDK said:

Hi KoketsoIG,

I get the following message: 

"errorCode": "error.public-api.exceeded-api-key-allowance"

I'm trying in the api companion but i get the same error in both prod and demo.

Dear @CNDK,

Thank you for your response.

You are kindly advised to monitor your requests closely and ensure you are not requesting more than the specified limits. 

All the best,

KoketsoIG

- KoketsoIG

Link to comment
  • 0
13 hours ago, KoketsoIG said:

Dear @CNDK,

Thank you for your response.

You are kindly advised to monitor your requests closely and ensure you are not requesting more than the specified limits. 

All the best,

KoketsoIG

Hi KoketsoIG,

The issus is that I don't even reach my limit before I get the error: 

"errorCode": "error.public-api.exceeded-api-key-allowance"

This is my test:

1) In api companion i login to me Live og Demo account (same problem in both environments)

2) I wait for at least a minute to my login doesn't influence the test

3) I make 25 GET /marketnavigation requests

4) I switch the account to my second account with the PUT /session request

5) I should now be able to make 30 GET /marketnavigation requests, but I get the error after just 4 requests

From your previous answer I should be able to make 60 requests per-app per minute, but I can only make 30. 

What am I doing wrong?

  • Like 1
Link to comment
  • 0
2 hours ago, CNDK said:

4) I switch the account to my second account with the PUT /session request

I think there is an issue when switching accounts. I have seen similar behaviour where my request limit appears to be exceeded even though I am only making 2/3 calls. 

There was another thread on this:

But so far no response/resolution.

Can somebody at IG look into this again?

Thanks

  • Like 1
Link to comment
  • 0
On 16/04/2024 at 05:51, CNDK said:

Hi KoketsoIG,

The issus is that I don't even reach my limit before I get the error: 

"errorCode": "error.public-api.exceeded-api-key-allowance"

This is my test:

1) In api companion i login to me Live og Demo account (same problem in both environments)

2) I wait for at least a minute to my login doesn't influence the test

3) I make 25 GET /marketnavigation requests

4) I switch the account to my second account with the PUT /session request

5) I should now be able to make 30 GET /marketnavigation requests, but I get the error after just 4 requests

From your previous answer I should be able to make 60 requests per-app per minute, but I can only make 30. 

What am I doing wrong?

Dear @KoketsoIG

Can you please help me with my question?

Link to comment
  • 0

Hi @KoketsoIG

Does "per app" refer to the IG application, or to a user client application?

My reading of the limits was that "per app" referred to a user application, ie API key. When you request an API key, you have to provide an application name - I always assumed that was the app.

It used to be possible to have multiple API keys per user account, so in that context it would make sense to have a different limit per application AND per account.

But (as I understand it) now it is only possible to have one API key per account, ie one for LIVE and one for DEMO. So now, that limit of 60 per application makes no sense.

Could you check with the API team please? And maybe ask them to update the page showing the limits, so it is more clear?

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

    • 2024 has brought a resurgence back to the gaming project with interest still building up ahead of the anticipated bullrun. Projects like PIXEL, PORTAL, Heros of MAVIA, SAGA and XAI have all performed exceedingly well commanding an impressive market cap.  With the gaming industry projected to reach a total mcap of $100B by the end of 2024, the current $20.3B market cap indicates their is a lot of potential in a lot of gaming project and with Undeads now preparing for its launch, the project has got a lot of mouth wagging as insider information reveals the project is on another level. Pioneering the first craft-to-Earn, Undeads is one of a kind MMORPG survival game built on the Ethereum blockchain and in-game NFTs. With a great team of expatriate and backing from top industry brands, the project is designed to give gamers a complete different gaming experience while enjoying unprecedented rewards. Undeads is beyond the usual P2E gaming project due to its priorities in revolutionizing how gaming project is perceived by offering unparalleled user experience, security and innovation. Not yet listed on any DEX and CEX, the native token of Undeads $UDS just secured its first listing on Bitget. Looking at the successes of PIXEL, PORTAL, SAGA and other gaming projects that have been listed on the exchange this year, am optimistic UDS might be another gaming token that will explode but I will like to hear your reviews about this project.
    • Bitget's May Carnival Event is a standout opportunity in the ever-shifting market. For traders, it's a chance to increase earnings potential. With the possibility of earning up to 15% and the opportunity to snag an Amazon gift card, depositing funds holds the promise of lucrative rewards. In the fast-paced world of cryptocurrency trading, it's wise to explore different avenues. Bitget's May Carnival Event offers attractive returns and added bonuses, catering to traders of all levels. Whether you're looking to grow your investments or expand your knowledge, this event has something for everyone.Therefore, as we keep an eye on market fluctuations, let's embrace the potential advantages that events like Bitget's May Carnival offer. With a strategic approach, we could find ourselves pleasantly surprised by the results.    
    • Traditional staking allows participants to stake assets, and lock them up for fixed periods while they accrue yields for the duration of the stakes. While this may sound great, the fixed locks mean that participants are unable to react to any unpleasant circumstances early enough. Realising this challenge, Bitget has introduced PoolX to deliver flexible staking option, one that allows users to redeem their staked assets from a staking pool whenever they desire. A flexibility that allows users to earn staking rewards without sacrificing liquidity considering that PoolX generate hourly returns. Having earned the trust of users through the juicy APY Bitget Launchpools offer– ZKF and ENA for instance delivered an incredible 329% and 241% APY for a 2 day and 10 day farming period respectively; it is left to be seen if the newly launced PoolX can replicate such yields.  One thing for sure, PoolX is on a mission to redefine the token farming experience with its flexibility and profitability. How excited are you with this product?
×
×
  • Create New...
us