Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. I tried the url provided by you, but was not able to get the Streaming to work. Also tried to check out the version 7.03, there is no such version. It is 7.0.3 but even that didnt work. Finally got the lightstreamer-client version 7.2.4 from NPM registry and i was able to get the ls Client up but there was an issue with the Subscription. So downgraded and tried other versions. Finally 7.2.2 version of lightstreamer-client from the NPM registry worked and now have the streaming up and running. Hope this helps anyone who is trying to get the streaming working for Forex.com . Kind Regards, Aniket.
  3. Last week
  4. Its my real money account. Thanks for the help regards
  5. Watch List Client api code

    Hi Brutsi, Are you using a demo / test account or is it your live real money account? The "Watch List Client" message means that restrictions have been placed on the account, which does not normally happen with test accounts. I do not have access to client account information so cannot check the reason why there are restrictions on the account. Please contact Client Services who do have access to account information. Kind Regards, PM
  6. Hello dg97, Unfortunately no. Once a market is expired it is no longer on our Live databases so cannot be queried via the API. Kind Regards, PM
  7. Watch List Client api code

    Hi Brutsi, Thank you for the details. We'll look into it and reply to you when we have a response. Kind Regards, PM
  8. Hello, Is there any way to find Market ID's for expired markets? ListMarketSearch returns only current (non-expired) markets, e.g. Copper (per 0.05) May 21 CFD, which has relatively short data history for testing purposes. Thanks.
  9. Earlier
  10. Here is an example json of what i send {"OcoOrder": null, "ExpiryDateTimeUTC": null, "Direction": "buy", "BidPrice": 13187.9, "MarketId": "99502", "OfferPrice": 13188.9, "Quantity": 1, "PositionMethodId": 2, "PriceTolerance": 1, "IfDone": [{"Stop": {"TriggerPrice": 13173.0, "Direction": "sell", "MarketId": "99502", "Quantity": 1}, "Limit": {"TriggerPrice": 13288.4, "Direction": "sell", "MarketId": "99502", "Quantity": 1}}]} And here is what i receive {'Status': 3, 'StatusReason': 95, 'OrderId': 782250860, 'Orders': [{'OrderId': 782250860, 'StatusReason': 140, 'Status': 8, 'OrderTypeId': 1, 'Price': 13188.9, 'Quantity': 1.0, 'TriggerPrice': 0.0, 'CommissionCharge': 0.0, 'IfDone': [{'Stop': {'OrderId': 782250862, 'StatusReason': 1, 'Status': 1, 'OrderTypeId': 2, 'Price': 0.0, 'Quantity': 1.0, 'TriggerPrice': 13173.0, 'CommissionCharge': 0.0, 'IfDone': [], 'GuaranteedPremium': 0.0, 'OCO': None, 'AssociatedOrders': {'Stop': None, 'Limit': None}, 'Associated': False}, 'Limit': {'OrderId': 782250861, 'StatusReason': 1, 'Status': 1, 'OrderTypeId': 3, 'Price': 0.0, 'Quantity': 1.0, 'TriggerPrice': 13288.4, 'CommissionCharge': 0.0, 'IfDone': [], 'GuaranteedPremium': 0.0, 'OCO': None, 'AssociatedOrders': {'Stop': None, 'Limit': None}, 'Associated': False}}], 'GuaranteedPremium': 0.0, 'OCO': None, 'AssociatedOrders': {'Stop': None, 'Limit': None}, 'Associated': False}], 'Quote': None, 'Actions': [{'ActionedOrderId': 0, 'ActioningOrderId': 0, 'Quantity': 1.0, 'ProfitAndLoss': 0.0, 'ProfitAndLossCurrency': None, 'OrderActionTypeId': 1}], 'ErrorMessage': None} {'Status': 3, 'StatusReason': 95, 'OrderId': 782250860, 'Orders': [{'OrderId': 782250860, 'StatusReason': 140, 'Status': 8, 'OrderTypeId': 1, 'Price': 13188.9, 'Quantity': 1.0, 'TriggerPrice': 0.0, 'CommissionCharge': 0.0, 'IfDone': [{'Stop': {'OrderId': 782250862, 'StatusReason': 1, 'Status': 1, 'OrderTypeId': 2, 'Price': 0.0, 'Quantity': 1.0, 'TriggerPrice': 13173.0, 'CommissionCharge': 0.0, 'IfDone': [], 'GuaranteedPremium': 0.0, 'OCO': None, 'AssociatedOrders': {'Stop': None, 'Limit': None}, 'Associated': False}, 'Limit': {'OrderId': 782250861, 'StatusReason': 1, 'Status': 1, 'OrderTypeId': 3, 'Price': 0.0, 'Quantity': 1.0, 'TriggerPrice': 13288.4, 'CommissionCharge': 0.0, 'IfDone': [], 'GuaranteedPremium': 0.0, 'OCO': None, 'AssociatedOrders': {'Stop': None, 'Limit': None}, 'Associated': False}}], 'GuaranteedPremium': 0.0, 'OCO': None, 'AssociatedOrders': {'Stop': None, 'Limit': None}, 'Associated': False}], 'Quote': None, 'Actions': [{'ActionedOrderId': 0, 'ActioningOrderId': 0, 'Quantity': 1.0, 'ProfitAndLoss': 0.0, 'ProfitAndLossCurrency': None, 'OrderActionTypeId': 1}], 'ErrorMessage': None}
  11. Watch List Client api code

    Hi Brutsi, Please paste the JSON request you sent and the JSON response you received back. Many thanks, PM
  12. Hi I am receiving a yellow card on my API trades order status 8 statusreason 140 "Watch list client" What does this mean? I can see there is also 3 other statusreason codes with the same description. regards
  13. Hello Aniket, The API documentation needs to be updated. The version of Lightstreamer running on our servers is (v7.03). The client development kits (CDKs) matching v7.03 can be download at: https://lightstreamer.com/download/#ls70. You just have to pick the correct programming language CDK to match what you are using. Kind Regards, PM
  14. Greetings, We are trying to get the Streaming Prices for currency pairs using the LightStreamer Service. The Documentation mentions that Note: the backend servers are currently still using version 5.1.2 of Lightstreamer. You will need to download and use version 5.1.2 of the Lightstreamer SDK until the servers are upgraded to the latest Lighstreamer version. So is this the Server Version or the LightStreamer Client version that we need to use? We tried the latest LightStreamer-Client 7.1.2 and the server disconnects with server error 60 ----this version of the client is not allowed by the current license terms. We tried the lightstreamer-client 6.1.4 which in the NPM registry says compatible with legacy-server-5.1.2, but here we are not able to get the angular app working as the lightstreamer js is not compatible with the ES5 Strict policy. We tried the Lightstreamer-client-web but that also throws server error 60. Please let us know which LightStreamer Client version should we download to get the streaming service up at our end. TIA, Regards, Aniket Kadam
  15. Best way to know if Market is closed

    Hi Superee, It is the MarketPrcingTimes fields. Since these are Forex 24H trading markets, we've been using a shortcut internally and that is probably what is causing you confusion. DayofWeek 0 is Sunday and DayofWeek 5 is Friday. Since we know that FX markets open on Sunday and close on Friday, we just take the current week's Sunday and Friday dates. The actual Date returned in the field is just today's date and close time of 22:00 hours. We're ignoring the date and appending the 22:00 hours close/open times to the Sunday Start and Friday End dates to get each weeks open/close. Kind Regards, PM
  16. Streaming Data and Historical Data

    Hi Sir Newton, If those are indeed actual price ticks the team will be able to correct it appropriately without losing the data. Kind Regards, PM
  17. "According to the Pricing team, an erroneous price tick was sent after market close on Friday resulting in the Saturday price bar" By the way, if those price ticks are actual and not generated by error. I rather you keep it in the history. I can write code to combine those with Friday historical.
  18. Best way to know if Market is closed

    I submitted a GET for GBP/USD, response is = { "MarketInformation": { "MarketId": 401166448, "Name": "GBP/USD", "ExchangeId": 400000032, "ExchangeName": "FX (IFX) Retail Exchange", "MarginFactor": 2.0, "MinMarginFactor": null, "MaxMarginFactor": null, "ClientMarginFactor": 2.0, "MarginFactorUnits": 26, "MinDistance": 0.00001, "MinDistanceUnits": 27, "WebMinSize": 1000.0, "MaxSize": 50000000.0, "MarketSizesCurrencyCode": "USD", "MaxLongSize": 5000001.0, "MaxShortSize": 5000001.0, "Market24H": true, "PriceDecimalPlaces": 5, "DefaultQuoteLength": 5, "TradeOnWeb": true, "LimitUp": false, "LimitDown": false, "LongPositionOnly": false, "CloseOnly": false, "MarketEod": [], "PriceTolerance": 2.0, "ConvertPriceToPipsMultiplier": 10000, "MarketSettingsTypeId": 2, "MarketSettingsType": "CFD", "MobileShortName": "GBP/USD", "CentralClearingType": "No", "CentralClearingTypeDescription": "None", "MarketCurrencyId": 11, "PhoneMinSize": 5000.0, "DailyFinancingAppliedAtUtc": "/Date(1614117600000)/", "NextMarketEodTimeUtc": "/Date(1614117600000)/", "TradingStartTimeUtc": null, "TradingEndTimeUtc": null, "MarketPricingTimes": [ { "DayOfWeek": 5, "StartTimeUtc": null, "EndTimeUtc": { "UtcDateTime": "/Date(1614117600000)/", "OffsetMinutes": -300 } }, { "DayOfWeek": 0, "StartTimeUtc": { "UtcDateTime": "/Date(1614117600000)/", "OffsetMinutes": -300 }, "EndTimeUtc": null } ], "MarketBreakTimes": [], "MarketSpreads": [ { "SpreadTimeUtc": null, "Spread": 0.0001, "SpreadUnits": 27 } ], "GuaranteedOrderPremium": 10.0, "GuaranteedOrderPremiumUnits": 1, "GuaranteedOrderMinDistance": 50.0, "GuaranteedOrderMinDistanceUnits": 27, "PriceToleranceUnits": 0.0001, "MarketTimeZoneOffsetMinutes": -300, "QuantityConversionFactor": 1.0, "PointFactorDivisor": 100, "BetPer": 1.0, "MarketUnderlyingTypeId": 4, "MarketUnderlyingType": "FX", "AllowGuaranteedOrders": false, "OrdersAwareMargining": false, "OrdersAwareMarginingMinimum": null, "CommissionChargeMinimum": null, "CommissionRate": null, "CommissionRateUnits": null, "ExpiryUtc": null, "FutureRolloverUTC": null, "AllowRollover": false, "ExpiryBasisId": 1, "ExpiryBasisText": "", "StepMargin": { "EligibleForStepMargin": true, "StepMarginConfigured": true, "InheritedFromParentAccountOperator": true, "Bands": [ { "LowerBound": 0.0, "MarginFactor": 5.0 }, { "LowerBound": 7200000.0, "MarginFactor": 5.0 }, { "LowerBound": 14000000.0, "MarginFactor": 5.0 }, { "LowerBound": 21000000.0, "MarginFactor": 5.0 }, { "LowerBound": 54000000.0, "MarginFactor": 20.0 } ] }, "OptionTypeId": null, "OptionType": null, "StrikePrice": null, "MarketTypeId": 2, "MarketType": "Ordinary Market", "Weighting": 628, "FxFinancing": { "CaptureDateTime": "/Date(1614204000000)/", "PreviousCaptureDateTime": "/Date(1614117600000)/", "LongPoints": 0.15, "ShortPoints": -0.03, "LongCharge": -1.23, "PreviousLongCharge": -0.41, "ShortCharge": -0.99, "PreviousShortCharge": -0.33, "Quantity": 10000.0, "ChargeCurrencyId": 11, "DaysToRoll": 3, "PreviousDaysToRoll": 1 }, "UnderlyingRicCode": "GBPUSD", "NewsUnderlyingOverrideType": "NamedItem", "NewsUnderlyingOverrideCode": "GBP/", "TrailingStopConversionFactor": 0.0001, "IsKnockout": false, "Knockout": null } } Which value gives me the Weekly Market Close and Open day/times? Thank you. @Physicsman
  19. Thank you. I looked through the full history and found similar out of bound entries. Will provide sqlscript used to find out of bound entries. Note: I use Postgres, but you should be able to do similar queries in other databases. In the DB datetime is "BarDate". Will give you Saturday and Sunday select * forex_history where extract(isodow from datetime)in(0,6,7) Or to see just Saturday select * forex_history where extract(isodow from datetime)=6
  20. Streaming Data and Historical Data

    Hi SirNewton, According to the Pricing team, an erroneous price tick was sent after market close on Friday resulting in the Saturday price bar. The team are working on removing this from the chart database. Kind Regards, PM
  21. Streaming Data and Historical Data

    Hi SirNewton, I'll look into this for you and reply back with our findings. Kind Regards, PM
  22. Hello @Physicsman While processing Historical data, I saw something unusual that I need your help with. We know that the Steaming Data along with the market closes on FRIDAY 9:59PM GMT And, we know that the Steaming Data along with the market opens on SUNDAY 10:00PM GMT And, we know that Each "day" historical data covers from midnight (00:00) to 23:59 GMT But, I noticed that in the Historical Data that was outside that range. See Blow: AUD/JPY: ASK: {"BarDate": "2021-02-20 00:00:00", "Open": 83.062, "High": 83.062, "Low": 83.062, "Close": 83.062} BID: {"BarDate": "2021-02-20 00:00:00", "Open": 82.912, "High": 82.912, "Low": 82.912, "Close": 82.912} USD/CHF: ASK: {"BarDate": "2021-02-20 00:00:00", "Open": 0.89672, "High": 0.89672, "Low": 0.89672, "Close": 0.89672} BID: {"BarDate": "2021-02-20 00:00:00", "Open": 0.89607, "High": 0.89607, "Low": 0.89607, "Close": 0.89607} USD/JPY: ASK: {"BarDate": "2021-02-20 00:00:00", "Open": 105.514, "High": 105.514, "Low": 105.514, "Close": 105.514} BID: {"BarDate": "2021-02-20 00:00:00", "Open": 105.392, "High": 105.392, "Low": 105.392, "Close": 105.392} 2021-02-20 is a Saturday. The other pairs, I am processing had a BarDate of "2021-02-19 00:00:00", which is what I expected. Can you please explain the discrepancy of the BarDate of pairs AUD/JPY, USD/CHF, and USD/JPY? Thank you.
  23. @SupereeDuperee I get that,. I was just not expecting that amount of a spread change within a second.
  24. Closing trade

    Got it. Even though, I would rather control the order I close the trades myself, I have adjusted for FIFO. Thanks.
  25. Closing trade

    Hi SirNewton, When you didn't include anything in the Close field the system should be closing your positions in the order they were opened going from first to second..., rather than closing them at random. Reading through the following link on the rule, it looks as though the NFA's aim of implementing this FIFO rule was to prevent clients from "hedging", which is to have simultaneous offsetting long and short positions in the same market. https://www.investopedia.com/terms/n/nfa-compliance-rule-2-43b.asp Kind Regards, PM
  26. Closing trade

    Why enforce FIFO in the US? Not sure, why that would be the case. Why would the US regulators enforce that?
  27. Closing trade

    Are you a US client? Yes, I am in the US. And I am a US client. Did you have more than one open position in the same market, and you were attempting to close one of those open positions specifically? Yes, I had several open in the same market and was trying to close one specifically. When I don't include anything in the CLOSE, it seems to close a random trade. I was hoping to use CLOSE to close a specific trade. Thank you.
  28. Hi Superee, Check the OrderStatusReason code that is also included in the response. It provides more information on the error and its cause. Kind Regards, PM
  1. Load more activity
×