Jump to content


Community Member
  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About Rick

  • Rank
    Occasional Contributor
  1. Well, as always with these things, if you beat your head against the wall for long enough you can probably fix it 🤣. I realised that the sample code uses the URI /history/transactions/{transactionType}/{lastPeriod} to access the V1 interface. V2 uses a slightly different URI ... just /history/transactions, with variable parameters passed using the '?' construct. I picked this up from the API Companion app, which helpfully shows the generated GET URIs. Then I had to invent a new V2Transaction type ( since the demo code only supports V1) to persuade JSON to deserialise to result for me. Pr
  2. Thanks for responding Andy. Stepping through the code, the relevant section of the IG sample API code can be precised as var client = new HttpClient(); ... if (conversationContext != null) { if (conversationContext.apiKey != null) { client.DefaultRequestHeaders.Add("X-IG-API-KEY", conversationContext.apiKey); } if (conversationContext.cst != null) { client.DefaultRequestHeaders.Add("CST", conversationCont
  3. I'm trying to access /history/transactions v2 via API, in order to retrieve accurate entry and exit times (not supported in v1). I'm writing in C#, based on the API samples, but they only seem to support v1, and not the v2 documented in the Reference guide. Anyone know how to amend the v1 code to make it support v2 ... the call in sample code is public async Task<IgResponse<TransactionHistoryResponse>> lastTransactionPeriod(string transactionType, string lastPeriod) { return await _igRestService.RestfulService<TransactionHistoryRes
  4. Fixed at 21:50 23-Jul ... again from API Companion: "rolloverDetails": null, "newsCode": ".FTSE", "chartCode": "UKX", "country": "GB", "valueOfOnePip": null, "onePipMeans": null, "contractSize": null, "specialInfo": ["MAX KNOCK OUT LEVEL DISTANCE", "DEFAULT KNOCK OUT LEVEL DISTANCE"] }, "dealingRules": { "minStepDistance": { "unit": "POINTS", "value": 5.0 }, "minDealSize": { "unit": "POINTS", "value": 0.5
  5. IG: "Unfortunately, we are experiencing an issue with the Market Data details that are being pulled in the REST API, this is being looked into and a fix is currently in testing. Please bear with us as we look to get this resolved as soon as possible for you"
  6. The REST call for Market Details (/markets/{epic} V2) seems to be returning empty Dealing Rules as of 18-July: they were functioning properly until that point, and give empty details now even using the API Companion (https://labs.ig.com/sample-apps/api-companion/index.html), so I know that it isn't my code. Here's an extract (for FTSE100 DFB) from this afternoon, generated using API Companion ... Any idea what's going on? Rick
  • Create New...