Jump to content

svb

Community Member
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

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

svb's Achievements

Occasional Contributor

Occasional Contributor (2/10)

2

Reputation

  1. Hi, Live account query. Support line didn't answer. I only trade US100 and have already placed 2 live trades this morning (mobile app - spread acct). When wanting to place 3rd trade (which would have been a winner ) I received message saying "Unable to place trade. Instrument not supported on this type of account". Tried 3 more times on mobile, still same. Logged out/in still same. Tried on desktop, worked. back to mobile and then it worked. What caused the error? Status page says system fine. Is this a transient issue related to my account? or global issue? Thanks
  2. if you don't have allowance, for that API key, that's all you'll get. Agree 2.5 sec is more reliable.
  3. improved it by making sure rest calls aren't async and also putting 2 second wait before each call (1 second is not enough and I get more forbidden responses). For what I'm doing this is ok-ish, but not great. Given this is the rest client returning this and not my code I'm not sure what's changed i.e account, service validation. If anyone has any ideas that would be much appreciated, the wait I added, foreach (var market in MarketList) { try { Thread.Sleep(2000); response = await igRestApiClient.priceSearchByNumV2(market, "HOUR", "2"); if (response != null) and the results. only 2 had issues this time, even with 2 second wait. with 1 second I get a lot more. time: 18/03/2021 11:58:01 time: 18/03/2021 11:59:01 time: 18/03/2021 12:00:01 persist 15: 18/03/2021 12:00:01 - CS.D.AUDUSD.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.EURCHF.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.EURGBP.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.EURJPY.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.EURUSD.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.GBPUSD.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.USDCAD.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.USDCHF.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.USDJPY.TODAY.IP persist 15: 18/03/2021 12:00:01 - IX.D.DOW.DAILY.IP persist 15: 18/03/2021 12:00:01 - IX.D.NASDAQ.CASH.IP persist 15: 18/03/2021 12:00:01 - IX.D.SPTRD.DAILY.IP persist 15: 18/03/2021 12:00:01 - IX.D.DAX.DAILY.IP persist 15: 18/03/2021 12:00:01 - IX.D.FTSE.DAILY.IP persist 15: 18/03/2021 12:00:01 - CC.D.DX.USS.IP persist 15: 18/03/2021 12:00:01 - CS.D.USCSI.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.AUDJPY.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.AUDCHF.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.GBPAUD.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.GBPCAD.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.EURCAD.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.USDMXN.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.GBPJPY.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.CADJPY.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.CADCHF.TODAY.IP response is null for CS.D.EURAUD.TODAY.IP 15 persist 15: 18/03/2021 12:00:01 - CS.D.NZDJPY.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.NZDUSD.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.CHFJPY.TODAY.IP persist 15: 18/03/2021 12:00:01 - CS.D.USCGC.TODAY.IP persist 15: 18/03/2021 12:00:01 - CC.D.CL.USS.IP persist 15: 18/03/2021 12:00:01 - CS.D.AUDCAD.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.AUDUSD.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.EURCHF.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.EURGBP.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.EURJPY.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.EURUSD.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.GBPUSD.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.USDCAD.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.USDCHF.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.USDJPY.TODAY.IP persist 60: 18/03/2021 12:00:01 - IX.D.DOW.DAILY.IP persist 60: 18/03/2021 12:00:01 - IX.D.NASDAQ.CASH.IP persist 60: 18/03/2021 12:00:01 - IX.D.SPTRD.DAILY.IP persist 60: 18/03/2021 12:00:01 - IX.D.DAX.DAILY.IP persist 60: 18/03/2021 12:00:01 - IX.D.FTSE.DAILY.IP persist 60: 18/03/2021 12:00:01 - CC.D.DX.USS.IP persist 60: 18/03/2021 12:00:01 - CS.D.USCSI.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.AUDJPY.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.AUDCHF.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.GBPAUD.TODAY.IP response is null for CS.D.GBPCAD.TODAY.IP 60 persist 60: 18/03/2021 12:00:01 - CS.D.EURCAD.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.USDMXN.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.GBPJPY.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.CADJPY.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.CADCHF.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.EURAUD.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.NZDJPY.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.NZDUSD.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.CHFJPY.TODAY.IP persist 60: 18/03/2021 12:00:01 - CS.D.USCGC.TODAY.IP persist 60: 18/03/2021 12:00:01 - CC.D.CL.USS.IP persist 60: 18/03/2021 12:00:01 - CS.D.AUDCAD.TODAY.IP time: 18/03/2021 12:03:01
  4. just do a price request and you'll see allowance in response. "metadata": { "allowance": { "remainingAllowance": 4602, "totalAllowance": 10000, "allowanceExpiry": 442401 },
  5. Hi, C# : use combination of REST & streaming. Replicated using WPF example that you can download in labs. This issue is specific to REST Every 15 minutes I get 15 min prices for a range of epics. My allowance is fine with +6500 left. I keep getting random null responses with "forbidden" status code. Different epics. If I trap null response and then set rest call to execute again, it works. I continue and it carried on with rest of epics, or will do say 10 , return forbidden for 3 and then return fine for epics following that. if I step through each epic, its fine. So seems to be some timing glitch. Tried trapping and adding task.delays and retries, but still null. I have to actually break and step over. Given its not my allowance, are there any quirks with REST calls to cause this? This is example, does some, throws forbidden and then fine for AUDCAD again. persist 15: 17/03/2021 22:15:01 - CS.D.CADJPY.TODAY.IP persist 15: 17/03/2021 22:15:01 - CS.D.CADCHF.TODAY.IP persist 15: 17/03/2021 22:15:01 - CS.D.EURAUD.TODAY.IP response is null for CS.D.NZDJPY.TODAY.IP 15 response is null for CS.D.NZDUSD.TODAY.IP 15 response is null for CS.D.CHFJPY.TODAY.IP 15 response is null for CS.D.USCGC.TODAY.IP 15 response is null for CC.D.CL.USS.IP 15 persist 15: 17/03/2021 22:15:01 - CS.D.AUDCAD.TODAY.IP I cannot replicate forbidden status response in REST companion for any epic either, just seems when run via rest client Thanks
  6. Nevermind. now to figure why I ran out by wednesday! { "errorCode": "error.public-api.exceeded-account-historical-data-allowance" }
  7. I have been running C# implementation for quite some time. last night it stopped working and response is null 403 forbidden. This is on live account. Can use API to log in (rest and streaming) make calls to get watchlist epics, for example. As soon as I call to get prices (e.g. igRestApiClient.priceSearchByNumV2) I get forbidden. looking at reference I don't see forbidden with null response. any ideas as to potential cause? this is something I usually start running on Sunday night and turn off on Friday night each week. It has done this for many weeks and previously ran ok against demo. thanks
×
×
  • Create New...
us