Jump to content

JulianG

Community Member
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

3 Neutral

About JulianG

  • Rank
    Occasional Contributor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. When I try to create an API key, I get the message "We can't update your preferences because of a technical problem. Please try again later.". Has anyone else had any success with this today? Julian
  2. I have a program that uses the REST API. It has a main routine and two threads (written in Python). The main routine and each of the two threads establish their own session using the API (POST /session), then set the account (PUT /session). This has worked fine for months, but for the last few weeks there has been a problem. The first creation of a session and setting the account works as before. However, when the threads come to set their accounts, I get error 401 and message 'error.security.account-token-invalid'. This program goes straight from creating the session to setting the accou
  3. This is fixed now for me in the API companion. I can list accounts and change account. Julian
  4. Get accounts is still not working for me on demo (i.e. using the API companion)
  5. Same problem with me. It also occurs if you use the API companion. I also cannot switch accounts.
  6. Answering my own question ... I had misunderstood how this is meant to work. I assumed that when data was available for a new timestamp, that meant the candle was complete. However, this is not how it works and, of course, not how it works with the online charts. When one candle is complete, price data is immediately available for the next candle even if it is still in progress. Therefore, what I was seeing was a snapshot at a number of seconds into a new candle. Naturally, this data would not be complete and correct until the next candle had started. Julian
  7. In my Python app I submit a /markets GET request for the Epic code. This returns the bid and offer prices, along with lot_size and margin requirement. I am assuming by "spend exactly 1000" you mean commit that much margin (I am mainly familiar with spread betting and CFDs). I calculate my order size by: cash / price / margin / lot_size So, if I have £1,000 available for margin on a CFD, the price is 7,500, the margin 5% and the lot size £2 per point, that means I need to open a position for £1.33 per point. Of course, the price may have changed marginally in the fr
  8. I am fetching 1min prices with an app every minute. I noticed that sometimes, my saved prices didn't match the online chart. Investigating further, it seems if you get the latest 1min price, and then get it again a few minutes later, it's slightly different. It is the same from the online API Companion. Here is a price retrieved from the Companion at 14:19 today, followed by the same data retrieved a few minutes later. You can see that the closing and high prices are different, and also the volume. (This is Epic: IX.D.FTSE.IFM.IP) Is this a predictable behaviour? How long do I need t
  9. I think you need to leave the Epic blank. There reference page says: [Constraint: Set only one of {dealId,epic}] See https://labs.ig.com/rest-trading-api-reference/service-detail?id=542 Also, I'm not sure about the SELL. I've a feeling that I have had to use the same direction as my original trade, but I couldn't be 100% sure. It's worth checking. Julian
  10. Is there a maximum size for the epic code in the API? I have seen in IG a code like "IX.D.FTSE.IFM.IP" but I need the max length for a database field. Many thanks, Julian
  11. I am using the web interface. I have been investigating Heikin-Ashi candlesticks, which look great. However, it appears that indicators like CCI, MACD, RSI and Stochastics change when you switch from standard candlesticks to H-A. Surely the indicators have their definitions which are based on actual OHLC, and shouldn't be calculated based on H-A OHLC? H-A is a smoothing mechanism, not a different way to define prices. Julian
  12. IG documentation says that overnight charges are applicable to daily funded bets and cash CFD positions (https://www.ig.com/uk/charges). Is there any easy way of checking the charge, or the fee percentage when I'm placing the deal? The app and the web page show the margin requirement but it would be useful to have this too. Thanks
  13. I have a share on the web platform that is in a market not currently open (LDL - Lydall). It shows Sell 2027, Buy 2033. I can create an order at price level 2033 with a stop one point away (at 2032). However, in the app when I create the order, it can be a limit order at 2032, or a stop order at 2034. It will not allow me to place an order at 2033 like the web platform. Why the difference? Thanks, Julian
×
×
  • Create New...