These are chat archives for binary-com/binary-extjs

7th
Oct 2014
Frank Carnovale
@frank-binary
Oct 07 2014 12:08
@Anton, I'm looking at these now..
How I can get start_time for each symbol for contract category Rise/Fall ?
Frank Carnovale
@frank-binary
Oct 07 2014 12:14
.. If you mean the start_time for pricing (or buying) a contract, then this is something that the user decides.. Is the contract to start now (start_time 0) or sometime in the future (start_time = some epoch value). This distinction is clearer in the "offerings" call in which one of the available filters is forward-starting = yes or no.
Anton Driemin
@AntonDriemin
Oct 07 2014 12:17
I mean this dropdown: http://prntscr.com/4tv61v
its different from symbol to symbol
Frank Carnovale
@frank-binary
Oct 07 2014 12:24
ah I see.. so we are saying, how do we know the valid range of start-times per-symbol for forward-starting contracts. hmm not sure if we expose that in the api, let me look around a little..
we do get "intraday_durations" but unfortunately it did not report limits on allowed start-times. I am going to have to research this in more detail and enhance the API to expose this.
Anton Driemin
@AntonDriemin
Oct 07 2014 12:29
thank you
Re your qn on ASIANU. It's a new bet-type but in theory the webapi layer should not be affected. Looking deeper..
Frank Carnovale
@frank-binary
Oct 07 2014 12:59
ok. the ASIAN U/D types are a very important change.. instead of a "duration" we specify the number of ticks. The Contract 'rest' interface does not support that yet. Anton, for now, best to not implement ASIAN contract types. I'll have to work on that.
(at least, we can now say the error message did make sense after all).
Anton Driemin
@AntonDriemin
Oct 07 2014 13:02
ok. But do you have more information about valid range of start-times per-symbol?
Frank Carnovale
@frank-binary
Oct 07 2014 13:07
We need to enhance the output of the contract_category/symbol call to deliver valid start-time info. For now, best way is to observe the time-gaps currently offered by the legacy web interface. There is a lot of code behind the derivation of these time-boundaries and I will have to identify best way of exposing this via the api.
Frank Carnovale
@frank-binary
Oct 07 2014 13:18
Anton we have some useful info in this call http://rmg-prod.apigee.net/v1/binary/symbols/frxUSDJPY
see property "intraday_interval_minutes". For forward-starting contracts, this shows the minimum start_time delay from "now".
Frank Carnovale
@frank-binary
Oct 07 2014 13:27
Your other question is about now to find barrier ranges. This is actually a difficult qn because it's not a static property of the symbol. It varies according to current market conditions. The only approach available at present is to guess reasonable boundaries and see if a contract-pricing call is accepted. Note that the trading website does not apply explicit barriers either.
Anton Driemin
@AntonDriemin
Oct 07 2014 13:31
I see intraday_interval_minutes, thank you, but it will not allow me to build valid range here http://i.imgur.com/Xx0mrpX.png - you see, it contains two time ranges with 5-mins interval
Frank Carnovale
@frank-binary
Oct 07 2014 13:46
Yes I see. Understood. It looks like the available starts are confined to the actual Stock Exchange trading hours. So from api calls we have the fact that the interval size (starting now) is 5 minutes, but we do not have the exchange trading hours, and we do not know how many forward-reaching days we want to offer. Again, I will have to study how the website gets this info. Trading hours are published here https://www.binary.com/c/trading_times.cgi
This info will have to be exposed in a new API call.
Anton Driemin
@AntonDriemin
Oct 07 2014 13:48
ok, thank you. I have trading times already on the dashboard, however, not from apigee, but from the web site directly.
Anton Driemin
@AntonDriemin
Oct 07 2014 17:49
I mean - I'm unable to use trading times in the drop down list (or it will be bad solution - parse HTML from the web site)
Frank Carnovale
@frank-binary
Oct 07 2014 18:54
gotit. Agreed, we don't want to depend on scraping the website. The good news: I began work immediately on a new set of calls "/exchanges" and "/exchanges/{exchange}". The latter will deliver all sorts of useful exchange-related meta data, including regular trading hours. Turns out to be non-trivial internally, but hope to deliver tomorrow sometime.
This still does not answer the question of forward-start-time limits on a per-symbol basis. I will be looking at that soon also.