bug-or-feature

UPDATE: I told the Web API team about this issue via their email address webapisupport@ig.com. Their reponse was: we know about this, it's not a bug. The excuse was and then My interpretation is: it has been like that since the API was released. They know its wrong, but to change it now would admit the mistake. So for now, the laborious workaround mentioned above is the only solution. Maybe if enough people make a noise about it, they will fix it. But I doubt it

There's a section in the FAQ about the API limits https://labs.ig.com/faq Note that the limits described there are for the LIVE environment. The limits in DEMO are different, less, and variable. In my experience though, you still get 10,000 price points per week for historical data

Price data is paged, and the default page size is 20. It is all in the docs https://labs.ig.com/rest-trading-api-reference/service-detail?id=682

I've done a bit more digging - I think there is a bug. And now I understand the issue as described by @SZZ It looks to me like the /confirms endpoint returns the wrong dealId when closing a position. The Streaming API also reports the wrong dealId from the TRADE Subscription. They both respond with the dealId of the opening trade instead of the closing trade. The correct closing trade dealId is reported by the /history/activity endpoint, and by the /history/transactions endpoint. So there is a workaround for your issue right now @SZZ . Once your trade is closed, look at the response of the /history/activity endpoint. Find the dealId where the affectedDealId is the ID of the opening trade, and description is "Positions/s closed: XXXXXXXX". Then lookup that dealId in the response of the /history/transactions endpoint, with field name reference. I have reported this to the webapi team, will post any updates here

Hmm not sure what is going on. My previous examples were market orders. I just tried a working order, and the transaction response contained the full 15 character reference field, eg DIAAAANXXXXXXXX Maybe someone from IG can explain. Why does the reference field in the /history/transactions response sometimes contain the full dealId, and sometimes just the portion after DIAAAAN?

@ColinAgbabiaka I'm not sure about any DEMO env bug - my example responses were from DEMO too. My responses were from futures based spread bets, dated. Yours looks like an undated CFD, is that correct?

INFO:trading_ig.rest:GET '/history/activity/', resp 200 date marketName epic period level direction dealId 0 2023-11-10T05:45:05 Oil - Brent Crude EN.D.LCO.Month6.IP JAN-24 8034.5 SELL DIAAAANP68C8YAQ 1 2023-11-09T05:45:11 10-Year T-Note Decimalised IR.D.10YEAR100.Month2.IP DEC-23 10845 BUY DIAAAANPPY34SAG INFO:trading_ig.rest:GET '/history/transactions', resp 200 openDateUtc dateUtc instrumentName period openLevel closeLevel size reference profitAndLoss 0 2023-10-27T18:59:23 2023-11-10T05:45:05 Oil - Brent Crude JAN-24 8923 8034.5 +0.53 DIAAAANP68C8YAQ £-470.91 1 2023-09-26T17:17:04 2023-11-09T05:45:11 10-Year T-Note Decimalised DEC-23 10814.4 10845 -0.62 DIAAAANPPY34SAG £-18.97 The dealId field from the activities endpoint (/history/activity) matches the reference field from the transactions endpoint (/history/transactions)

Ah, well firstly "all the indices on IG" is a lot less than "all the pricing data". It's still a lot. Spread bets, CFDs, something else? A lot depends what your hypothesis is. Are you investigating spread values? If so, you could get the prices from somewhere else, and sample the IG spread using the Streaming API. With that API you can be subscribed to 40 instruments concurrently. See here Platform choice is a big subject, probably not a question for this forum - I'm sure you have great Google skills being a researcher. But you could start with Yahoo Finance, Google Finance or AlphaVantage

Thanks @KoketsoIG Can you ask the dealing desk to make them consistent please?

Yes, there is. Once your account is open, there is a page with all the referral info, linked from the My IG section. Mine says "For a limited time, you’ll get £50 for each friend who signs up for an investment account and £200 for trading account opens – up to a maximum of £1000", and has a link to the T&Cs

https://labs.ig.com/

My advice would be to not attempt to do anything like this. "All the pricing data at 1min resolution" is an absurd amount of data. The IG platform is not a good place to try anything like this, due to the number of markets on offer, and the rate limitations. There are plenty of other platforms where you can obtain financial pricing data, either paid or free

Hi Why are minimum bets on futures based spread bets and forwards inconsistent between DEMO and LIVE environments? Examples: Natural Gas: DEMO £1.00, LIVE £0.50 Hong Kong HS50: DEMO £0.50, LIVE £0.10 USD/CAD Forward: DEMO £0.50, LIVE £1.00 It would be much easier for your customers to design and test strategies on the platform if minimum bet sizes were consistent I'd appreciate a response from someone at IG many thanks Andy

@KoketsoIG FYI the undated bet is still £0.10

@KoketsoIG Thanks

Can someone from IG respond please?

What is going on with the minimum bet for 'Sugar - London No.5'? The December contract is 10p, but later contracts are £15.00. Can someone from IG please clarify? Thanks Andy

If you are keeping bets open for more than a few days it is usually more cost efficient to make a fixed expiry bet. Sometimes they are referred to as Futures or Forwards bets. There is no overnight charge, but the spread is a bit wider, and the bets expire on a specified date. There is some info about the charges here. To see the chart and info for these bets, click the "Futures" drop down next to "Undated" (aka "Spot") in the window header. Natural Gas does not have any trading hours restrictions. Some bets do, they have an extra section called "Trading Hours" at the top of the Info tab in the side bar. See "Cocoa - London" for an example

There is no extra cost associated with auto renewal of futures or forward bets, the cost is built into the spread. Its just as if you did it manually yourself. There's info on the charges here

Confusing response. Are you trading spread bets, CFDs or shares? You can only trade spread bets and CFDs with the REST API You can only trade CFDs and shares with L2 Dealer EC.D.ATOFP.CASH.IP is a spread bet epic

Thanks @AshishIG

Look at the REST API docs, you can see there is no endpoint with URL /workingorders/dma/equity. The endpoint for making OTC working orders is /workingorders/otc. That is why you are getting a 404 error

@AshishIG Thanks. Its great that the individual contract is now tradeable, but I'm more concerned that the underlying problem has not been addressed. It would be preferable if this sort of issue was detected automatically, rather than relying on your users to report it

There is a problem with the High Grade Copper bet for the DEC-23 futures contract. It is possible to place a bet on the SEP-23 contract, even though it expires very soon (just over 24 hours at the time of writing), but not possible to place a bet on the DEC-23 contract. The web interface shows a message that says "Closing only: Contract due to expire", despite the expiry being three months away. Even worse, the REST API reports the DEC-23 contract as TRADEABLE. This problem looks very much like the one reported here, which, at the time @AshishIG reported as "has been rectified". Clearly not See attached screenshots

Thank you @AshishIG