Jump to content


Community Member
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Benjamin

  • Rank
    Occasional Contributor
  1. When submitting /positions/otc version 2 POST requests, my positions are occasionally getting rejected with reason UNKNOWN. In the account past activity, I find that the result column lists "Rejected: invalid stop or limit". However, the requests I am submitting do not have a stop or limit. The parameters I provide (copied from my Python code) for my API request are as follows: create_position( epic=epic, direction='SELL', size=1, currencyCode='GBP', expiry=expiry, forceOpen=True, guaranteedStop=False, dealReference=None, level=bid, limitDistance=None, limi
  2. Thanks for the info , this makes sense. I have a couple of follow up questions. When making trades via the API, I would like to be sure of precicely what is being traded. Is the preferred/only way to check what a specific EPIC corresponds to, to check its name (e.g. "Daily N225 Cash to keep in range -460 to +460")? If they did, do you happen to know when the DJIA and FTSE tunnels changed in the past, and if possible what these changes were? It would be really useful to be able to query what any given historical data point corresponded to specifically. Thanks
  3.  Thanks for your reply. I'm glad I asked, in that case. I noticed after posting that the REST IG API Companion says "Trading" before the Positions and Working Orders sections in the menu on the left and assumed requests under these headdings were considered trading requests. However, trade confirmation, listing positions and perhaps a few other requests in these sections don't seem to fall into your list. Are you sure these are not also considered trading requests? It would be very useful if the REST API reference specifically clarified this for each request.
  4.  You're welcome - thought I might as well mention it even though it's relatively insignificant. I wondered whether it was delayed, though the timing of it coming through seconds after my second post seemed rather coincidental.
  5. I received the "1st Post badge" immediately after my second post. IG may care to look into this minor issue when they next work on the community forum. I couldn't see a more relevant subforum to post this in.
  6. Which API requests are trading requests, and which are non-trading requests? This is important given that the limits are different for each.
  7. When I first began to use the IG REST API, I believed that EPICs were unique instrument identifiers: that a given EPIC would always correspond to a specific instrument and that this instrument would never change. However, I have recently discovered that this is untrue. For example, there are 19 daily Japan 225 tunnels available, which always have a set of corresponding EPICs of the form BT.D.NIK._.IP, where _ can take a value from 1 to 19. However, the size of tunnel specified by any given EPIC changes. Last week, BT.D.NIK.1.IP was +/-120 points, at the time of posting this it is +/-160 po
  • Create New...